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 behavior 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 that, in the Portal Dashboard, a placeholder text containing a brief instruction on how to enable the widgets will now be displayed when all widgets are disabled. This enhancement improves user guidance by providing clear direction in the absence of active widgets.
- It has been implemented that the REST API now allows read-only access to LinkRules via GET endpoints without requiring the ManageLinkRule permission. This enables users to retrieve LinkRule data for validation and templating purposes, while still restricting create, update, and delete operations.
Table View
- It has been implemented that, in the table view, additional field descriptions are now displayed as info icons within the respective grid columns. In this initial version, the info icons will appear only when at least one of the additional field descriptions is enabled. Supported descriptions include:
Field Description
Mandatory
Read Only
Multivalue
Unique
Exclude from Default View
Field History
Expression Engine
Inspire
The Field Description is localized, with language selection prioritized in the following order: the user's current model language, default English, or the first available value. - It has been implemented that, in the table view, the selected columns are now retained when a user performs a quick search and receives results. This ensures a consistent user experience by preserving column configurations during search interactions.
Workflow
- It has been implemented that, in the workflow, rich text versions of workflow instructions are now displayed within an accordion component. The Workflow Maker application supports storing instructions in rich text format, including elements such as bullet points, bold, and italic styling, enhancing clarity and readability for end users.
-
It has been implemented that, in the workflow module, support for the Enhanced Workspace type has been introduced. Once a workflow workspace is defined in Enrich, it becomes selectable within the workflow assignment configuration, enabling tighter alignment between workflow steps and workspace views.
Additionally, a "Refresh" button has been added to the workflow query list. This allows users to retrieve newly created workflow queries in real-time without leaving the workflow configurator, thereby improving usability and reducing context switching during workflow setup.
NB! The Enhanced Workspace option is available only to users with the ManageWorkflows permission and in environments where the EnhancedWorkspace feature flag is enabled.
Inspire
- It has been implemented that, in Inspire, the media rendering logic within the Details tab has been enhanced to improve image loading performance.
- It has been implemented that, in Inspire, unexpected error messages have been enhanced to provide clearer and more user-friendly explanations of failure reasons.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that, in the Portal, when editing an Entity in Enrich > Details Tab, users are prevented from saving if no changes have been made and the Enter key is pressed while focused on a text field.
- We have applied a solution to ensure that the Excel import process no longer becomes unresponsive due to issues caused by certain regular expressions.
- We have applied a solution to ensure that, in the REST API, a timeout is implemented for regex matching during the addition and updating of entity fields.
- We have applied a solution to ensure that, when creating a new language via the REST API, the API response accurately reflects the successful addition of the language, providing correct and reliable feedback to the client.
- We have applied a solution to ensure that the /api/v1.0.0/channels/content/{path} REST API endpoint correctly respects the Accept-Language header. When a valid localized value for DisplayName exists in the requested language (e.g., "bg" for Bulgarian), it will now be returned accordingly.
- We have applied a solution to ensure that the list of EntityIds under a static Workarea is not cleared when a validation failure occurs during processing. This preserves the atomicity and integrity of the Workarea’s data, preventing unintended data loss.
- We have applied a solution to ensure that regular expression validation is consistently enforced across all Add and Update Entity methods in the Remoting API. This resolves an issue where certain entity fields were not properly validated against their defined regular expressions, preventing potential data inconsistencies.
Table View
- We have applied a solution to ensure that, in the table view, all language variants of a locale string are displayed when 'Select All' is used in the columns tool panel. Additionally, all columns related to a single locale string are now counted as one toward the maximum column limit, allowing for a more accurate and user-friendly column selection experience.
- We have applied a solution to ensure that, in the Table View under the Includes tab, when an entity with no media is dragged and dropped, a default thumbnail image is displayed. This ensures consistent visual feedback and prevents missing thumbnails for entities without media.
- We have applied a solution to ensure that, in the Table View, the updated main picture is correctly displayed after it is changed. Additionally, the fallback icon is now consistently shown across both the Media and Entity columns, providing a uniform visual experience when no image is available.
Workflow
- We have applied a solution to ensure that, in the workflow module, the Modified Date is now correctly updated when changes are made to workflow rules or steps. This ensures accurate tracking of workflow modifications for auditing and version control purposes.
- We have applied a solution to ensure that, in the workflow module, only active workflows are displayed in the workflow assignment selection. This enhancement improves usability by preventing the selection of inactive or deprecated workflows.
- We have applied a solution to ensure that workflow query Workareas can now be dragged and dropped from sub-folders (child) to the tree (parent), aligning the behavior with that of standard Workarea Folders and Workarea Queries. This fix improves consistency and usability in managing workflow configurations.
Inspire
- We have applied a solution to ensure that, in Inspire, the simultaneous generation of parent and child CVLs in the Details tab functions correctly. This fix resolves the issue where the parent CVL value previously had to be generated and saved before the child CVL value could be generated, enabling concurrent processing of related CVLs.
- We have applied a solution to ensure that Inspire fields are now correctly displayed in edit mode within the table view. This fix improves visibility and accessibility of Inspire-specific data during editing operations.
Expression Engine
- We have applied a solution to ensure that the Expression Engine no longer causes the REST API /fetchdata endpoint to fail with a 500 error when a faulty function is applied. This fix enhances the robustness of the endpoint by handling expression-related errors more gracefully.
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
2 comments
Hi Peter,
Please reach out to inriver Support to have the EnhancedWorkspace feature activated for the environments where you need it. At this time, it cannot be activated manually. The feature will be generally available across all environments shortly, but until then, Support can assist you with the activation.
Best regards,
Viktor
Hi, can you please give more info on how to enable the EnhancedWorkspace feature flag? I created a server setting with this name and set the value to true but I still don't get the option to save the workspace as a "Workflow workspace". I also have the permission ManageWorkflows.
Please sign in to leave a comment.