Release notes: June 1sth - June 2nd, 2024

inriver is moving towards more incremental, smaller releases to be able to accommodate our customers in a better and faster way. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster. 

Please see below for the deployed features and improvements:

• As a Control Center user, I will now be able to see the creation and first activation (initial login) timestamps for each user in the user listing, allowing for easier management of invite resending and improved tracking of user onboarding.
• The Swagger documentation for the REST API has been updated to enumerate the available HTML templates, enhancing the user experience.

Please see below for the deployed bug fixes:

• We have applied a solution to ensure that for users utilizing the Syndicate + adapter with Content Delivery 1.7, any record import failures into S8 will be reported in the control center logs and documented in the WarningsAndErrors.csv resource linked to the master runtime entity.
  
  NB! Existing customers will need to do a Connect Service Reset to get the latest changes.
  
  
• We have applied a solution to ensure that in the Control Center, within the Model under CVL, adding an "Empty" CVL value via Swagger will no longer result in "NULL" entries in the database. This change enables users to export CVL values even with "Empty" CVL entries.
• We have applied a solution to ensure that an issue in the revision history of LocaleStrings has been resolved. The problem, where retrieving the latest value for a specific language was affected by case and accent insensitivity, has been fixed, ensuring accurate tracking of field revisions.
• We have applied a solution to ensure that error handling aligns with expectations for the logs in Control Center. Users now promptly receive guidance on addressing a "max call stack size exceeded" error, while a loading circle visually indicates logs being fetched from the server, preventing them from waiting for non-existent data.

inriver Implementation Standards
inriver's ambition is to collaborate with our partners in providing our customers with as safe and secure a PIM system as possible. With that in mind, inriver is improving the information on our Community to help implementation partners ensure quality, optimize implementations, and avoid pitfalls.
Read more about inriver Implementation Standards