sections in the article
inriver is moving towards more incremental, smaller releases to accommodate our customers better and faster. 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.
Please see below for the deployed features and improvements:
General
- It has been implemented that the Details View in the Portal now supports persistent scroll behavior after saving an entity. Previously, saving an entity triggered a page reload, resetting the user’s scroll position to the top of the page. This enhancement ensures that after saving, users are returned to their previous scroll position, significantly improving user experience and workflow efficiency. By maintaining the scroll position, this update enhances usability, providing a more seamless and intuitive interaction within the Details View.
- It has been implemented that the Portal now features optimized search performance for multiple entities, significantly reducing execution time. This enhancement addresses prior delays, improving query responsiveness and ensuring faster delivery of search results.
- It has been implemented that the Portal now allows searching for entities missing links to others, using the "Non-existing" operator with field conditions. This feature identifies entities without links to a specified type when defined conditions are unmet, enhancing search precision and usability.
Workflow
- It has been implemented that the assignment ID is now included as a query parameter for the Enrich assignments workflow. To pass the relevant fields set in an assignment within an Enrich workspace configuration, a developer must include the workflowStepGateId when navigating to an assignment.
Inspire
Content Store
Syndicate Plus
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that Portal now correctly handles reading the value of LocaleString in the Details tab. The update ensures that the current and modified values of LocaleString are not equal, improving the user experience. In case of an error, users can now retry saving changes to the LocaleString, enhancing workflow continuity and reducing disruption.
- We have applied a solution to ensure that Supplier Onboarding no longer encounters an error when importing resources due to attempts to fetch old field values from non-existing entities. This fix allows users to import all resources without any errors, ensuring a smoother and more reliable import process.
- We have applied a solution to ensure that in the Query Editor, when CVL keys are digits, selecting a second Child CVL condition now displays the correct values in the dropdown list.
- We have applied a solution to ensure that the DISABLE_CONTENT_SEGMENTATION_FOR_NODES server setting now functions as intended. Previously, when enabled, it incorrectly blocked the linking of entities from segments outside the channel or its nodes, limiting cross-segment relationships. With this fix, the setting now works as expected, allowing entities from any segment to be linked to the channel or its nodes, supporting cross-segment linking. This resolves the issue that previously restricted its utility in scenarios requiring cross-segment entity linking.
- We have applied a solution to ensure that when creating a "spot" or "area" in the Merchandising entity, an error will now appear in the console only if the field type resource map is missing as shown below.
Syndicate Plus
- We have applied a solution to ensure that Syndicate Plus no longer experiences a display bug when no outbound templates exist. This fix improves the user interface by preventing errors or inconsistencies when no templates are available, enhancing overall system stability.
-
Workflow
inriver Implementation Standards
inriver's ambition is to collaborate with our partners in providing our customers with as safe and secure a PIM system as 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
4 comments
Could you give a screen shot of this? I am having problems finding that option
Beth Ryan - thanks for the question! Below I have added a screenshot of how it could look like. Before the "Add condition" box did not appear when selecting "Non Existing" and searching for a link but this has now been implemented and should work as shown is the screen shot.
Helena Gerebro,
Could we get clarity on how the result of "Non-existing" operator with field conditions should be expected?
Hi Steven Christensen, the enhancement to the "non-existing" operator introduces the ability for users to search for parameters to refine the non-existent operator even further.
In the provided screenshot example, the query results would return all items that do not have "Video" as the specific media type linked to them, even if they have other linked resources.
Please let me know if you have any further questions!
Please sign in to leave a comment.