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.
Please see below for the deployed features and improvements:
- It has been implemented that in Enrich, users now can utilize the "Not Contains" operator within the Query Editor for both String and LocaleString data types. This enhancement allows for more precise data filtering.
- It has been implemented that a cancel button has been added to all warning messages that involve user decisions within the Brand Store section, including alert modals. This enhancement allows users to easily cancel an action or dismiss a warning, providing greater control and improving the overall usability of the interface.
-
It has been implemented in the Brand Store section, a notification toast will now appear when a brand store is deleted, providing immediate feedback to the user. Additionally, a spinner will be displayed during the deletion process to indicate the action is in progress. These enhancements aim to improve user experience by clearly communicating the status of the deletion operation and ensuring that users are informed throughout the process.
Please see below for the deployed bug fixes:
- We have applied a solution to ensure that the zoom responsiveness in the Brand Store section functions correctly. This resolution addresses the issue where zooming in to 100% or more caused the brand store layout to break. With this update, the layout now remains intact and visually consistent at all zoom levels, thereby enhancing user experience and usability across different display settings.
-
We have applied a solution to ensure that fields in the Brand Store display appropriate fallback values when a language translation is unavailable, addressing previous issues where some fields showed "object.object...". The resolution is as follows:
-
Grouping Dropdown: When no translation exists, the fieldtypeid will now display, providing clarity.
-
Field Labels: The fieldtypeid will be displayed when no translation is available, ensuring consistent identification.
-
Variation Table:
- When a language is selected but the value is empty, a "-" will be displayed, maintaining the existing behavior.
- When no translation is present for the selected language, the label "Missing Translation" will be shown, indicating that the translation is unavailable for the chosen language.
These improvements enhance readability and user experience by providing clear, consistent labeling across untranslated fields.
- We have applied a solution to ensure that when a PDF template is deleted from the Brand Store, it is also removed from all associated Brand Stores utilizing that template.
- We have applied a solution to ensure that .tiff files in the Brand Store are handled effectively, given that browsers do not support previewing this file format. Specifically, the system now displays a file type icon instead of a preview for .tiff files within entities, providing a consistent user interface. Additionally, the preview button for .tiff files has been replaced with a download button, allowing users to access the file directly.
- We have applied a solution to ensure that the "No Available Products" message is no longer displayed momentarily when a user opens a brand store to which they have access.
- We have applied a solution to ensure that NULL CVL String values from the Control Center are displayed with the bracketed CVL Key in the Portal, rather than appearing blank. This fix aligns the display of NULL values with that of CVL LocaleStrings, improving clarity and consistency for users.
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.