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 the REST API now includes a new endpoint to retrieve the current channel queue depth, returning the item count only. This enhancement provides a straightforward mechanism to determine how many items are presently in the channel queue, addressing the previous lack of a simple and efficient method to obtain this information.
Visual Workflow Builder
It has been implemented so that the Visual Workflow Builder includes a new server-level configuration for defining the minimum cooldown period applied when sending workflow assignment notification emails. This setting, WORKFLOW_ASSIGNMENT_NOTIFICATION_COOLDOWN_IN_MINUTES, accepts any numeric value between 5 and 10,080 minutes, allowing administrators to control notification frequency and prevent excessive email delivery.
It has been implemented so that, within the Visual Workflow Builder, workflow assignment notification emails are sent only when there are actual assignment updates. This ensures that notifications are triggered exclusively by meaningful changes, reducing unnecessary email traffic and improving the relevance of assignment communications.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that, when using a Media Object with the /api/v1.0.1/entities:fetchdata REST API endpoint, all linked resources are now returned as expected. This fix resolves an issue where associated resources were not fully included in the response.
We have applied a solution to ensure that, during Excel Import, updating a Parent CVL value automatically removes any invalid Child CVL values that are not associated with the newly selected parent value. This fix enforces proper parent–child CVL relationships and maintains data integrity during the import process.
We have applied a solution to ensure that the REST API endpoints, entities:fetchdata and linksandfield,s no longer return a 500 Internal Server Error when linked entities have no field data. This fix addresses an issue where missing saved field values caused an exception, and the endpoints now handle such cases gracefully to consistently return a valid response.
We have applied a solution to ensure that the REST API endpoint PUT /api/v1.0.0/entities/{entityId}/specificationvalues and /api/v1.0.0/entities/{entityId}/specification now returns a correct and consistent response even in scenarios where a link between the entity and specification exists, but the SpecificationEntityMapping table fails to contain a value for the connection. This fix prevents errors and ensures reliable handling of edge cases in specification value updates.
We have applied a solution to ensure that, in the Portal Entity Overview page, the Workflow Assignment Instruction(s) list now expands and minimizes as expected. This fix resolves an issue where the list did not respond correctly to user interaction, restoring proper usability and behavior.
Brand Store v2
We have applied a solution to ensure that filtering behaves correctly when multiple filters are applied simultaneously. This fix resolves an issue where certain filters were unintentionally ignored, allowing users to reliably and accurately refine results using combined filter criteria.
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.