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 behaviour 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 permanent customization of table view templates is supported, enabling users to reorder columns and have that order persist across refreshes. Column widths are saved and maintained to ensure the layout remains readable and stable over time. Workflow-specific field prioritization is preserved and is not overridden by default configurations.
It has been implemented to update the search button label from “Update…” to “Update search query…”, providing clearer instructions to users and improving overall usability.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the tab context menu no longer overlaps or stacks when triggered. The context menu behavior has been updated to prevent rendering conflicts within the tabs area, resulting in a clean and unobstructed interface.
We have applied a solution to ensure that saved workspaces in the table view correctly retain the configured column ordering, maintaining a consistent and expected layout when the workspace is reopened.
We have applied a solution to ensure that attributes hidden at the category level are no longer visible or selectable within the table view, enforcing proper visibility rules and maintaining configuration consistency.
We have applied a solution to ensure that work area tabs are no longer obscured by the sidebar and that their labels are fully visible, improving layout integrity and usability.
We have applied a solution to ensure that the random “unexpected error” pop-up messages encountered when opening an entity in the Portal Enrich module no longer occur. The issue was caused by intermittent 500 errors from the /api/entityOverview/{entityId} endpoint and has now been resolved
We have applied a solution to ensure that Portal Template–based custom widgets are evaluated consistently with Dashboard Widgets when determining the dashboard empty state in the Portal Dashboard. If all Default, Custom, and Portal Template widgets are disabled, the empty state message box is displayed; if any of these widget types are present, the empty state message box is not shown.
We have applied a solution to ensure that the inriver logo is correctly included in assignment emails, maintaining consistent branding and presentation.
We have applied a solution to ensure that clear and actionable error feedback is displayed when deleting a FieldType from the EntityType page in Control Center. If the deletion fails, a dedicated error dialog is now shown to surface backend errors to the user, aligning the behavior with the dedicated FieldType page and improving consistency, transparency, and overall usability.
We have applied a solution to ensure that duplicate entries are no longer generated in workflow history, maintaining consistency with assignment records and improving the accuracy and clarity of workflow tracking.
Expression Engine
We have applied a solution to ensure that the ApplyExpression job in the expression engine executes correctly for entities whose fieldset expression evaluates to NULL, preventing job failures and ensuring consistent processing behavior.
Inspire
We have applied a solution to ensure that child CVLs are correctly generated even when their parent CVL is created in an earlier workflow step. Parent and child CVLs can now be generated across separate workflow steps as expected, ensuring proper dependency handling and workflow consistency. This fix is implemented in the Inspire Generate Agent.
We have applied a solution to ensure that the Inspire Review button is displayed only when filtered cells are successful, improving interface accuracy and preventing inappropriate or unavailable actions.
We have applied a solution to ensure that translation fields are correctly handled within the Inspire configuration, enabling accurate localization and consistent behavior across all supported languages.
We have applied a solution to ensure that CVL values are correctly handled in the Inspire table view by enhancing the DynamicGrid and CvlCellEditorOptions.
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.