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.
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 tabindex HTML attribute is now applied to the menu navigation, allowing menu items to be properly highlighted when navigating using the Tab key. This enhancement improves accessibility and ensures a better user experience.
- It has been implemented that the "Assignments" button on the Dashboard has been updated to improve clarity and user experience. The button has been renamed to "View Assignments", its styling has been updated to a rounded black button, and hover animations have been added for enhanced interactivity.
Expression Engine
- It has been implemented that the performance of entity creation involving hundreds of expressions has been significantly improved.
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that when a user in the Portal utilizes Enrich to copy an entity, a new GUID is generated for fields with FieldType tagged as unique and a GUID default value.
- We have applied a solution to ensure the Query Editor displays the correct query in split view, corresponding to the selected workspace area.
- We have applied a solution to ensure that Mass Update report logs provide clearer and more accurate status descriptions. The term "Updated" has been replaced with "Processed" to indicate that entities have undergone the mass update process, regardless of whether any values were changed. Additionally, "Not updated" has been changed to "Failed" to explicitly indicate that these entities encountered an issue during the update process.
- We have applied a solution to ensure that restricted fields remain hidden from users with restricted roles during mass update operations. Role-based visibility rules have been introduced:
- If a user has multiple roles and segments, with at least one unrestricted and one restricted, the field is displayed with a warning.
- If a user has a single role and all segments are restricted, the field remains hidden.
- If a user has a single role and all segments are unrestricted, the field is shown without a warning.
Expression Engine
- We have applied a solution to ensure that stale error messages are no longer shown for expressions after they are re-evaluated.
- We have applied a solution to ensure that expressions are correctly copied when duplicating an entity.
Brand Store
- We have applied a solution to ensure that field names are correctly translated and displayed in exported files, aligning with the default language.
Syndicate Core
- We have applied a solution to ensure that Excel files downloaded from syndication correctly handle work areas or mappings containing a "." in their names.
inriver Integration Framework
- We have applied a solution to ensure that logically deleted entities are properly excluded, preventing potential "The given key was not present in the dictionary" exceptions when invoking the GetDeltaCategoriesPaged and GetAllCatalogStructuresPaged methods. This fix addresses the issue by refining entity filtering logic, ensuring data integrity and stability in the retrieval process.
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.