sections in the article
inriver is moving towards more incremental, smaller releases to be able to accommodate our customers in a better and faster way. 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.
Please see below for the deployed features and improvements:
Workflows:
- Users will now be redirected to a new Dashboard on the main homepage, displaying their assignments. The Assignment Dashboard will present the context of each assignment—personal, role-based, or team-related—enabling a quick understanding of task scope and relevance. Assignments will be displayed in a table format for easy sorting and management.
- For our workflow creators, a new trigger based on the internal event that is called: 'EntitySegmentationChanged' has been added to the workflow builder application.
- For our workflow creators, you can now define Plan & Release as a workspace for individual assignments, and the assigned user will be redirected to Plan & Release by clicking an assignment link on the dashboard or in the top right corner.
- For our workflow creators, you can now define Evaluate as a workspace for individual assignments, and the assigned user will be redirected to Evaluate by clicking an assignment link on the dashboard or in the top right corner.
Additional release notes:
- It has now been implemented so that setting a null value to a LocaleString object at the Field level of the Entity is blocked to prevent creating a FieldRevisionHistory entry, and an error prompt will inform users that a null value for a LocaleString object is not allowed.
- For our Syndicate Plus users, it has now been implemented so that only relevant types are filtered out on the Trading Partner screen.
-
For our Syndicate Plus users, it has now been implemented so that collections can be sorted by name.
-
For our Syndicate Plus users, it has now been implemented so that collection names must be unique.
Please see below for the deployed bug fixes:
-
We have applied a solution to ensure that relevant fields are displayed when the Custom workspace is selected in the Portal, aiming to enhance user experience.
- We have applied a solution to ensure that when a work area folder is created with two conditions using dataCriteriaOperator 'Or', the REST API endpoint correctly retains the dataCriteriaOperator as "Or" to mitigate the unreliable nature of the endpoint for users.
- We have applied a solution to ensure that in the portal, the character counter for a LocaleString field remains visible even after the field has been deselected, aiming to improve user experience.
- We have implemented a solution to ensure that, for Syndicate Plus users, a product image is displayed in the product view even if the first SKU lacks an image.
- We have applied a solution to ensure that, for Syndicate Plus users, input validation is added for text fields in the A+ Content module.
- We have applied a solution to ensure that in Enrich, the completeness window's responsiveness is updated relative to the window size, preventing it from being cut off when opening tabs.
- We have applied a solution to ensure that in Enrich to ensure that when working with mass updates on Date/Time fields, if a value is null, it is displayed as empty, enhancing user experience.
- We have applied a solution to ensure that when a user clicks on 'Show all' under 'Tasks assigned to me' in Planner, it displays all tasks assigned to the user, addressing the issue where the query with 'Contains all' clause previously skipped tasks assigned to other users.
-
We have applied a solution to ensure that in Enrich, users can now export the list of MultiSearch results from the left side frame even when some searched entities are not found.
-
We have applied a solution to ensure that in Enrich, the Work Area Title displays clean text instead of HTML-encoded content, improving user experience.
inriver Implementation Standards
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
7 comments
I feel this one is a breaking change:
Unless I misunderstand the change... But from what I understand, if there are connectors out there setting a null value to a LocaleString field, it will now throw an error!? If so, how do we clear/reset a LocaleString field value, by emptying all locale values?
You could set the field value to an empty new LocaleString vs null.
David Kraft I know we can set an empty LocaleString value 🙂 What I worry about is that before this change, it was possible to set a null value to a LocaleString field, and now it seems it's no longer allowed, hence the breaking change.
Agreed on the concern, would be nice to have advanced notice on changes like this so impact can be assessed ahead of time.
So based on what I've gathered, setting the LocaleString field value to null is possible when it's done via API integration.
But it's supposed to throw an error when it happens. From a customer's point of view, if it's blank, it means that the value is null. And yes, it should be possible to reset/clear the value by just emptying each locale value.
Hope this makes it a bit more clear!
What is "the Custom workspace" that is referred to here:
"We have applied a solution to ensure that relevant fields are displayed when the Custom workspace is selected in the Portal, aiming to enhance user experience."
Torbjorn Stavas; sorry for the delayed response. I hope this clears up the question you asked:
Customers and partners can create Custom Workspaces to enhance product capabilities for specific needs. While the workflow builder provides extensive configuration options, Custom Workspaces offers flexibility when standard configuration is insufficient. Default workspaces are available to all, and custom workspaces can be created using Workspace Templates, similar to Application Templates.
Please sign in to leave a comment.