Sunflower (R1 2025) Critical Service Patch #9 - Modules release deadline: July 20 | Release notes update: July 24 | GA date: July 27

Sunflower (R1 2025) Critical Service Patch #9 - Modules release deadline: July 20 | Release notes update: July 24 | GA date: July 27

MOD RELEASE DEADLINE JULY 20

TO BE RELEASED AT JULY 27

Dashboard

Notes on Functionality by Area (expand each section to see list of issues)

Issues Impacting Functionality - Acquisitions

GOBI integration fix

  • Addressed an issue where expense classes are intermittently not populated in POLs created via the GOBI API. For more details see MODGOBI-248.

 

Issues Impacting Functionality - ERM (Agreements, eholdings, Licenses, eUsage)

eholdings app fix

  • Address usage not returning all titles or costs. Only applicable to eholdings app customers that have EBSCO Usage Consolidation integration. For more details MODKBEKBJ-825

Agreements app fix

  • Agreement start and end date calculations are once again correct following a security update. For more details see ERM-4130.

Issues Impacting Functionality - Platform

No Functional impact.

 

Issues Impacting Functionality - Security Updates

EBSCO hosted customers only:  A CSP #8 security update will be deployed to all EBSCO hosted customers with CSP #9. The update: A security setting will be enabled that controls which websites are allowed to communicate with FOLIO.  If your institution access FOLIO through standard, supported interfaces, no further action is required. If your institution has built custom integrations that call FOLIO APIs directly from a browser, that address must be added to EBSCO’s approved list, or requests from it may be blocked after this update is deployed to your institution's environment. Please contact your Customer Account Specialist (CAS) via EBSCO Connect, if you have questions and to add your integration's address to the allow-list. Read more details about security update

Issues Impacting Functionality - User Management

No Functional impact.

Issues Impacting Functionality - Circulation & Fulfillment

INN-Reach Fixes (interlibrary lending)

  • Item re-linking now properly handles contribution workflow — When items or holdings records are moved to another instance within the same consortium, the system now properly handles the contribution lifecycle. The fix ensures that items are decontributed from the central server when moved and then recontributed under the new bibliographic record, maintaining data consistency across the INN-Reach network. https://folio-org.atlassian.net/browse/MODINREACH-512

SIP2 Fixes

  • Access token refresh logs fixed — When an access token refresh operation failed during a SIP2 login attempt, the system was incorrectly logging the refresh as successful even though the underlying login operation had failed. This could mask authentication issues in logs, making it harder to debug connection problems. The fix ensures that failed login operations are properly reflected in log messages, clearly indicating that both the refresh and login operations have failed. https://folio-org.atlassian.net/browse/SIP2-316

 

Issues Impacting Functionality - Metadata Management & Serials Management

Inventory app Fixes

  • ECS only: A user viewing a shared instance was able to click links to item and holdings records that they had no active affiliation. Clicking a link resulted in a catastrophic error. Intermittent issue. For more details UIIN-3675

  • ECS only: Unable to move an item between tenants due to a database configuration limitation. For more details MODINV-1393

  • Feature flag to prevent redundant updates for Inventory records: https://folio-org.atlassian.net/browse/MODINVSTOR-1580 . The optimization work was completed in Sunflower, but it impacted workflows by not guaranteeing the updated date was the same between FOLIO and source record instances. In this CSP, a feature flag was created so that this is disabled by default; with the flag disabled, the updated date will be the same between the FOLIO and source records, regardless of mapping that doesn’t exist between the two.

    • For ECS: This flag is maintained at the central tenant-level; when disabled/enabled, it will impact all member tenants

Serials app Fixes

ECS only: Serials Receiving Pieces — Fix for Consortium Libraries Using Both Central and Local Ordering. Libraries in a consortium environment (ECS) that use both central ordering and local ordering were unable to generate receiving pieces from the Serials Management app for orders placed at the local (member) level.

  • What was fixed: The app now correctly detects whether you're working in the central tenant or a member tenant. If you're in a member tenant, the unnecessary affiliation field no longer appears, and receiving pieces can be generated as expected. For more details UISER-205

Issues Impacting Functionality - Data import

  • Data import logs performance and scalability improvements

    • Improved Performance for Data Import Log Loading - We've optimized the way Data Import log entries are retrieved. Libraries running large import jobs should see faster load times when viewing import logs. This includes database index improvements to ensure the log page responds promptly, even for high-volume imports. For more details MODSOURMAN-1438 & For more details MODSOURMAN-1437

    • During high-volume data import runs, some journal record entries could fail to save due to a database conflict (deadlock), potentially resulting in incomplete import logs even though the records themselves were imported. This fix prevents those conflicts so that all journal entries are reliably recorded during large imports.For more details - MODSOURMAN-1428

  • Single record data import queue management

    • When importing a single record via Z39.50 (e.g., from Biblioteca Nacional de España), some users received the error: "Record has been queued for import, but is not yet available." This patch addresses the underlying timing issue so that single record imports complete successfully without this error. For more details MODINV-1397

  • ECS only: Data Import Log Sorting and Pagination Fix - Some libraries experienced issues where the Data Import log displayed an inconsistent number of records and did not sort correctly by Record number or Title. Additionally, clicking "Next" to page through results had no effect. This patch resolves these sorting and pagination issues so that import logs display and navigate as expected. For more details - MODSOURMAN-1436

Issues Impacting Functionality - Data Export & OAI-PMH

No Functional impact.

Issues Impacting Functionality - Bulk-edit

No Functional impact.

Issues Impacting Functionality - Lists & Reporting

No Functional Impact.

Approval Log

https://folio-org.atlassian.net/issues/?jql=filter%3D23654

Tickets list

https://folio-org.atlassian.net/issues/?jql=filter%3D23654

Modules list

Release tag

 

Configuration

CSP

Functional Area

Change or Additions

Considerations

Action timing,
Action required

Comments

Contact person,
Related JIRAs

CSP

Functional Area

Change or Additions

Considerations

Action timing,
Action required

Comments

Contact person,
Related JIRAs

9

folio-keycloak

Configurable admin credentials for startup scripts; KC_HTTPS_KEY_STORE renamed to KC_HTTPS_KEY_STORE_FILE to follow Keycloak Environment variable format: Configuring Keycloak

New Environment Variables / Breaking Change

Before upgrade — deployments setting KC_HTTPS_KEY_STORE must rename it to KC_HTTPS_KEY_STORE_FILE

New: KC_BOOTSTRAP_ADMIN_USERNAME (default admin) and KC_ADMIN_USER (default admin) — admin usernames for configure-realms.sh and

keycloak-scripts/enable-client-credentials.sh respectively, previously hardcoded to admin. The existing KC_BOOTSTRAP_ADMIN_PASSWORD and KC_ADMIN_PASSWORD variables had their default-value handling fixed (previously could silently resolve to an empty password when unset); both now default to admin, with

KC_BOOTSTRAP_ADMIN_PASSWORD still falling back to KEYCLOAK_ADMIN_PASSWORD if set.

Renamed: KC_HTTPS_KEY_STOREKC_HTTPS_KEY_STORE_FILE (same default

/opt/keycloak/conf/test.server.keystore and meaning), used in both start.sh and start-fips.sh — if left unrenamed, the keystore path silently falls back to the

default.

https://folio-org.atlassian.net/browse/APPPOCTOOL-37