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 Field Set and Field Type retrieval mechanisms significantly improve response times, thereby reducing the overall load time of the Enrich Export form.
- It has been implemented that two new operators, ContainsAny and NotContainsAny, are now supported for the CreatedBy, ModifiedBy, and LockedBy fields when creating a new Workarea query through the REST API.
Table View
- It has been implemented that the Table View now includes support for dynamic grid UI with multiline row configuration, enabling enhanced flexibility and improved readability in data presentation.
Print 2.0
- It has been implemented that Print 2.0 has optimized the handling of multiple LinkUpdate notifications, reducing system load and improving overall responsiveness during processing.
- It has been implemented that Print 2.0 now features improved logging by reducing noise through the suppression of less relevant messages and enhancing critical logs with more detailed and informative content, thereby facilitating easier debugging and monitoring.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the Create New Entity Model modal no longer exhibits a brief flicker upon opening, providing a smoother and more stable user experience.
- We have applied a solution to ensure that validation is enforced for consistency between Parent and Child CVL values during REST API create and update operations. The system now blocks updates where the Child CVL does not align with the selected Parent CVL, and vice versa, thereby maintaining data integrity and preventing invalid CVL combinations.
- We have applied a solution to ensure that all newly added languages in the Enrich module’s Details tab (Locale String fields) are immediately retrieved and displayed in the language list. This resolves the issue where the last added language would not appear until an additional language was added.
- We have applied a solution to ensure that Control Center correctly accepts CVL keys containing square brackets and other previously accepted characters. The validation logic has been updated to a blacklist-based approach, rejecting only explicitly disallowed characters while permitting all others, including square brackets and Unicode characters - unless otherwise specified.
- We have applied a solution to ensure that updating a FieldType from non-unique to unique no longer results in process locking, even when the FieldType contains null values. Additionally, a validation has been implemented to detect and prevent the conversion if duplicate values exist within the FieldType, safeguarding data integrity by producing an error in such cases.
- We have applied a solution to ensure that the admin user can successfully unlock all selected entities after clicking the "Unlock Selected" button in the Control Center > Locks module.
- We have applied a solution to ensure that the Collapse button in the Enrich module functions correctly, restoring its expected behavior for expanding and collapsing content sections.
- We have applied a solution to ensure that, for customers using 3DL, the Field Revision is correctly populated in the Enrich UI when an entity is created via Excel import, addressing the previous issue where this information was not displayed.
- We have applied a solution to ensure that, for customers using 3DL, fields are no longer duplicated for the Product entity within the Enrich module, resolving the issue that caused redundant field entries.
Expression Engine
- We have applied a solution to ensure that the expression engine preserves expressions on LocaleString fields during Excel import, preventing unintended deletion of expressions.
Print 2.0
- We have applied a solution to ensure that Print 2.0 reliably displays document previews in the Automation module, resolving the issue where previews were occasionally not shown.
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.