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 users can now open a workflow in a read-only viewer for a specific entity (e.g., a product) to see which step it is currently in, making it easier to understand where the entity sits in the process without risking accidental changes. Additionally, the workflow viewer now includes history insights with simple charts that show enrichment time trends (median and p90) and distribution of enrichment times, helping teams monitor workflow execution, identify bottlenecks, and analyze historical performance.
It has been implemented to improve usability on smaller screens by introducing responsive logic that toggles the right-hand panel on the Entity Details page, enabling smoother navigation and more efficient access to content in constrained viewports.
It has been implemented to improve overall performance and efficiency in the specification field retrieval and processing, resulting in a more responsive and stable experience.
It has been implemented so that the Control Center’s new UI provides clear visual indication of the currently selected role within the user role assignment dropdown
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the Append, Remove, and Replace options are correctly displayed in the Mass Update feature of the New UI, restoring full functionality for bulk data operations.
We have applied a solution to ensure that the missing view management icons are restored in the New UI Planner, re-enabling the ability to open, define, and save views directly.
We have applied a solution to ensure that users with the EnableManualWorkflowTriggering permission can manually trigger workflows, streamlining workflow execution while maintaining proper access control.
We have applied a solution to ensure that the selected workspace is retained when navigating between entities, providing a consistent and uninterrupted user experience.
We have applied a solution to ensure that the default icon for the Custom Template option in the sidebar navigation is updated, improving user interface consistency and enhancing overall navigational clarity.
We have applied a solution to ensure that the table’s pagination buttons are correctly positioned within the view area.
We have applied a solution to ensure that Work Area Table View filters and column settings are preserved when switching between work area tabs, with filters cached and automatically restored when returning to a previously opened work area.
We have applied a solution to ensure that the 'Rename Fields' functionality in the New UI Content Store correctly displays field mappings.
We have applied a solution to ensure that the tooltip values in the entity card view are correctly displayed, enhancing accessibility and providing accurate contextual information.
We have applied a solution to ensure that sub-menu options consistently reflect the actions relevant to the current context, improving navigational clarity and overall user experience.
We have applied a solution to ensure that the completeness section on the right toolbar in the entity view is hidden when no completeness rules exist, improving interface clarity.
We have applied a solution to ensure that scrolling with the scrollbar in the Mass Update dialog of the New UI no longer dismisses the DatePicker, providing a smoother and more predictable user interaction.
We have applied a solution to ensure that scrolling functions correctly within the Specification Template in the New UI, restoring full navigational capability and improving user experience.
We have applied a solution to ensure that LastLoginDate is correctly displayed and tracked for users, including those authenticated through Auth0.
We have applied a solution to ensure that Excel imports preserve string values containing DateTime formats, preventing automatic conversion to date format.
We have applied a solution to ensure that all forbidden characters are correctly removed during Excel export, maintaining data consistency.
We have applied a solution to ensure that duplicate keys can no longer be saved in FieldType settings. Validation has been added to block users from adding or renaming settings to a key that already exists, displaying a clear error message instead of causing a 500 error and an inability to load the entity list.
We have applied a solution to ensure that CVL fields without initial values are included in the Excel export output, restoring completeness and consistency of the exported data.
We have applied a solution to prevent an error message from appearing when navigating to an entity after a new field type has been added through the Control Center.
We have applied a solution to ensure that duplicate restricted fields are not added to the list when validation fails in the Control Center - Restricted Fields management page, preventing misleading UI states and ensuring data consistency.
We have applied a solution to ensure that EnrichPDFTemplate updates in the Control Center/Remoting API no longer set LocalizedName values to null, preserving existing data and maintaining template integrity.
We have applied a solution to ensure that the SSO domain name is visible on the SSO Configuration page when using the new UI in Control Center. Previously, the domain text appeared invisible due to a font color matching the white background.
We have applied a solution to ensure that "Cache-Reloaded" log entries in the RestAPI are correctly attributed to the environment where the cache reload occurs, instead of incorrectly showing log entries belonging to other environments. Additionally, the log source has been corrected from "WebPortal" to "RestAPI" for accurate module attribution.
We have applied a solution to ensure that the `entities:fetchdata` REST API endpoint returns field values correctly, regardless of the order of requested objects in the `objects` parameter.
Syndicate Advance
We have applied a solution to ensure that the BeforeAfter function in Syndicate Advance no longer introduces a leading space in the “Before” value when no delimiter is defined, ensuring correct string formatting and output consistency.
We have applied a solution to ensure that the start page styling in Syndicate Advance properly accommodates long trading partner names, improving readability and overall visual consistency in the redesigned interface.
Expression Engine
We have applied a solution to ensure that completeness rules of type "expression" cannot be created when the expression engine is not enabled in the environment, enforcing proper validation and preventing invalid configurations.
We have applied a solution to ensure that expressions are correctly triggered during Excel updates, even when the associated expression field is restricted, restoring expected behavior in the expression engine.
We have applied a solution to ensure that the quick search index is automatically rebuilt following Excel imports when Display Description is generated via the Expression Engine, maintaining accurate and up-to-date search results.
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.