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 releases and identify and mitigate any erroneous behaviour 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 when an administrator imports CVL values from a file in the Control Center Model page, a log entry is now recorded in the environment log. The log entry captures which user performed the import, which CVL was affected, and the name of the uploaded file, giving administrators full traceability over CVL value imports alongside the existing logging for add, update, and delete operations.
Inspire
- The "Include Context" checkbox on the Inspire Translate Agent configuration now displays an informative tooltip explaining what context is included when enabled (glossary terms, linked entity data, and existing translations). Separately, the field and language selection now shows a live task counter and enforces a maximum of 25 tasks (fields × languages) per step — this limit is always active regardless of context settings, preventing users from exceeding the system's processing limit.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the entity list in the workflow "In Progress" view tab displays a vertical scrollbar, allowing users to scroll through and access all entities when the list exceeds the visible area.
- We have applied a solution to ensure that entities in a workflow process are correctly displayed in the entity list/grid in the Workflow process view. Previously, the workflow step badge and Assignments panel showed entities were assigned, but the entity table below was empty.
We have applied a solution to ensure that localized string values are saved as independent field updates for each language rather than as a single aggregated localeString object.
- We have applied a solution to ensure that action buttons on the Details tab of channel nodes are correctly hidden whenever the Segment and Fieldset dropdown controls are displayed.
- We have applied a solution to ensure that the Expression Engine aborts cyclical update chains when entities of the same type reference the same field type and are processed
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.