...
| Functional Area | Change or Addition | Considerations | Action timing, Action required | Comments | Contact person, Related JIRAs |
|---|---|---|---|---|---|
| Affected app or module | What has been changed or added that should be noted for this release | What challenges may arise related to this change or addition | When can the action be taken (before, during or after upgrade)? If applicable, detail what action(s) must be taken here Is this action required for the next release? | Name of user leaving comment: comment on what you encountered or ask a question @mention Contact person | User name of person that can provide additional detail. Include issue link for bug fix, story or feature that applies |
| Consortia manager | Added mod-consortia and ui-consortia-settings | Please review the following documentation Steps to setup Consortia env. This will instruct you as to how and why you would enable this functionality. | Configuration takes place after the upgrade | Applicable only for multi-tenant FOLIO customers. If site is not multi-tenant the are no actions required to disable these functions. | |
| Login | Changes made to mod-consortia, mod-login, mod-users, mod-authtoken. Username is unique across member tenants | TBD | TBD | Serhii_Nosko | |
| Consortia manager | In an environment that has consortia functionality enabled (see above) There is now an area in settings where consortia membership can be edited. | Membership can only be edited in the UI. To add or remove members you must use APIs (see above for more info) | After migration | ||
| Consortia manager | (ONLY valid in central tenant) Settings areas that can be manipulated via the consortia manager now have a "source" field with a possible value of "consortia" OR "local" | No action is required but users should be aware they can only edit settings with source "local" unless they're in Consortium Manager. | N/A | ||
| Export manager | migrated mod-data-export-spring to quartz implementation | No longer need to re-enable modules. Just install and enable once | This would be a consideration for after the upgrade | More than one mod-data-export-spring can now be run in parallel. | |
| Invoices | Invoices can now be assigned to previous fiscal years. When processed all transactions will be made against the corresponding fiscal year. | Users will need specific permissions to perform this action (see below). | No action required | If ignored invoices will continue to apply to the current fiscal year. | |
| Users | (ONLY applicable if consortia enabled) User type is a required field. For non-consortia environments it is optional but can be used if desired through the UI. | In a consortia environment, users must be given a type of "patron" OR "staff". There is also a type of "system" and "shadow" that is used by FOLIO to manage user accounts and access across members. | Dennis Bridges |
New Apps
| App | Description | Comments/notes | Product Owner |
|---|---|---|---|
| mod-consortia | Backend module that enables workflow collaboration between FOLIO tenants | Not included in FOLIO platform complete | |
| ui-consortia-settings | UI module that surfaces workflow collaboration functionality in FOLIO systems with mod-consortia enabled | Not included in FOLIO platform complete |
Permissions Updates
| App | New Permissions | Deprecated Permissions | Product Owner |
|---|---|---|---|
| Invoice | Pay against the previous year | ||
| Consortia manager | Can create, edit and remove settings; Can share settings to all members; Can view existing settings | ||
| Organization Settings | |||
| Acquisition units Settings | |||
| Finance Settings |
...