Release notes: August 3rd - August 4th, 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:

• It has been implemented for Syndicate Plus users to enhance the Value Mappings functionality. A "Download" button has been added within the Value Mappings section. This button lets users conveniently download the value mapping data for further use and analysis.
• It has been implemented so that the new Control Center metrics view now displays the Database Size in MB instead of GB. Please note that this feature is only available in the Production stack.
• It has been implemented so that PIM administrators can add new Field Types, Entity Types, and Link Types to the data model without these changes being immediately published to Content Stores. This allows for more controlled and deliberate updates to the data model.
  
  Details of the changes in the server settings are as follows:
  
  • EXCLUDE_NEW_ENTITYTYPES_FROM_CONTENTSTORES = TRUE -> New EntityType excluded from all Content Stores
  • EXCLUDE_NEW_FIELDTYPES_FROM_CONTENTSTORES = TRUE -> New FieldType is excluded from all Content Stores
  • EXCLUDE_NEW_LINKTYPES_FROM_CONTENTSTORES = TRUE -> New LinkType is excluded from all Content Stores
  • EXCLUDE_NEW_ENTITYTYPES_FROM_CONTENTSTORES = FALSE -> New EntityType is excluded from all Content Stores
  • EXCLUDE_NEW_FIELDTYPES_FROM_CONTENTSTORES = FALSE -> New FieldType is excluded from all Content Stores
  • EXCLUDE_NEW_LINKTYPES_FROM_CONTENTSTORES = FALSE -> New LinkType is excluded from all Content Stores

NOTE! To maintain backward compatibility in server settings, the following logic is applied to EXCLUDE_NEW_FIELDTYPES_FROM_CONTENTSTORES:

• When a user adds a new Field Type, the setting is validated.
  • Setting is absent or set to FALSE - behavior remains unchanged.
  • Setting is TRUE - new Field Type is excluded from all Content Stores.

Please see below for the deployed bug fixes:

• We have applied a solution to ensure that IIF listeners no longer spam logs when tracking deleted links in cases where the link source or target is missing a unique ID.
• It has been implemented so that users can now export resources for Syndicate without encountering errors.
• It has been implemented so that the Control Center process has been optimized to ensure smooth and responsive performance when switching between links using the shortcut menu.
• It has been implemented so that pagination has been added to the process of retrieving and deleting all cache blob files for Image Configuration, enabling efficient cleaning of all cached data stored in the blob per image configuration
  
  

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