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 releases and identify and mitigate any erroneous behaviour 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 Customer Admins in Control Center can elevate Customer Users to Customer Admin directly from the User Management module, without needing to submit a support ticket.
Please note! This feature is only visible if the logged-in user has the Customer Admin role.
It has been implemented that the workspace delete confirmation message in the workflow module now includes a scroll bar when the workspace is used in multiple workflows, preventing the dialog from overflowing the screen.
Inspire
It has been implemented so that, within Inspire Table View, the generation of child CVL values is blocked when the corresponding parent CVL field is unset.
It has been implemented so that the Inspire enables multi-field product enrichment via conversational AI, populating multiple attributes simultaneously, leveraging entity context and attached file guidelines to understand your product's data model and respect field constraints.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the Save button remains disabled until actual changes or updates are made to entity details.
- We have applied a solution to ensure that the node ordering in Plan & Release is correctly preserved after dragging and dropping nodes and refreshing the page.
- We have applied a solution to ensure that if an Excel file has a LocaleString field column with a locale that the environment doesn't have, the field will not be automatically mapped to the first existing locale in alphabetical order. Instead, the mapping will remain unset, requiring the user to manually select the correct field type or locale.
- We have applied a solution to ensure that a Link Entity in Enrich can be saved even when fields are empty or contain only their default value.
- We have applied a solution to ensure that the unintended scrolling behavior, where the page would jump to the top during image loading, is resolved.
- We have applied a solution to ensure that updates to the channel node link rule operator can be modified as intended and that all configuration changes are correctly persisted upon saving. This resolves the issue where modifications were not retained, ensuring consistent behavior in Plan & Release.
- We have applied a solution to ensure that workspace configuration changes can only be saved by users with the appropriate permissions. Users without the required authorization are now presented with a clear validation message indicating insufficient privileges to save a new workspace configuration.
- We have applied a solution to ensure that CVL formatting from the dynamic grid component is consistently applied to the dynamic relations preview grid.
- We have applied a solution to ensure that the display of CVL values remains consistent between Table View and Entity Details when CVL data for a fieldset is modified. This addresses discrepancies that could arise when existing records reference outdated or invalid CVL values. The update is limited to presentation-layer alignment; no changes have been made to data validation or CVL data handling.
- We have applied a solution to ensure that only a single active listener is registered for opening the Query Editor. Previously, multiple listeners could trigger duplicate modal openings simultaneously. Although only one modal became visible (as opening a modal closes others), the duplicate triggers caused conflicts and slowed down the Query Editor initialization.
- We have applied a solution to ensure that link entities can be created in Table View when dragging an entity onto an existing link entity.
- We have applied a solution to ensure that the context menu no longer causes unintended overflow within the container, which previously resulted in an extra scrollbar appearing/extra scrolling needed to access the full context menu.
- We have applied a solution to ensure the tooltip displays the correct entity name when hovering over a resource in the Media tab.
Workflow
We have applied a solution to ensure that timestamps in the Workflow history and process tables now consistently display in UTC time. The "Started at" and "Completed at" column headers also now clearly indicate "(UTC)" to avoid confusion between local and UTC.
Expression Engine
We have applied a solution to ensure that expressions are no longer incorrectly cleared from fields and that evaluated values are computed and persisted accurately.
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.