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 Control Center system logs can now be retrieved programmatically through the REST API. A new endpoint, /api/v1.0.0/logs, returns log records for the current environment and supports filtering by log level, time range (in UTC), free-text search across the message, module, and username, and a maximum number of results to return.
Please note! This endpoint is only accessible to roles with the APIViewSystemLogs permission.
- We've updated the REST API Swagger documentation for the CVL value deletion endpoint (DELETE model/cvls/{cvlId}/values/{key}) to make it clear that deleting a CVL value does not check whether it is still in use elsewhere. API users are responsible for verifying a CVL value is not in use before deleting it, as doing so may otherwise lead to data integrity issues.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that all supported language codes - including Norwegian ("no") - can be added via the REST API endpoint POST /api/v1.0.0/model/languages. Previously, some valid language codes were incorrectly rejected with the error "The language code isn't recognized" due to environment-specific differences on the server.
- We have applied a solution to ensure that Excel files exported from Enrich can be imported again via Import Data without any changes being made first, without an error occurring.
- We have applied a solution to ensure that the CVL list in Control Center correctly reflects the actual state immediately after a failed Add or Delete operation. Previously, when adding a CVL with an identifier that did not meet the naming requirements caused an error, the failed entry would remain visible in the list even after the error message was dismissed. Similarly, a failed Delete operation could leave the list showing an inaccurate state. In both cases, users had to manually refresh the page to see the correct CVL list. The CVL list now updates automatically after an error is dismissed, so the view always reflects the true state without requiring a manual page reload.
- We have applied a solution to ensure that field type IDs are handled consistently regardless of letter casing across all REST API endpoints. Previously, some endpoints required the exact casing of a field type ID while others did not, which could cause unexpected "not found" or validation errors when a slightly different casing was used.
- We have applied a solution to ensure that reordering items in Table View is fast and responsive, and the page no longer scrolls back to the top after completing a reorder.
- We have applied a solution to ensure that Table View enforces language-role restrictions for localized string fields when LANGUAGE_ACCESS_ENABLED = true. Table View now correctly applies language-based access permissions as follows:
- ReadWrite – The language column is visible and editable.
- Read – The language column is visible but read-only.
- No Access – The language column is hidden and is not displayed in the table.
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.