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.
Welcome to the new Inriver UI
The new Inriver UI is now your default experience. It’s designed to help you work with greater focus, clarity, and efficiency.
If you’re not ready yet, you can switch back to the legacy UI at any time using the toggle in the User Details menu, as seen below.
Please see below for the deployed features and improvements:
General
It has been implemented so that Single Entity Details now respect field-level customizations, including CVLs and Boolean fields. The new UI supports configurable colorful CVLs and Boolean display styles. These settings are consistently reflected in both the Table View and the Overview Page, ensuring uniform rendering across interfaces.
It has been implemented so that performance related to expression retrieval and entity creation operations has been improved, resulting in faster processing times and enhanced operational stability.
It has been implemented so that when the user is configuring their export, a warning will show if the export may take longer due to the number of fields and entities selected.
It has been implemented so that a role dropdown has been added to the target environment selection, enabling users to define a default role. This enhancement also allows users to select a default role when triggering a self-service copy, ensuring consistent role assignment during the operation.
Inspire
It has been implemented so that Inspire now supports adding document resources as context data for text generation, in addition to images. Supported formats include PDF, DOCX, XLSX, PPTX, TXT, and CSV.
Document context usage is opt-in and must be explicitly enabled.It has been implemented so that image thumbnails in Inspire Apps now open a full-size preview using the same modal component as the Details tab. This ensures a consistent image viewing experience without requiring users to navigate away from the application.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that query filters in the Portal Query Editor now work correctly for nested multi-level CVL fields across all hierarchy levels.
We have applied a solution to ensure that derived classes inheriting from RestfulField have their properties correctly deserialized during JSON processing. This fix also resolves issues with the UpdateApproach property in mass update operations.
We have applied a solution to ensure that when a task is selected in the Portal with the New UI enabled, the corresponding task details content is correctly displayed.
We have applied a solution to ensure that, with the New UI enabled, the red dot indicator for entity comments is consistently displayed when returning to a previously selected entity that contains comments.
We have applied a solution to ensure that, with the New UI enabled, closing one side of a split view no longer triggers an unintended refresh in the remaining pane.
We have applied a solution to ensure that, with the New UI enabled, explicit width and height values are defined for toggle icons in the Enrich and Plan & Release modules. This resolves visual inconsistencies observed in Safari on macOS and improves overall rendering consistency and user experience.
We have applied a solution to ensure that, with the New UI enabled, short CVL values in Enrich no longer cause the dropdown to render horizontally and disrupt layout alignment. Component styling has been updated to maintain proper alignment and spacing.
We have applied a solution to ensure that, with the New UI enabled, the Entity Detail page no longer resets to the top of the page after saving changes, preserving the user’s scroll position and improving workflow continuity.
We have applied a solution to ensure that, with the New UI enabled, the System Info click handler invokes the correct function. Previously, the handler always triggered the parent node’s System Info; it now correctly executes the corresponding handler for child nodes.
We have applied a solution to ensure that, with the New UI enabled, the ShowInEntityOverview setting for the Overview page supports any valid string value, enabling more flexible configuration and consistent rendering behavior.
We have applied a solution to ensure that, with the New UI enabled, textbox field type names are properly hidden in Enrich within the Entity Details view, aligning the display with the intended UI design.
We have applied a solution to ensure that, with the New UI enabled, newly selected entity icons from the Icon Picker are displayed correctly on the Dashboard, restoring consistent and accurate icon rendering.
We have applied a solution to ensure that, with the New UI enabled, the "Remove From Work Area" button is available in the Work Area. This restores the ability to remove multiple items in card view, addressing the previously missing bulk removal option.
We have applied a solution to ensure that, with the New UI enabled, the scroll bar in Enrich Entity Details no longer automatically scrolls upward after image loading, preserving the user’s current position and ensuring a stable viewing experience.
We have applied a solution to ensure that, with the New UI enabled, selecting a task in the Portal correctly displays the associated task details content.
We have applied a solution to ensure that, with the New UI enabled, Completeness values no longer truncate names, preserving full text display and ensuring accurate presentation of information. A tooltip has also been added to provide clear visibility of the complete value where applicable.
We have applied a solution to ensure that, with the New UI enabled, the multi-search dropdown no longer displays missing items and is no longer subject to layout overlap issues, restoring complete and properly aligned dropdown rendering.
We have applied a solution to ensure that, with the New UI enabled, the "Not found (xx)" message is no longer displayed when switching to a new Work Area tab, preventing the persistence of outdated or irrelevant status indicators.
We have applied a solution to ensure that, with the New UI enabled, the multi-search dropdown displays the correct items when used in split view, restoring accurate and consistent search results across layouts.
We have applied a solution to ensure that, with the New UI enabled, the resource display name is visible by default without requiring the user to hover over the resource, improving clarity and accessibility.
We have applied a solution to ensure that, with the New UI enabled, UI overflow caused by long Work Area titles and multi-search queries is resolved, ensuring consistent and stable layout rendering.
We have applied a solution to ensure that, with the New UI enabled, change detection and state handling correctly activate the Save button when specification settings are modified. As a result, users can successfully edit and save specification settings in both the Old UI and New UI without needing to revert changes.
We have applied a solution to ensure that, with the New UI enabled, the Save button correctly activates when a Specification Template is added or updated. As a result, users can add, update, and save Specification Templates directly in the New UI, aligning the behavior with that of the Old UI.
We have applied a solution to ensure that, with the New UI enabled, permission checks are enforced to disable the Publish, Unpublish, Rebuild, and Synchronize buttons for unauthorized users. Additionally, permission validation has been implemented within each corresponding function as a safeguard, ensuring secure execution even if UI-level restrictions are bypassed.
Print 2.0
We have applied a solution to ensure that, in Print 2.0, prints using the ShowDuplicate functionality no longer result in missing items, restoring complete and accurate output generation.
We have applied a solution to ensure that, in Print 2.0, the FormatDecimal formula now supports custom thousands separators, enabling more flexible and locale-specific numeric formatting.
We have applied a solution to ensure that, in Print 2.0, the Concatenate formula functions correctly when loading data from publications, restoring accurate data processing and output generation.
We have applied a solution to ensure that, in Print 2.0, data is correctly synchronized in all relevant scenarios, resolving cases where certain data was previously not properly updated or reflected.
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
6 comments
What does this bullet in the release note mean in practice?
It has been implemented so that a role dropdown has been added to the target environment selection, enabling users to define a default role. This enhancement also allows users to select a default role when triggering a self-service copy, ensuring consistent role assignment during the operation.
Can you give more detail on this
It has been implemented so that a role dropdown has been added to the target environment selection, enabling users to define a default role. This enhancement also allows users to select a default role when triggering a self-service copy, ensuring consistent role assignment during the operation.
Thank you
Hi Beth Ryan & Anette Olofsson - In practice, this means users can now select a default role in the copy UI.
If, during a self-service copy, a user cannot be matched to any role in the new role structure, the system will assign the selected default role instead. This value is passed to the runbook as DefaultRoleName.
Previously, users were assigned the Reader role by default, but since that role and its permissions can be deleted, copies could fail. This change prevents that by ensuring a valid fallback role is always defined.
Hope this answers your questions!
Best Regards
//Helena Gerebro
Sr Engineering Manager
Hi Helena Gerebro
Has the self-service copy been changed to also include coping users? Previously users have NOT been copied when using self-service copy, when inriver made the copy the users were copied in full. That is also what is documented:
https://community.inriver.com/hc/en-us/articles/14506516381212-Introducing-Self-Service-Database-Copies
Can you please clarify this a bit more, thanks! :)
Regards
Peter
Hi Helena Gerebro,
Do you have any feedback to Peter Norlander (ICP) question regarding users when copying between environments?
Is it that the user isn't copied, but the users roles are copied from the source environment?
// Kind regards, Torbjörn
Torbjorn Stavas - Sorry for my late response!
The default behavior is to copy only the roles (this is also the approach used via self-service). The users in the destination environment are retained, and the system attempts to match them to the newly copied roles as accurately as possible. However, during the copy process, it should be possible to specify whether the users should also be copied over or not.
Cheers
//Helena
Please sign in to leave a comment.