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 the locale string editing modal now remains open after saving, enabling users to seamlessly edit multiple locales without the need to reopen the modal. This enhancement eliminates unnecessary clicks, thereby improving usability and enhancing overall efficiency for customers working with multiple language layers.
NB! This represents a behavior change based on feedback.
- It has been implemented that, as a user in the Control Center, when selecting the number of visible entries in the Logs section, additional options of 100 and 1000 entries are now available.
- It has been implemented that, in the Portal, fields retrieved from the backend are now filtered by the FieldSet. This optimization reduces the amount of data transmitted from the server to the client browser, improving performance.
- It has been implemented that the width of input fields has been increased to provide more space for user input when adding or managing extensions. This enhancement improves usability by ensuring better visibility of entered data.
- It has been implemented that the "Reload Cached Model in Web Portal" button has been removed from the Portal.
Expression Engine
- It has been implemented that the Expression Engine has been updated to align the behavior of the AddEntities method with AddEntity in terms of expression handling. This enhancement ensures consistency in entity addition processes.
- It has been implemented that, in the Expression Engine, the Apply Expression job cannot be executed unless the current Control Center user is also added as a user in the PIM environment, as it modifies entity data. To address this, an error message has been introduced to clearly explain why the job cannot be run, improving user awareness and troubleshooting efficiency.
Workflow
- It has been implemented that, in the Workflow Overview Page, the Trigger column now displays names instead of IDs (e.g., "Entity Created" instead of "EntityCreated"). Additionally, the Changed By column now shows the full name of the user instead of their email address.
Inspire
- It has been implemented that, in Inspire, faster evaluation response times are now provided when assessing entity data against its matching sub-configuration in the Details tab.
- It has been implemented that, in Inspire, a low token warning is now displayed in the right drawer app once the customer's remaining Inspire tokens fall below a defined threshold. This feature helps to proactively notify users of token depletion, allowing them to take necessary actions before running out of tokens.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that opening an entity in a duplicated browser tab no longer results in the loader getting stuck and an error is thrown. This fix resolves the issue by improving the handling of duplicate tabs, ensuring smooth functionality, and preventing errors from occurring.
- We have applied a solution to ensure that, in Enrich > Tasks and Notifications, when a user searches a query from the notifications, they are properly redirected to the corresponding query results.
- We have applied a solution to ensure that, in the portal, right-click pasting into entity text fields now correctly triggers events such as updating the character count and displaying the save button. This fix ensures that the user interface responds as expected when pasting content.
- We have applied a solution to ensure that, in Supplier Onboarding's Approve Tab, the fieldTypeId and pending-status-switch containers remain visible after updating a locale string field and switching tabs. This fix resolves the issue where these elements are hidden, allowing users to efficiently approve or reject locale string updates.
- We have applied a solution to ensure that, when deleting a canceled job from the jobs dropdown in the portal, the error dialog stating "Could not delete card" no longer appears. This fix resolves the issue, allowing users to delete canceled jobs without encountering errors.
Brand Store
- We have applied a solution to ensure the brand store efficiently handles the optimized bulk email invitation process. When publishing a store with hundreds or thousands of users, this solution addresses potential performance bottlenecks and ensures seamless email distribution.
Workflow
- We have applied a solution to ensure that, in Workflow, quote characters are now displayed in the configuration name input field tooltip. This fix improves clarity and provides better guidance to users when entering configuration names.
- We have applied a solution to ensure that, in Workflow, truncated text on images displayed on smaller to medium screens will now show a tooltip with the full text upon hovering. Additionally, the text will revert to its normal, fully visible state on larger screens, improving readability and user experience across different screen sizes.
- We have applied a solution to ensure that, in Workflow, the "Build a New Workflow" button is now disabled when the workflow limit is reached. A tooltip has been added to inform users that they have reached the maximum allowed workflows, providing clearer guidance and preventing further attempts to create additional workflows.
Inspire
- We have applied a solution to ensure that, in Inspire, language data is generated correctly if a user has another data language set. This fix ensures that language-specific data is consistently generated and displayed based on the user's selected language, improving accuracy and user experience.
- We have applied a solution to ensure that, in Inspire, the CVL result is now generated correctly when inspiring a CVL field, even if the data language is not set to English. This fix resolves the issue where incorrect results were displayed
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
2 comments
Regarding "We have applied a solution to ensure that, in Workflow, the "Build a New Workflow" button is now disabled when the workflow limit is reached":
What is the maximum number of workflows and/or does it depend on license?
Hello Anssi Raittila Anssi Raittila the limit is 20 workflows per customer enviroment.
If you have a need of additional workflows we from Product Management would like to speak to you and understand your use case. How the amount of workflows relate to your license I can't answer here. Please reach out to your Customer Success Manager and we can continue that conversation if needed.
Thank you
Ruy Ramos
Please sign in to leave a comment.