Release notes: September 28th - September 29th, 2024

inriver is moving towards more incremental, smaller releases to accommodate our customers better and faster. 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 that Control Center Users can now start and pause extensions directly from the extensions list. A "play/pause" button will be displayed for each extension: a pause icon indicates an active extension, while a play icon denotes a paused state. For disabled extensions, the indicators will be greyed out and inactive, ensuring clarity and ease of use.
• It has been implemented that Control Center now includes an improved prompt within the self-service environment copy feature. The updated message is: "Copying an environment does not include extensions/packages and extension settings. You must upload these to the target environment after the copying process is finished." This enhancement provides clearer guidance to users, ensuring that they are informed of the necessary steps to fully replicate environments, particularly regarding the handling of extensions and their configurations.
• It has been implemented that, in Control Center, all customer environments will be displayed in the drop-down menu of the Target Environments, regardless of the entity model of the current environment. However, suppose a user selects an environment that does not match the entity model of the current environment. In that case, an error message will be generated, indicating that the environment copy cannot proceed and advising the user to seek assistance from Support. This feature aims to clarify the limitations of cross-entity model environment copying, preventing confusion about the absence of certain environments in the target selection.
• It has been implemented that in the Portal, the number of fields loaded on the Enrich - Details page is now filtered by the selected FieldSet. By loading only the necessary fields, this optimization reduces the amount of data transferred to the browser, improving performance and efficiency during the enrichment process.
• It has been implemented that the CVLFIELD_SORT_BY_DISPLAY_LABEL setting allows specified field types to be sorted alphabetically in the UI.
  This cannot be applied globally, as some CVLs, such as EnrichmentStatus, require index-based ordering. When a CVL field's fieldtypeid matches an entry in this setting, its values are sorted alphabetically according to the user's language,
  improving efficiency and reducing frustration, particularly when large lists do not align with the expected order due to language differences.
• It has been implemented that, in the Enrich Overview, tooltip text has been added for the Includes section header, stating, "Here you can see up to 8 parent entities, click to see more." A tooltip for the Included In section header now reads, "Here you can see up to 8 child entities, click to see more." Both headers have been made clickable, which will open the corresponding Includes and Included In tabs, enhancing user navigation and accessibility.

Please see below for the deployed bug fixes:

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