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 the initial server response time for the Dashboard in the Portal has been optimized, resulting in faster page load performance.
- It has been implemented that the display of filters has been updated to improve user perception and readability. Specifically:
- The bold red styling previously used for filters has been removed to prevent it from being misinterpreted as an error.
-
Matched words in the hierarchical tree view now have updated text styling:
- The highlighted words have been changed to black.
- Highlighting for matched nodes in the tree structure has been refined.
- Partial highlighting is now applied to matched words instead of highlighting the entire text.
- It has been implemented that UI improvements have been made to ensure consistency throughout the interface. Specifically:
- The arrows have been updated as outlined in the deck on slides 12–13, referenced in #106179.
- The tooltip for the work area has been updated to display "Add new work area."
- The messaging for starred entities has been revised to "You don't have any starred entities at the moment."
Expression Engine
- It has been implemented that the expression engine now validates generated CVL keys. Previously, it was possible for an expression to generate an invalid CVL key, which is no longer allowed.
- It has been implemented that the Expression Engine’s FIELDCVLVALUE will no longer fail if the field is null or empty (i.e., no CVL key is set).
- It has been implemented that evaluation error messages have been added to the Expression Engine to provide clearer indications when an expression contains a cyclical dependency.
- It has been implemented that a new function, LSREGEXREPLACE, has been added to the Expression Engine. The function syntax is as follows:
-
LSREGEXREPLACE(originalLocaleString, pattern, replacementText) – This function replaces the text in the supplied locale string based on the specified regex pattern. The replacement will be applied to each language in the original locale string. It is important to note that the replacement text is treated as a regular string.
Example usage:
=LSREGEXREPLACE(FIELDVALUE('MyLocaleString'), ';', '|')
-
Syndicate Plus
- It has been implemented that the default selection for the Inbound Template in the Field Mappings View in Syndicate Plus has been improved, ensuring a more intuitive and efficient user experience.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that, in the REST API, users are no longer able to switch CVL fields from multi-value to single-value if there are existing entities that contain multiple values in that field.
- We have applied a solution to ensure that, in Enrich Export, fields without a fieldset and excluded from the default view no longer appear in the selection of fields in the export modal. Additionally, these fields will not be exported in the generated Excel file.
- We have applied a solution to ensure that the "Not Found" label in Enrich's Multisearch now correctly appears when no values match the search.
- We have applied a solution to ensure that, in the REST API, updating one or more languages of a Specification Field with the LocaleString data type no longer deletes values for languages that are not modified.
- We have applied a solution to ensure that, as a user in the Portal working with Enrich, filtering empty values on a Boolean FieldType now returns the correct results.
- We have applied a solution to ensure that LinkTypes now display correctly in Enrich when adding a new LinkType with the same TargetEntityTypeId as an existing one. Previously, LinkTypes with an index greater than 0 would not appear in the UI if they shared a TargetEntityTypeId with another LinkType.
Expression Engine
- We have applied a solution to ensure that the Expression Engine correctly recognizes all field types using the same CVL expression. Previously, when several field types utilized the same CVL expression, the dependency collection would only recognize one field type as having a CVL value. This issue has now been resolved.
- We have applied a solution to ensure that the Expression Engine now correctly displays the child CVL values that are connected to the parent CVL.
- We have applied a solution to ensure that the Expression Engine's JSONVALUE function works correctly when the supplied JSON Path returns multiple tokens. Previously, a bug prevented the function from handling such scenarios, this has now been resolved.
Syndicate Core
- We have applied a solution to ensure that the Output file for Advanced Excel Format in Syndicate Core now consistently reflects as Filename.xlsx, regardless of the setting in the Extension's 'OutputFormat' field. Previously, the output file was being renamed to Filename.OutputFormat when the setting contained anything other than 'EXCEL' or 'xlsx'.
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.