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 that a toggle has been added to the Control Center, enabling users to switch between the legacy interface and the newly restyled user interface.
- It has been implemented that updates to the Event Filtering Configuration for Extensions made via the Control Center are now logged and displayed on the Control Center's Logs page.
- It has been implemented that the update process for toggling FieldType uniqueness in Control Center → Data Model – FieldType Configuration has been optimized to improve performance and scalability.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the Control Center now blocks the entry of special characters such as ', <, >, ±, *, +, and \ in CVL values. This prevents invalid input and enhances data integrity by restricting unsupported characters from being saved.
- We have applied a solution to ensure that users can now successfully delete a Field when the Notification Query utilizes a valid Operator as specified in the official documentation - https://community.inriver.com/hc/en-us/articles/360018873314-SystemQuery
- We have applied a solution to ensure that multiple clicks on the Save button in the Add Extension page no longer result in duplicate extensions being created. Safeguards have been implemented to enforce single submission, thereby preventing unintended duplicate entries and improving system reliability.
Expression Engine
- We have applied a solution to ensure that the expression engine correctly handles dependencies within FieldSets.
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.