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.
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 a user's selected view now persists after refreshing the page. This enhancement ensures that the preferred view remains intact, eliminating the need to reselect it upon each refresh.
-
It has been implemented that Enrich now displays the number of linked entities for a link type across multiple views:
- On the "Includes" tab in the default card view
- On the "Included in" tab in both the default and sorted card views
This enhancement provides users with greater visibility into the number of linked entities for each link type, improving data accessibility and enabling more informed decision-making.
Expression Engine
-
It has been implemented that the Expression Engine now includes a new function:
LSEXTRACT(localeString, langCode) — This function retrieves a string for a specific language from an arbitrary locale string.
Example: =LSEXTRACT(FIELDCVLVALUE('MyLocaleStringCvl'), 'sv-SE')
This enhancement allows users to efficiently extract language-specific values from locale strings, supporting more dynamic and localized data processing within the Expression Engine.
Inspire
- It has been implemented that Inspire now streamlines the content review experience by enabling content managers to validate, enhance, and approve generated text directly within the modal. This reduces the need for context switching, offering improved usability and seamless workflow integration. As a result, the content validation process in inriver Enrich is faster, more efficient, and user-friendly.
- It has been implemented that Inspire has enhanced the Details tab by leveraging portal entity data, significantly improving performance by reducing the need to retrieve entity data via the REST API.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that the Values step for Locale Strings in Mass Update now loads correctly and responds to user actions. This fix restores full functionality, allowing users to update Locale String values without issues.
- We have applied a solution to ensure that extensions deployed in the Control Center now generate correct Complex Query results. This fix resolves the issue with inaccurate query outputs, ensuring reliable and consistent data retrieval.
- We have applied a solution to ensure that Plan & Release now supports adding Links with LinkEntities.
- We have applied a solution to ensure that Plan & Release correctly prevents the duplicate creation of Links with LinkEntities.
- We have applied a solution to ensure that Plan & Release properly displays related entities with LinkEntities, ensuring they no longer duplicate when the same entity is linked under multiple LinkEntities.
- We have applied a solution to ensure that Plan & Release includes droppable zones to link entities under already created LinkEntities, aligning with Portal functionality.
- We have applied a solution to ensure that Plan & Release accurately removes individual entities under a LinkEntity without affecting the entire row of entities.
- We have applied a solution to ensure that, after a static CVL is converted into a custom CVL, only the CVL values from the custom CVL extension are returned in REST API and remoting API requests.
- We have applied a solution to ensure that in Plan & Release, entities with LinkTypes will no longer duplicate in the sortable card view. This fix eliminates redundancy and ensures a more accurate and streamlined display of linked entities.
- We have applied a solution to ensure that in Enrich > Details, field set modifications are restricted for locked entities, preventing users from changing and saving field sets when an entity is locked. Previously, users were able to modify and save field sets for locked entities, which resulted in unintended changes and potential data inconsistencies. This fix ensures that locked entities remain protected from unauthorized updates.
- We have applied a solution to ensure that in Content Segmentation - Excel Import, users with non-administrator roles and non-default segments assigned can now successfully create entities via Excel import. Previously, users in these roles were unable to create entities, which resulted in import failures. This fix ensures that users can now perform the import operation regardless of their role or assigned segment.
- We have applied a solution to ensure that Enrich Specifications Tab now maintains consistent Parent/Child CVL behavior by dynamically filtering Child CVL values based on the selected Parent CVL. Previously, the Specifications tab displayed all Child CVL values regardless of the selected Parent CVL, causing inconsistencies with other areas in PIM and increasing the risk of incorrect data selection. This update ensures a more accurate and streamlined user experience.
Expression Engine
-
We have applied a solution to ensure that the ISERROR function in the Expression Engine behaves as expected, facilitating accurate error checking. This update allows scenarios like the following to work correctly:
=IF(ISERROR(FIELDVALUE('SomeField', FIRSTLINKEDENTITY('MyLinkType'))), 'error', 'success')
- We have applied a solution to ensure that the Expression Engine correctly calculates custom rules when updated via expressions. This fix aligns expression-based updates with manual behavior, allowing users to reliably update child entities and unblock publishing workflows.
Workflow
We have applied a solution to ensure that in Enrich Work Areas, filtering by workflow queries now works correctly after performing drag-and-drop actions. This fix ensures that the results are updated and accurately reflect the latest changes.
Brand Store
- We have applied a solution to ensure that Brand Store has corrected the date formatting for PDF downloads to ensure data integrity. This update addresses inconsistencies in the previous format, ensuring all downloaded reports reflect accurate and standardized date information.
- We have applied a solution to ensure that Brand Store has corrected the issue with displaying field names according to the default language. This ensures that the proper field names are accurately shown in the Manage Export Fields section, aligning with the selected default language settings.
Inspire
- We have applied a solution to ensure that the missing tokenRemaining return value in inspireField is now correctly handled. This fix resolves the issue where the remaining token count was displaying as "Infinity" when generating content, ensuring accurate token count display during content generation.
- We have applied a solution to ensure that the error on the Details tab in Inspire, caused by missing Fieldset data during entity transformation, is resolved. The fix introduces a check to set the Fieldset to null if unavailable, preventing the error.
- We have applied a solution to ensure that Inspire no longer displays negative or "Infinity" token values in the low token warning message. The token count now accurately reflects the remaining balance.
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
0 comments
Please sign in to leave a comment.