Sections in the article
inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. 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 so that saving a Link Rule Definition in Plan & Release is now more efficient, with noticeably faster processing times. The degree of improvement may vary depending on factors such as the complexity of the queries, the number of rules or queries involved, and the volume of matching entities.
- It has been implemented so that, in Plan & Release, the process of rebuilding a channel now provides real-time progress reporting for the RebuildChannel job.
- It has been implemented so that an additional index is added to the expression table to enhance query performance, specifically addressing issues related to slow entity creation within the portal. This indexing strategy aims to optimize data retrieval times, thereby reducing latency during entity creation operations.
Inspire
- It has been implemented so that, when translating using the Inspire Translate Agent, additional context data is provided whenever the "include context when translating" option is selected. The supplied context is determined by the customer’s Inspire configuration and may include specifications, as well as fields from the current and linked entities, thereby enhancing translation accuracy and relevance.
- It has been implemented so that the Inspire Drawer on the Details tab has been restyled, providing a refreshed and more consistent user interface experience.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that, in the Portal under Enrich > Details Tab, pressing Enter in a text field will no longer attempt to save the entity when no changes have been made. This prevents unnecessary save actions and ensures that the system only processes updates when actual modifications occur.
We have applied a solution to ensure that, in the REST API, the endpoint /api/v1.0.0/entities/{entityId}/channels now correctly respects the CHANNEL_FILTER and CHANNEL_FILTER_ENHANCED server settings, providing consistent and filtered results based on the configured channel parameters.
We have applied a solution to ensure that Specification fields referencing deleted Unit CVL values are handled correctly. Previously, deletion of a Unit CVL value used in a Specification FieldType could cause the UI to fail in displaying related Categories and FieldTypes, giving the appearance of broken configurations. With this update, missing Unit CVL references are now displayed in square brackets (e.g., [DeletedUnit]), preventing display errors and allowing administrators to view and manage Specification templates without manual intervention or confusion.
We have applied a solution to ensure that, in the Portal, CVL values provided by the CustomCVLValuesExtension are correctly separated from static CVL values when a Custom Value List is configured for a CVL. This prevents mixing of dynamic and static entries, ensuring accurate and consistent value selection.
We have applied a solution to ensure that the starred entity is correctly moved to the first position in the plan and release view. This fix addresses the issue where the starred entity was not being prioritized as expected, preventing it from appearing at the top of the list.
inriver Implementation Standards
inriver's ambition is to collaborate with our partners in providing our customers with the safest and most secure PIM system 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.