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 that the Field Set and Segment fields have been repositioned alongside Completeness, allowing the Display Name and Description fields to utilize the full available width in Compact mode.
- It has been implemented that the Index column is now displayed in the Plan & Release table overview, improving visibility of item ordering directly within the table view.
Inspire
- It has been implemented to surface Inspire-related errors and warnings in the PIM Control Center logs table. Errors from supported Inspire endpoints (generate, translate, and configuration CRUD operations) are logged and made available in Control Center.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that parent-child CVL mappings resolve correctly when multiple fields share the same CVL, preventing incorrect or missing values in Table View.
- We have applied a solution to ensure that searches containing double quotes (") are processed correctly in Query Editor, preventing valid queries from incorrectly returning no results.
- We have applied a solution to ensure that when a multi-language (LocaleString) field is updated through Excel import, server extensions now receive the complete set of language values for that field – including the languages that were not part of the Excel file – instead of only the languages present in the import. This matches the behaviour already seen when updating a field through the portal, so server extensions that validate language values (for example, checking that certain languages are not empty) now behave consistently regardless of whether the update is made via the portal or via Excel import. Only the languages actually provided in the Excel file are saved; the remaining languages keep their existing values.
- We have applied a solution to ensure that creating an entity no longer returns an error when its entity type has a completeness action configured to create a task on entity creation. The entity and its task are now created successfully.
- We have applied a solution to ensure that the Workflow entity condition using "Fieldset" with "Contains Any" correctly routes entities to the matching output path. Previously, entities always went to the Default output regardless of the fieldset condition.
- We have applied a solution to ensure that the glossary CSV file imports automatically handle common formatting differences caused by Excel and regional settings. Users no longer need to manually edit files before importing - the system now detects the correct delimiter and encoding automatically, and displays informational messages when adjustments are applied.
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.