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 releases and identify and mitigate any erroneous behaviour 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 we now support multi-file uploads with real-time progress and status feedback, streamlining asset ingestion and improving upload visibility.
- It has been implemented so that all changes performed by administrators within Control Center – Model are logged with full traceability, including the affected changes and the responsible user, making all modifications visible in the Control Center logs.
- It has been implemented that workflow list actions are now consolidated into a single action area per row. Each workflow row displays a primary action button with an overflow menu for additional options, providing a more consistent and streamlined interaction pattern.
- It has been implemented that the table panels in the Workflow In Progress and History views are now resizable. A visible drag handle between the main content area and the lower table allows users to adjust the layout vertically based on their preference, making it easier to focus on either the upper content or the table data.
- It has been implemented that the Channel service handles high-volume link update and delete operations more efficiently under concurrent load, reducing processing delays that could occur when large numbers of channel structure updates are processed simultaneously. Please note! This improvement is most impactful in environments with a high volume of concurrent link operations.
- It has been implemented that the resize handle in the Enrich view now has an increased hit area and improved visual feedback, making it easier to detect and interact with.
- It has been implemented that the REST API query endpoint (POST /api/v1.0.0/query) now accepts an optional objects field in the request body. When "objects": "count" is specified, the response returns only the total count of matching entities, omitting the full list of entity IDs. This results in a significantly smaller and faster response for callers who only need the count.
Existing query requests that do not include the objects field are fully unaffected and continue to return both the count and the full list of entity IDs, as before.
Please note! If an unrecognised value is provided for theobjectsfield, the API returns a 400 Bad Request response with a descriptive error message listing the supported values.
Print & Publish (Print 2.0)
- Product rebranding to "Print & Publish" — The login page, header, and navigation menu now reflect the updated product name. The "Automation" section has been renamed to "Self-service publishing", and the InDesign EasyCatalog Enterprise adapter is now labelled "inriver Print & Publish".
- It has been implemented that Print generation for large documents (2000+ main entities) is now significantly faster. The system now generates output per main entity, allowing incremental regeneration of only entities that changed, without compromising overall system stability.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that search operations within work Areas perform more efficiently and reliably, introducing a loading spinner to provide clear user feedback during search execution.
- We have applied a solution to ensure that Fieldset and Segment Automation can be configured successfully within Workflow Entity Automation steps without UI errors when selecting Static Values.
- We have applied a solution to ensure that the assignments panel no longer displays assignments with zero entities. Previously, assignments without associated entities could appear incorrectly on the panel. Now, only assignments containing at least one entity are shown.
- We have applied a solution to ensure that the Save button remains disabled until actual changes or updates are made to entity details.
- We have applied a solution to ensure that concurrent API requests no longer result in duplicate link creation.
- We have applied a solution to ensure that users can remove a previously set Link Entity Type from a link type directly in Control Center. It is now possible to clear the Link Entity Type by selecting the blank option from the dropdown and saving the changes.
- We have applied a solution to ensure that the Query Editor correctly scopes DateTime field interactions to individual query rows, preventing the calendar pop-up from failing to open and values from leaking between rows when editing saved queries with multiple conditions.
- We have applied a solution to ensure that importing a model in Control Center no longer fails with a database foreign key constraint error on the LanguageRoleLanguage table.
- We have applied a solution to ensure that languages can be deleted successfully in Control Center > Model without encountering an unexpected error.
- We have applied a solution to ensure that the REST API now correctly rejects writes to formatted (read-only) specification fields. Previously, calling PUT /api/v1.0.0/entities/{entityId}/specificationvalues on a field with a Format template would silently persist the value to the wrong database table, causing data corruption and HTTP 500 errors on subsequent GET requests. The endpoint now returns a clear error message when a formatted field is targeted, preventing unintended data modifications.
We have applied a solution to ensure that Specification Categories in Enrich are consistently visible in the new UI, regardless of their collapsed state configuration in the legacy UI.
Print & Publish (Print 2.0)
- We have applied a solution that fixed an issue where CVL keys were rendered instead of their translated values in InDesign templates. Special characters (e.g. the diameter symbol) are also now displayed correctly.
- We have applied a solution that fixed cases where a failed print could incorrectly display a "ready" status instead of being marked as failed.
- We have applied a solution for prints without a source configured to now gracefully be skipped during the reset process instead of causing an error.
- We have applied a solution for an issue where the latest Print & Publish extensions (1.0.36) failed to load in Control Center.
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.