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 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 so that the Control Center now provides an enhanced HasFieldUsingMultivalue method. This improvement optimizes the handling of the Multivalue property for Field Types, delivering more efficient and reliable performance when enabling or disabling multivalue configurations within the Control Center.
Brand Store v2
-
It has been implemented so that the Brand Store now operates under the cataloghub.com domain, replacing the previous *.inriver.io domain, effective November 5.
What’s changing?
Brand Store URLs now use the cataloghub.com domain, providing a clearer, more recognizable, and user-friendly destination for accessing and browsing product content.What about existing links?
All existing *.inriver.io links automatically redirect to the new cataloghub.com domain, ensuring uninterrupted access and maintaining compatibility with existing bookmarks or integrations.Do I need to do anything?
No action is required. After November 5, users and administrators can begin referring directly to cataloghub.com for Brand Store access.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the REST API correctly performs Parent/Child CVL validation when creating entities via REST. Previously, the validation process did not account for the selected fieldset and instead validated against unrelated parent fields, which could result in entity creation failures.
We have applied a solution to ensure that entity listener messages generated during Excel imports correctly display the username of the importing user, rather than defaulting to “system.” Previously, the context username could intermittently revert to “system” before the listener events were created, resulting in inaccurate audit attribution.
We have applied a solution to ensure that CVL error log messages display with correct spacing and formatting. Previously, inconsistent spacing caused log messages to appear misaligned, impacting readability. This improvement enhances the overall user experience by providing clearer and more structured error log outputs.
Workflow
We have applied a solution to ensure that users can access the Create Workflow function without encountering errors. Previously, an issue in the workflow initialization process could prevent users from opening the Create Workflow interface, disrupting workflow configuration. This fix ensures stable access and a smoother user experience when creating new workflows.
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.