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 features and improvements:
General
- We've implemented a new REST API endpoint, GET /api/v1.0.0/extensions/queue-summary, to provide grouped counts of queued and error messages per extension ID. The endpoint requires no query parameters and returns a summary for all extensions. The existing GET /api/v1.0.0/extensions/queue endpoint remains unchanged and fully backward-compatible.
- It has been implemented that the spinner is rendered and painted by the browser before heavy rendering begins, providing immediate visual feedback to the user.
- It has been implemented that field editor-type lookups are cached, eliminating repeated scans of the complete field list and improving lookup performance.
- It has been implemented that field and category templates are precompiled once and reused, eliminating redundant template compilation for individual fields.
- It has been implemented that right-click paste handling uses a single shared DOM listener instead of individual searches and listeners for each field.
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.