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 Control Center users can now set the number of visible list entries beyond the previous limit of 20. New options include a page size of 50 and an 'all' option for viewing entire lists simultaneously.
- It has been implemented that the performance of fetching completeness definitions has been significantly improved. This enhancement optimizes the retrieval process, reducing latency and ensuring faster access to completeness definitions.
- It has been implemented that the filtering behavior for Parent-Child CVLs in the Link Rule Editor within the Enrich and Plan & Release modules has been enhanced. This improvement ensures proper association and usability, eliminating confusion and inefficiencies. Users can work seamlessly with large CVLs, maintaining precise configurations when managing link rules.
-
It has been implemented that a search field has been introduced within the CVL selection dropdown in the Link Rule Editor of the Plan & Release and Enrich modules. This enhancement enables users to quickly locate specific values within large CVLs, addressing previous challenges that made finding values difficult and hindered the effective creation or updating of link rules. This improvement significantly enhances the user experience and streamlines workflows for managing complex link rules.
Expression Engine
- It has been implemented that the Expression Engine now supports these new functions:
-
SEGMENTID([entityId]) - Returns the segment ID. Entity can be supplied to get the value from another Entity.
Example: =SEGMENTID()
Example: =SEGMENTID(FIRSTLINKEDENTITY('MyLinkType')
-
FIELDSETID([entity]) - Added overload to FIELDSETID to be able to check other entities fieldset id
Example: =FIELDSETID(FIRSTLINKEDENTITY('MyLinkType')
-
GUID() - Generates a new GUID
Example: =GUID()
-
SWITCH(valueToSwitch, valueToMatch, returnOnMatch, [valueToMatch1, returnOnMatch1, …], defaultValue) - A switch statement is a way to check one value vs many values, returning a specified value on the first found match or if no match was found returns a default value
Example: =SWITCH(FIELDVALUE('MyType'), ‘typeA’, ‘some text’, ‘typeB’, ‘some other text’, ‘No matching type found!’)
-
SEGMENTID([entityId]) - Returns the segment ID. Entity can be supplied to get the value from another Entity.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that HTML templates created or updated via the REST API in Control Center > HTML Template Management now render correctly in the Portal without manual intervention. This fix ensures seamless rendering of HTML templates, improving user experience and efficiency.
- We have applied a solution to ensure that the entity remains active and draggable when opened in a new tab in Enrich.
-
We have applied a solution to ensure that when a Server Extension cancels the linking of two entity types involving a LinkEntity, neither the Link nor the LinkEntity is created, as expected.
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.