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 a new GUID is generated when an entity is copied. If a field is marked as unique and its default value is set to "GUID," the system will automatically generate a new GUID for that field, ensuring the uniqueness constraint is maintained and allowing the copy operation to proceed without errors.
-
It has been implemented that the REST API now prevents duplicate link types from being processed by the upsert endpoint. This enhancement ensures data integrity and eliminates redundancy during upsert operations.
Expression Engine
- It has been implemented that the Expression Engine now supports these new functions:
-
-
XMLVALUE(xmlDocumentString, xPath) - This function allows users to retrieve values from an XML string using XPath.
Example:
=XMLVALUE(FIELDVALUE("MyXml"), "/breakfast_menu/food[@id='belgian_waffle']/description/en/text()")
-
JSONVALUE(jsonString, jsonPath) - This function enables users to extract values from a JSON string using JSONPath.
Example:
=JSONVALUE(FIELDVALUE("MyJson"), "$.breakfast_menu.food[?(@._id == 'belgian_waffle')].name.en")
-
CVLVALUE(cvlId, cvlKey) - Returns the CVL Value (either string or locale string) of the indicated CVL.
Example: CVLVALUE('Authors', 'astrid_lindgren')
Example: LSCONCATENATE(FIELDVALUE("LocaleStringField"), " - ", CVLVALUE("Color", "red"))
-
FIELDCVLVALUE(fieldTypeId, [entity]) - Returns the CVL Value (either string or locale string) from another Field.
Example: =FIELDCVLVALUE('MyOtherField')
Example: =FIELDCVLVALUE('MyOtherField', FIRSTLINKEDENTITY('MyLinkType'))
-
XMLVALUE(xmlDocumentString, xPath) - This function allows users to retrieve values from an XML string using XPath.
-
Workflow
-
It has been implemented that the Workflow service now includes a new workflow trigger to handle "LinkedEntityUpdate" events. This enhancement enables workflows to respond dynamically to updates in linked entities, providing greater flexibility and automation capabilities.
Brand Store
- It has been implemented that the Brand Store now incorporates product variations into the data available for all download outputs. Additionally, more detailed product information has been made accessible to enhance the experience for Brand Store App users.
- It has been implemented that the Brand Store now includes product variations in the data provided for all download outputs. Furthermore, additional product information has been made available to improve the user experience and accessibility.
-
It has been implemented that the Brand Store now allows users to customize the email subject when sending invitation emails. This enhancement improves user experience by enabling personalized email subjects for each email template, granting users greater flexibility and control.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that users working with HTML Templates in the Control Center will no longer encounter issues when invalid JSON data is present in the Properties field. This fix improves stability and ensures proper handling of JSON data within the Properties field, preventing errors during template processing.
- We have applied a solution to ensure that the Content Store HTML templates now generate previews correctly following the CSP (Content Security Policy) deployment. This fix resolves the issue that caused previews to stop generating, restoring the expected functionality.
Brand Store
- We have applied a solution to ensure that the Brand Store now performs validations on input fields before allowing the cart to be downloaded. This improvement enhances the user experience by preventing errors and ensuring data accuracy.
- We have applied a solution to ensure that the Brand Store no longer includes attributes in a dataset model definition that have not been explicitly selected for use in that dataset. This fix improves data consistency and prevents the inclusion of unnecessary or unintended attributes.
Expression Engine
- We have applied a solution to ensure that the options 'Append,' 'Remove,' and 'Replace' are consistently displayed and accessible in the GUI during the mass update process in the Expression Engine. This fix resolves the previous display issues, ensuring the options appear as expected and function properly.
-
We have applied a solution to ensure that the validation for longer scripts in the Expression Engine is consistent between the UI and CC. This fix resolves the discrepancy where the UI permitted a script to run while the CC did not allow the same script to be saved, ensuring uniform validation across both interfaces.
- We have applied a solution to ensure that it is no longer possible to create an entity when using a fieldSet expression template that returns a non-field set ID in the Expression Engine. This fix prevents invalid entity creation and ensures that only valid field set IDs are processed.
-
We have applied a solution to ensure that mass updating fields with the ExcludeFromDefaultView property set now functions correctly in the Expression Engine. This fix resolves the issue, allowing the mass update process to work as expected for fields with this setting.
Workflow
- We have applied a solution to ensure that queries included in assignments within the Workflow service can now be deleted as expected. This fix addresses any restrictions or errors previously encountered, allowing for more efficient management of queries.
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.