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 bug fixes:
General
- We have applied a solution to ensure that fields can be successfully updated via Mass Update in Table View when entities are filtered using a datetime column.
- We have applied a solution to ensure that changes to multiple language values of the same localized field in Table View are correctly represented in the payload, preventing save errors.
- We have applied a solution to ensure that CVL filter options are populated independently of row data and are available in the filter sidebar, while restricting parent-child CVL validation to row editing to preserve existing row validation behavior.
- We have applied a solution to ensure that the workspace name on the entity details page stays consistent after refreshing the browser page, instead of reverting to the Default workspace.
- Please also note that this release rolls back the previously introduced changes to how locale string field types are displayed on the entity Details tab. The Details tab will revert to its prior behavior for locale string fields until further notice.
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.