Sections in the article
Inriver is moving toward smaller, more incremental releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver can improve release quality and transparency and identify and mitigate erroneous behavior 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 to ensure more reliable information, allowing users to clearly see when a job has been completed or has failed.
- It has been implemented that the workflow list now shows a queue-status indicator in the header, displaying the number of entities waiting to enter workflow processing and the number waiting for AI Agent processing. The counts refresh automatically while you are on the page, and a tooltip shows the current processing state and when the information was last updated. When there is nothing queued, a neutral "No items waiting" state is shown. The AI Agent count is only shown when both Inspire and Workflow Agents are enabled.
- It has been implemented that quick search suggestions are generated more efficiently, improving response times and overall search performance.
Expression Engine
-
It has been implemented that expressions can establish dependencies on CVLs, enabling them to reactively re-evaluate when CVL values are added, updated, or removed. Currently, dependencies are established only for expressions that directly reference a CVL using the CVL VALUE or FIELDCVLVALUE function. Re-evaluation runs as a background job and is visible in the portal to the user who modified the CVL.
Important: Dependencies are established only when an expression is evaluated. Consequently, existing expressions do not have these dependencies established automatically and must be re-evaluated once to activate reactive behavior. This can be achieved, for example, by running an ApplyExpression job.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that special characters such as accents and symbols (é, à, ™, °) are preserved when a glossary is downloaded as a CSV file and uploaded again. Downloaded CSV files now also open with the correct characters in Excel.
- We have applied a solution to ensure that a language no longer permitted by a user's Language Role is removed from the Data Language and Model Language selection lists independently, so a language that is still allowed for one of those fields no longer incorrectly stays selectable for the other.
We have applied a solution to ensure that mapping combinations, syndication consistency, and API requirements and mappings for exports work correctly in Combine & Syndicate.
- We have applied a solution to ensure that multi-value CVL fields can be updated via the REST API and RemoteManager when the field already contains a value that was deactivated after it was selected. Previously, this failed with a "CVL key that is deactivated" error; you no longer need to remove the deactivated value first. Adding a new deactivated value is still not permitted, matching the Portal.
- We applied a fix to ensure the REST API documentation (Swagger) for the endpoint POST /api/v1.0.0/entities:mapuniquevalues correctly shows that a returned entity id can be null when a unique value has no matching entity. Previously, the documentation described the returned values as non-nullable integers, which did not match the actual response. The response of the endpoint itself has not changed.
Please note! API clients that are generated from the Swagger document may now treat the returned values of this endpoint as nullable integers.
Expression Engine
- We have implemented a solution to ensure completeness expressions re-evaluate when values in linked entities change.
Print & Publish
- We have applied a solution to ensure that documents generated with a Template pagination configuration show their page previews in the same order as the source data, and that all previews are available. Previews now start appearing while the document is still being generated, instead of only after the whole job has finished. Output files whose names contain special characters (such as a backslash) are now handled correctly and included in the generated output.
- We have applied a solution to ensure that the Self-Service Publishing interface clearly indicates whether generated documents are based on the latest version of the print XML, making it easier to identify documents that require regeneration.
- We have applied a solution to ensure that the dashboard label "Prints in progress" is renamed to "Prints to be reloaded" to more accurately reflect the status of print operations requiring reloading and avoid confusion with background processes currently in execution.
- We have applied a solution to ensure that changes to the Print Configuration of a Priority Print automatically trigger print regeneration as expected.
Syndicate
- We have applied a solution to ensure that Combine & Syndicate correctly applies mapping function combinations, resolves inconsistencies with standalone syndications, and supports exports with API requirements and mappings.
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.