Sections in the article
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.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
Please see below for the deployed features and improvements:
General
- It has been implemented that, within Control Center, new columns will be added to the server settings configuration. These columns include Created, Modified, Created By, and Modified By. Adding these fields will enhance the tracking and management of server settings, providing clear records of when configurations were created and modified and identifying the users responsible for these changes.
Expression Engine
-
It has been implemented that, within the Expression Engine, the ability to determine the Content Segmentation ID via an expression has been added, similar to the field set ID functionality. Additionally, a new function has been introduced to the Expression Engine: SEGMENTNAME([segmentId]). This function returns the name of the segment. If no segmentId is provided, it will return the current entity’s segment name; if a segmentId is supplied, it will look up and return the name of the segment associated with the specified ID.
Examples of usage:
- =SEGMENTNAME() – Returns the name of the current entity's segment.
- =SEGMENTNAME(5 – Returns the name of the segment with ID 5.
Brand Store
- It has been implemented that, within Brand Store, updates have been made to handle support for EPS and PSD file extensions, enabling preview functionality similar to other image types. This enhancement aims to provide a more seamless and intuitive user experience by allowing users to preview EPS and PSD files directly within the interface, thereby improving workflow efficiency and accessibility.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that, in Control Center, users can no longer switch CVL fields from multi-value to single-value when existing entities contain multiple values in the specified field. This change prevents data inconsistency and enforces field integrity across all associated records.
- We have applied a solution to ensure that users in Control Center can now delete unused CVL values without issue, and these deletions are automatically reflected in Enrich, maintaining consistency across the platform.
Brand Store
- We have applied a solution to ensure that, in Brand Store, labels for features and functionalities default to the item in the default language. If the default language item is null or empty, the system will fall back to the backup language ("en"). If both are unavailable, the label will default to the field type ID (e.g., "[itemcode]") to ensure consistent display.
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
Comments
0 comments
Please sign in to leave a comment.