Release notes: August 10th - August 11th, 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 to allow workflow creators to define the exact channel relevant to a 'Plan & Release' assignment. This ensures workflow users are directed to the correct location within the Plan & Release application. When 'Plan & Release' is selected as the desired workspace within the assignment settings, adding additional context to the assignment is now possible. This feature enhances the precision and relevance of workspace assignments.
• It has been implemented to enable users in the REST API to create queries for work areas, mirroring the functionality available in Portal-Enrich. This enhancement is part of an ongoing effort to synchronize work area behavior between Portal-Enrich and the REST API.
• It has been implemented for BrandStore to shift the processing of image resources from the server to the client side. When the export type option is set to "Include Files" or "Both" for downloading Excel files, the browser will now handle the download of image resources sequentially, improving efficiency and reducing server load.
• It has been implemented for BrandStore to display progress and status information when downloading Excel files with included resources. The status messages, such as 'Preparing Resources to be downloaded' and 'Downloading # out of # resources' provide users with real-time updates on the download process, enhancing visibility and user experience.
• It has been implemented as an improvement in the REST API that users working with the 'Model-Category' and the 'Model-FieldSet' endpoints can now omit the ID in the request body when performing a PUT request. This enhancement streamlines the update process by eliminating the need to include redundant ID information.

Please see below for the deployed bug fixes:

• We have applied a solution to ensure that Portal users can specify the character separator for CSV files uploaded to import data in Enrich. A new setting, IMPORT_DATA_CSV_SEPARATOR, has been introduced to accommodate various CSV formats. If the server setting is not configured in Control Center, the default CSV separator will remain as ';' to maintain compatibility with the current implementation. This enhancement supports CSV files that use separators other than ';', such as ','.
• We have applied a solution to ensure that when a link rule is updated with a LocalString in any language, the changes are saved correctly, regardless of the default Data Language setting in the UI. The link rule will now accurately reflect the new LocalString value specified by the user. This enhancement resolves the issue where users working with multiple languages were unable to save updates to link rules with LocalStrings in languages differing from the default.
• We have applied a solution to ensure that the revision value is correctly updated when modifying entities via the REST API, performing mass updates or importing data. This fix addresses issues where the revision value was previously incorrect, ensuring accurate and consistent revision tracking across all update methods.
• We have applied a solution to ensure that users can successfully copy entities even when a RegExp field is present. The issue where warnings on Unique field(s) prevented the copying of entities has been resolved, allowing for smoother duplication of entities with RegExp fields.
• We have applied a solution to ensure that LocaleString History in the REST API accurately reflects updates. This fix addresses the issue where the history did not update correctly due to the presence of null values in the [Value] column of FieldRevisionHistory.
• We have applied a solution to ensure that query results in Enrich are consistent between saving a work area and executing the same query conditions in a new query. This addresses the issue where the number of entities returned differed between the saved work area and new queries with identical conditions.

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