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:
- It has been implemented so workflow assignees can view their assignments in a table format. This feature allows for easy sorting, management, and an overview of tasks based on criteria such as due date, priority, status, and associated entities. The table view aids in quickly assessing and managing workloads within a structured and familiar layout.
- It has been implemented so workflow creators can define Evaluate as a workspace for an individual assignment. Additionally, upon clicking an assignment link (either in the top right corner or on the dashboard), a workflow assignee will be redirected to Evaluate.
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that regex validation is included during the "Copy Entity" process in Enrich. Regex validation is now also implemented on the entity details page during manual updates.
- We have applied a solution to ensure that entity cards in a work area are now marked with a blue overlay, making it easier to identify the selected item.
- We have applied a solution to ensure that the tooltip for the Default Segment in workflows is now visible.
- We have applied a solution to ensure that when the entity history is open, the highlighted text no longer states 'Open history' but instead 'Close history'.
- We have applied a solution to ensure that the "Select All" function now works correctly for large queries, even when reaching 200,000 records. Additionally, we have implemented validation for saving within the work areas. By design, our workspace can save up to 10,000 entities at a time. Furthermore, validation has been added to prevent saving more than 10,000 records, thus avoiding potential issues.
- We have applied a solution to ensure that the LocaleString History now correctly reflects updates. This fix addresses the issue caused by the presence of null values in the [Value] column of the FieldRevisionHistory.
- We have applied a solution to ensure that TrackedChanges for FieldTypes with data types String and XML, including those with special characters or NULL values, are now properly managed. This fix addresses issues related to \r\n or \n values and prevents the creation of unnecessary new field revisions when the previous revision was system-generated.
- We have applied a solution to ensure that filter field types in the Content Store are optimized.
- We have applied a solution to ensure that, as a user in the Portal, the CVL keys are now case-insensitive during the supplier onboarding process. This update applies to both the validation stage and entity import via the approval tab.
- We have applied a solution to ensure that notifications for workflow assignments are also sent when the assignee is specified as only a role.
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
0 comments
Please sign in to leave a comment.