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
- It has been implemented that the Swagger documentation for the REST API now clearly states whether a PUT endpoint fully replaces a translated field (clearing any language not included in the request) or only updates the languages provided while keeping the rest unchanged. This removes the previous ambiguity where some PUT endpoints behaved differently than expected without it being documented.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that Enrich Assistant proposals can be applied correctly even when a workspace limits which fields are visible on an entity.
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.