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 behaviour 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:
Table View
It has been implemented so that segments are updated in the table view immediately after the mass update segments action is completed, without requiring a page refresh. This ensures the user interface remains synchronized with the underlying data state and provides a seamless, real-time user experience.
Workflow
It has been implemented so that the date and time fields within the workflow use the same formatting as those displayed in Entity Details, ensuring interface consistency and improving usability through a unified representation of temporal data.
Inspire
It has been implemented so that Inspire functionality is enhanced with loading indicators and improved status messaging, providing clearer feedback during processing and improving overall user awareness and experience.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the date picker follows its associated field when scrolling within the Details tab, improving usability and preventing unintended interactions when the date selection window is open.
-
We have applied a solution to ensure that Parent-Child CVL validation in the REST API is fixed and enhanced.
The following endpoints are affected:v1.0.0/entities:upsert
v1.0.0/entities:createnew
v1.0.1/entities:createnew
v1.0.0/entities/{entityId}/fieldvalues
Validation now correctly enforces that:
The first Parent CVL field (lowest index) determines the validation behavior for all Child CVLs.
All Child CVLs sharing the same Parent are validated against it.
Fields not displayed in the Portal are excluded from validation.
Updating a CVL automatically updates descendant CVLs, removing invalid values unless explicitly provided in the payload.
Syndicate Core
We have applied a solution to ensure that tagging an empty Workarea to a Syndicate no longer causes the Syndicate to error, allowing execution to proceed according to the configured settings.
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.