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:
-
A minor release, version 1.17.0, and a maintenance release, version 1.17.1, of the Integration Framework (IIF) have been released. and for detailed information on this please see: Integration framework: Release notes
- It has been implemented that, when utilizing the channel rebuild feature in Plan & Release, a feedback mechanism is now available to verify the completion status of a channel rebuild by making use of the new REST endpoint - /api/v1.0.0/channels/{channelId}/rebuildchannelstate .
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that newly added entities are automatically linked within the channel node content for customers on 3DL.
-
We have applied a solution to ensure that calculated field updates in the Contribute function as intended, introducing key improvements:
- Resolved an issue where updating a single calculated field incorrectly flagged all calculated fields as updated.
- Adjusted the logic so that only the fields that are updated or affected are marked as "Pending" in the Contribute section, ensuring they appear accurately in the Approve list.
- Corrected the display of calculated fields in Contribute to align with the Portal, now properly displaying the concatenation of two fields instead of merely their IDs.
These changes enhance field tracking accuracy and provide a consistent data presentation between the Contribute section and the Portal, offering a clearer and more reliable user experience.
-
We have applied a solution to ensure that the /api/v1.0.0/workareafolder/{workareaFolderId}/entitiylist endpoint now returns results that accurately reflect the specified query conditions. Previously, when using the "channel not equals" filter, the endpoint incorrectly returned results as if "channel equals" had been specified.
With this fix, the returned data now aligns precisely with the saved query conditions, ensuring that results for "channel not equals" filters are displayed as expected. This adjustment corrects the data displayed in customer HTML templates used to monitor entity counts across various work areas, providing reliable and accurate information for "channel not equals" conditions.
- We have applied a solution to ensure that field types retrieved from the cache by Contribute will no longer be modified. Previously, when Contribute fetched field types from the cache and set them to read-only based on Supplier Settings, the ReadOnly attribute in the cache was inadvertently altered. With this fix, the ReadOnly attribute remains unaffected in the cache during retrieval, preserving the original attribute state and preventing unintended updates. This enhancement ensures data consistency and aligns cache behavior with expected read-only configurations in Supplier Settings.
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.