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.
Please see below for the deployed features and improvements:
- It has been implemented that a new workflow trigger, titled "Completeness Rule Complete", has been introduced. This trigger allows for the automated assignment of entities to specific user assignments contingent upon satisfying predefined completeness rules. When the designated completeness criteria for an entity are fulfilled, the workflow will be activated, streamlining the process of managing entity assignments by these rules.
NB! If a completeness rule becomes stuck, this trigger will not function as intended. It is important to communicate this limitation to users to avoid confusion and prevent erroneous bug reports related to the trigger when the underlying issue is with completeness rules.
Additionally, completeness rules of the type "Relations Group Completed" are currently not functioning as expected (refer to the test summary), and this trigger should not be used for those specific completeness rules.
- It has been implemented that the Workflow Summary Email has been redesigned for improved clarity. Users will now receive the email 10 minutes after any workflow trigger is initiated, providing a clear and concise summary of workflow activities for better insight and quicker decision-making.
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that the workflow creation and management functionality is fully operational for all users with the relevant permissions in our system. Specifically, the issue where certain users were unable to create workflows has been resolved. Additionally, we have addressed the limitation that previously prevented users with long usernames from creating or updating workflows. These fixes have been implemented to enable seamless workflow management for all eligible users moving forward.
- We have applied a solution to ensure that the Field Mapping details view in Syndicate Plus now functions as expected. The bug that occasionally caused the source field to not display correctly has been fixed. This update ensures that all source field data is accurately presented in the Field Mapping details view, improving the overall user experience and data accuracy within the system.
- We have applied a solution to ensure that in both Enrich and Excel Import when an entity field value is updated with track changes enabled, a field revision history is automatically created for the previous value if it does not already exist. This fix guarantees that the historical data is preserved, preventing the loss of previous field values during updates, thereby maintaining a complete and accurate revision history for each tracked change.
- We have applied a solution to ensure that the handling of old field values in the supplier onboarding process has been improved. Specifically, in the Portal, we have fixed the mechanism by which the old field values are saved in the supplier import history following the approval of supplier import data. This enhancement guarantees that the FieldDataBefore column in the History Excel Export will no longer contain any blank data, thereby providing a complete and accurate record of prior field values.
- We have applied a solution to ensure that when navigating within the browser, clicking links in work areas will now correctly direct users back to the previously opened page, rather than reverting to the main Enrich page. This enhancement improves the user experience by preserving the context of navigation, allowing for more efficient workflow and continuity when managing tasks within the application.
- We have applied a solution to ensure that when attempting to delete a field type currently in use within a notification, a popup will now be displayed. This popup prevents the deletion of the field type and informs the user of which notifications are currently utilizing it. This enhancement improves system usability by preventing accidental deletions and providing clear visibility into dependencies, thus facilitating better management of field types within notifications.
- We have applied a solution to ensure that the Excel Import feature within the Entity Data Model now correctly starts the Field Revision number at 1 for the first update of the LocaleString field, rather than 2. This fix addresses the issue of not properly recording the second field revision, thereby ensuring accurate tracking of all field updates. As a result, users can expect a complete and consistent revision history for LocaleString fields, enhancing data integrity and auditability in the system.
- We have applied a solution to ensure that the Excel Import process operates correctly even when the parent CVL is restricted to certain roles. Now entities will be updated successfully, regardless of user restrictions on specific fields. The import process will now appropriately ignore any restrictions as long as the restricted fields are not being updated.
-
We have applied a solution to ensure that the issue of the page scrolls back to the top after removing a link in Enrich has been resolved. Specifically, after expanding the "Show All" option and scrolling down, the page will now retain its scroll position following link removal. This fix enhances the user experience by providing a smoother, more user-friendly interaction, thereby reducing inefficiencies and improving workflow management within the Portal/Enrich environment.
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.