sections in the article
inriver is moving towards more incremental, smaller releases to accommodate our customers better and faster. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release 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 word and character counts are now displayed for locale string entries within the Enrich module. Specifically, word counts have been added to the locale string controller, and both word and character counts are shown for locale string list view items.
- It has been implemented that in the Control Center, within the Entity Type View, when editing a field and navigating back to the entity type, the Fields datagrid will automatically return to the previously opened page.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that error handling is properly implemented when deleting a Configure Link Rule in the Plan & Release module.
- We have applied a solution to ensure the properties parameter is properly validated when creating or updating HTML templates via the REST API. This fix prevents the properties parameter from being null or empty, addressing a previous issue where templates with an empty properties parameter were stored as NULL in the database. As a result, these templates would not appear in the Portal unless manually edited and saved in the Control Center.
- We have applied a solution to ensure that when the server setting DISABLE_CONTENT_SEGMENTATION_FOR_NODES is enabled, the linked entities to a node remain consistent with each run of the Update Link Rule Definitions job in the Control Center. Previously, enabling this setting could result in inconsistent linking of entities across job executions. This fix ensures stable and predictable behavior, maintaining data integrity and alignment between nodes and their linked entities.
- We have applied a solution to ensure that vertical scrolling is properly enabled in work areas under the Plan & Release module
Brand Store
- We have applied a solution to ensure that in Brand Store, changes to referenced products do not affect the return value directly. To maintain output integrity, a new variable has been introduced to handle modifications separately.
Syndicate Plus
- We have applied a solution to ensure that inbound mappings consistently display as expected in Syndicate Plus.
inriver's ambition is to collaborate with our partners in providing our customers with as safe and secure a PIM system as 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.