Q3 2020 (Honeysuckle) Release Notes

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

If applicable, detail what action(s) must be taken here

When can the action be taken (before, during or after upgrade)

User name of person that can provide additional detail

Name of user leaving comment: comment on what you encountered or ask a question @mention Contact person

Include issue link for bug fix, story or feature that applies

edge-rtac

New endpoints have been added to edge-rtac

Ngnx configuration needs to be updated in every environment, where edge-rtac is used

The nginx proxy for edge modules in the environments needs to be able to route to two different paths on the edge-rtac module:

* /prod/rtac/folioRTAC * /rtac

Before upgrade

@Khalilah Gambrell (PO)

https://github.com/folio-org/edge-rtac#configuration

https://folio-org.atlassian.net/browse/FOLIO-2835

ui-agreements

If a EBSCO KB customer,  please go to Settings > Agreements > Display settings and uncheck the settings under "Display "Suppress from discovery" setting on." These settings are not applicable. 

Change can be done before or after upgrade. 

@Khalilah Gambrell or @Owen Stephens

Permissions - Finance

The following were replaced by more granular permissions: Finance: all permissions for View and Edit ledgers, funds, budgets and fiscal years

Finance: View groups, ledgers, funds, budgets and fiscal years

The permission should still display in your instance as no script was written to delete them.

You are advised to update your finance related permissions sets, if you have any, and your users perms. simply remove the old ones and add the desired finance perms in the new format.

Anytime after upgrade

@Dennis Bridges

https://folio-org.atlassian.net/browse/UIF-228

ui-orders

When creating an order the "Re-encumber" toggle is set to active by default. 

Once fiscal year rollover is implemented in R1, if you choose to rollover encumbrances for the type of order. The system will then look to this field to determine if each individual "Open" order of that type will be encumber in the upcoming year.

Order templates will potentially override this setting. If you want to re-encumber these orders you should revise your order templates and confirm this box is checked. This way when applying the order template the re-encumber toggle will still be active by default.

Could be done before or after upgrade. The sooner the better

@Dennis Bridges

https://folio-org.atlassian.net/browse/UIOR-622

mod-data-import/mod-data-export

Previously these modules did not support running in HA mode(more than 1 instance of the module running)

It has been agreed that it will be the hoster's responsibility to create a persistent shared volume that can be shared between the tasks to run the modules in HA mode

Both these modules will be considered Horizontally Scalable

If mod-data-import or mod-data-export are being run with multiple tasks, then a persistent shared volume must be configured to save the files. The files are temporary and will be auto-deleted using a timer job periodically

• data-export : The file storage path used in the module is 

  "./storage/files" (for now this cannot be changed)

Change can be done anytime, just that any jobs triggered will fail if multiple tasks are running

@Kruthi Vuppala (data-export)
@Taras Spashchenko (data-import)

https://github.com/folio-org/mod-data-import#module-properties-to-set-up-at-mod-configuration

Horizontal Scalability Document

Presented in tech-leads meeting: 2020-10-21 Meeting notes

ui-eholdings/mod-kb-ebsco-java

Database schema restructuring was done

When multiple tenants are deployed to an environment or when a new tenant is installed that has not been setup with accurate HoldingsIQ credentials prior to upgrade, eHoldings app becomes non-functional. 

For the multiple tenants situation, newer version of mod-kb-ebsco-java is needed v.3.6.4 or v3.6.5(hotfix-1 version)

For single tenant on a fresh install, HoldingsIQ credentials can be configured from the UI using a PUT/PATCH request like below:

PUT https://{okapi-url}/eholdings/kb-credentials/80898dee-449f-44dd-9c8e-37d5eb469b1d with request body like

{
"data": {
"id": "80898dee-449f-44dd-9c8e-37d5eb469b1d",
"type": "kbCredentials",
"attributes": {
"name": "Knowledge Base",
"apiKey": "****",
"url": "https://api.ebsco.io" or "https://sandbox.ebsco.io", - based on whether its sandbox account or prod account
"customerId": "***"
}
}
}

After the upgrade

@Sobha Duvvuri

https://folio-org.atlassian.net/browse/MODKBEKBJ-537https://folio-org.atlassian.net/browse/MODKBEKBJ-550

mod-agreements

Supplementary Document cleanup

When upgrading from Goldenrod consider running the Supplementary Document cleanup job on initialising the module in the tenant. This is to fix an issue that could lead to a single supplementary document being linked to multiple agreements. The cleanup job will detect this situation and duplicate the document so each agreement is linked to it's own copy of the document

On installing the module in the tenant, include

cleanSupplementaryDocs%3Dtrue

in the tenantParameters.

e.g.

/_/proxy/tenants/diku/install?tenantParameters=cleanSupplementaryDocs%3Dtrue

After the upgrade

@Owen Stephens

https://folio-org.atlassian.net/browse/ERM-1114