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/OpenAPI documentation now more accurately reflects the API's request and response schemas across all endpoints. Required fields are correctly marked in the documentation, and internal .NET types that were incorrectly exposed in the schema have been removed.
NB! No API behavior has changed - only the generated documentation has been corrected to match the existing behavior.
Expression Engine
- It has been implemented so that the expression engine only evaluates expressions when the expression itself or one of its dependencies has changed.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that memberName/Method value from 'LogException' logs the actual method name that is logged from it, as this will be more useful in identifying which part encountered the exception.
- We have applied a solution to ensure that the work area tab is closed whenever the user logs out.
- We have applied a solution to ensure that the Create New Entity window correctly displays the full list of entities.
We have applied a solution to ensure that the rightmost columns remain visible and accessible in Table View when a column is pinned to the left.
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.