Sections in the article
Inriver is moving toward smaller, more incremental releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver can improve release quality and transparency and identify and mitigate erroneous behavior 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 the Quick Search bar performs searches for multiple items more efficiently, reducing search latency and improving overall responsiveness.
It has been implemented that the multi-search not-found list UI has been updated to align with the new design. Additionally, a copy-to-clipboard feature has been introduced, allowing users to copy all missing IDs at once and seamlessly paste them into Excel or any other application of their choice. This enhancement addresses user feedback received following the introduction of the modernised UI.
Syndicate Core
- It has been implemented that the Advanced UI prevents the same Entity type from being used at multiple levels within a mapping (e.g., Product appearing more than once). This restriction ensures accurate data lineage tracking and prevents mapping inconsistencies that could lead to unreliable results.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that deleting an entity type through the REST API returns a clear error when the entity type is still in use. The message now names what still refers to it, for example, field sets, restricted field permissions, search hints, or print display information, and explains how to remove it. Old entity version data no longer prevents an entity type from being deleted once all its entities are removed. If a delete fails for an unexpected reason, the API now returns a server error (HTTP 500) instead of HTTP 400.
In addition, new entity types and other model changes made through the REST API are now reliably available to the following requests, and creating or updating a field set without a name or description no longer returns an error. - We have applied a solution to ensure that reordering folders and queries in My work areas is saved and no longer jumps back to the previous position when one or more top-level shared folders have an Index other than 0.
- We have applied a solution to ensure that entity queries return accurate results when field values contain special characters, such as % or _, preventing unintended query matching and ensuring correct data retrieval.
- We have applied a solution to ensure that the Share with individuals dropdown in the workspace-sharing interface supports searching by name and email address, enabling users to locate and select the intended individuals more efficiently.
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.