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, as a customer admin user working with the Excel export shared settings, you can now edit and delete the settings, provided that you have the "ManageSharedExportSettings" permission. This ensures that only a limited number of users with the appropriate permission can make changes to shared export settings.
For shared export settings, the following actions now require the "ManageSharedExportSettings" permission:
-
- Edit the name of the export setting
- Edit the settings parameters for the export setting
- Delete a shared export setting
For personal export settings, users will still retain full control to perform these actions without needing the new permission.
- It has been implemented that, as a customer admin saving the configuration settings for an Excel export, you can now save the settings as shared. This allows other users to perform exports based on the same shared settings, ensuring consistency and ease of use across the team.
- It has been implemented that logging has been added to provide metrics on the number of entities returned from query searches. Additionally, logging has been implemented for every search type, with logs accessible in the CC. This enhancement enables better tracking and analysis of search performance and results.
- It has been implemented that, as a content editor exporting entities to Excel, you can now select from a list of either shared or personal export settings. This functionality allows you to reuse previously saved settings, whether they were created by you or a colleague, ensuring greater flexibility and efficiency in the export process.
Brand Store
Expression Engine
Please see below for the deployed bug fixes:
General
- We have applied a solution to ensure that when a customer updates a field via Excel import, the new value is correctly displayed in the portal. Previously, the updated value was not showing, even though it was reflected in the field revision history.
- We have applied a solution to ensure that the CVL Key and Value columns in the export file are displayed adjacent to each other, as expected. Previously, the values were displaced, causing a misalignment between the keys and their corresponding values.
- We have applied a solution to ensure that, as a user in the Portal working with the query editor, the contains operator applied to a locale string field now returns accurate results.
- We have applied a solution to ensure that searches for specific numeric values (e.g., "1", "2", "7", "8", "3", "9") in the Work Area now return accurate results. Special characters are no longer rendered as HTML ASCII codes and apostrophe mismatches (curly vs. straight) no longer impact search accuracy.
- We have applied a solution to ensure that the placeholder image no longer persists on the media tab after unlinking all resources using the "Remove All Relations" feature. Previously, after using this feature during load tests or cleanup, a placeholder image continued to display even when no resources were linked, requiring manual intervention to resolve.
- We have applied a solution to ensure that all fields are displayed during mass updates, with a warning issued if a field has a restriction set up. Users are now prevented from selecting fields with restriction rules applied during a mass update, ensuring compliance with the established restrictions and improving the user experience.
-
We have applied a solution to ensure that empty fields in the query search in Enrich are correctly found after editing. Previously, fields that were left empty during an edit were not returned in search results.
Brand Store
- We have applied a solution to ensure that the Brand Store clears previous preview values before loading the updated design template. This adjustment aims to improve the accuracy and consistency of the design preview display.
- We have applied a solution to ensure that the Brand Store provides an enhanced user experience by updating the modal image display to support both TIFF, PDF, and PSD file types. This improvement allows users to seamlessly upload and view these file formats within the platform.
- We have applied a solution to ensure that the Brand Store now includes the missing Chinese language options, providing full support for the previously unavailable Chinese language variants.
- We have applied a solution to ensure that the Brand Store maintains data integrity by creating a new dataset when restoring a Brand Store.
- We have applied a solution to ensure that the Brand Store provides a more reliable and user-friendly experience by updating the display text when deleting an HTML template. Additionally, a confirmation dialog has been implemented to prompt users when deleting a Brand Store, preventing accidental deletions and ensuring actions are confirmed before proceeding.
- We have applied a solution to ensure that the Brand Store operates seamlessly by implementing a check for a single language selection as soon as the page is loaded when the PDF is selected.
Expression Engine
- We have applied a solution to ensure that the template expression for creating a new entity is now correctly populated in the dialog within the Expression Engine. Previously, the template expression was not being displayed, which impacted the user experience.
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.