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 behaviour 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 so that when the server setting DISABLE_CONTENT_SEGMENTATION_FOR_NODES is set to true, saving a link rule in Portal will establish associations between the node and entities from other segments. This behaviour is consistent with the processing logic executed by the UpdateLinkRuleDefinitionsJob.
Expression Engine
-
It has been implemented so that the Expression Engine now includes the CHAR(characterCode) function, which returns the Unicode character corresponding to the specified value. This enables scenarios such as inserting line breaks within locale strings by using CHAR(10) or CHAR(13).
Syntax:
CHAR(characterCode)Example:
=LSGENERATE(CONCATENATE("Some text", CHAR(13), "Some text on a new line"))
Inspire
It has been implemented so that Inspire now notifies users when an AI-translated value is unchanged, addressing cases where identical translations previously kept the Save button disabled and were excluded from field history.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the Media Tab now correctly displays resources even when the number of linked entities exceeds 5,000.
- We have applied a solution to ensure that CVL fields with large locale string lists now update correctly when switching Data or Model Language settings, resolving an issue where non-language-aware CVL Value ETags previously caused cached values from the prior locale to persist instead of retrieving the correct localised data.
- We have applied a solution to ensure that validation reports can now be successfully downloaded from the Portal and that the LRJ Excel import no longer triggers validation errors related to invalid DateTime column values.
- We have applied a solution to ensure that the Select All option is hidden when the work area is split, preventing unintended selection behaviour in the split view.
- We have applied a solution to ensure that when restoring a field revision for a child CVL in table view, the system validates that all restored values are allowed by the currently selected parent CVL value(s). If any restored values are invalid under the current parent selection, the restore is blocked, and an error message lists the invalid values.
- We have applied a solution to ensure that the Content Store correctly displays the migration warning, adjusting the styles to prevent the warning from appearing on the initial load and improving the overall user experience.
Expression Engine
- We have applied a solution to ensure that expression dependencies are correctly recorded in the Expression Engine when FIELDVALUE() is used to retrieve the value of a linked entity field, even if that field is empty.
- We have applied a solution to ensure that expression engines set on CVL fields are properly updated when the related entity transitions from a null value to a populated value.
- We have applied a solution to ensure that expressions on parent entities are updated immediately based on values from their associated Item(s), without requiring any additional updates to the parent entity.
- We have applied a solution to ensure that the =SEGMENTID(FIRSTLINKEDENTITY('')) expression now returns the correct Segment ID. The issue causing the expression to always return 0 has been resolved, and it now evaluates linked entities as intended.
Brand Store v2
We have applied a solution to ensure that the Related Products table no longer displays a LocaleString when no language value exists, and now correctly renders the field as empty in such cases.
We have applied a solution to ensure that users now receive the correct default language, with the system properly selecting it based on the store’s configured languages.
Syndicate Core
- We have applied a solution to ensure that the "Image" and "Images" JSON objects in Syndicate are correctly rendered in the Excel output, resolving the previous formatting issues.
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.