Sections in the article
Inriver is moving toward smaller, more incremental releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver can improve release quality and transparency and identify and mitigate erroneous behavior 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 accounts holding the APIManageUsers permission can update a user's first and last name through the REST API, using the new endpoint version PUT /api/v1.0.1/system/users/{username}. Previously, changing a user's name via the API required the Administrator role, even though the same permission already allowed creating, deleting, and re-permissioning users.
Please note! This improvement is only available in the new endpoint version. The previous version, PUT /api/v1.0.0/system/users/{username}, is unchanged and continues to require the Administrator role for name changes, so existing integrations are not affected.
- It has been implemented so that the Assignment Panel can switch between assignments for the current entity and user assignments when opened in an entity view. Selecting an entity workflow assignment displays its instructions without navigating away from the current entity. The assignment toggle is only shown when the current entity has one or more entity workflow assignments. If there are none, the existing user-assignment list is shown without the toggle.
Shopify Adapter
- It has been implemented that Client Assertions are now used instead of unexpiring tokens, in preparation for the deprecation of unexpiring tokens effective January 1, 2027.
- It has been implemented that metafield support now includes variant references, enabling improved handling and synchronization of variant-related metafield data.
- It has been implemented that exports gracefully handle lists exceeding Shopify's 128-item limit. The first 128 items are exported, and a warning is added to the Warnings and Errors report indicating that the limit has been exceeded.
- It has been implemented that additional security hardening measures have been introduced to strengthen the overall security posture of the solution.
- It has been implemented that Shopify's security scanner is integrated into the CI/CD pipeline to enable automated security checks as part of the development and deployment processes.
- It has been implemented that IP whitelisting is now supported in Inriver's Shopify App, providing an additional layer of access control and security.
Please see below for the deployed bug fixes:
General
- It has been implemented that, in plan and release, when a user saves a query without selecting an entity type, a red indicator appears. Before the red indicator was visible before save.
- We have applied a solution to ensure that fields marked as read-only for a specific language under a user's Language Role can no longer be modified through a Supplier Onboarding file import. Previously, importing a file that only touched such a read-only field could incorrectly mark that row as invalid; these rows are now correctly recognized as having no changes.
- We have applied a solution to ensure that deleting a field type through the REST API no longer fails with an internal server error when the field type has a large number of values or a long revision history. Field types that are used in entity type search hints or field views can now also be deleted. If a field type is still used by Print display information or Print field value mappings, the delete is now rejected with a message that explains what to remove first, and none of its data is removed. If deleting a field type with a very large amount of data does not finish in time, a message now asks you to delete the field type again to finish the delete.
- We have applied a solution to ensure that PUT /api/v1.0.0/links/sortorder only updates links whose position changes. Links already at the requested position are no longer saved and no longer trigger link update events, extensions, or a main picture recalculation, so resending an unchanged order no longer re-triggers any updates.
- We have applied a solution to ensure that Child CVL filter options are dynamically populated based on the selected Parent CVL filter values, excluding unrelated Child CVL values while retaining unset values under the Not Set option.
- We have applied a solution to ensure that users without the ManageWorkflows permission can reorder and move their work areas in Enrich, and the new arrangement is saved and kept after refreshing the page.
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.