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.
Please see below for the deployed features and improvements:
General
- It has been implemented that Control Center admin users can now upload customer logos during the preparation phase for a new customer. This feature allows the uploaded logo to be displayed on the environment selection page within the Control Center, ensuring it is visually represented on the customer card for a professional and customized user experience.
- It has been implemented that a new feature enables the export of CVL Keys along with their corresponding values in a dropdown format as "CVLKEY | CVLVALUE". This enhancement also introduces support for importing Excel files in the same format. The feature is restricted to the "CVL Key" CVL setting and does not support multi-value CVLs. This functionality improves clarity and usability when working with CVLs in exported Excel files, ensuring a more streamlined and efficient process.
Workflow
- It has been implemented that the workflow now filters workflow assignment information based on the user's segment. This enhancement ensures that users receive only the relevant entity counts in their workflow assignment details.
Brand Store
- It has been implemented that the Brand Store now supports server-side PDF generation using the Winnovative library to convert HTML to PDF. The generated PDFs are automatically uploaded to Azure Blob Storage, streamlining document handling and enhancing the user experience with efficient conversion and storage.
- It has been implemented that the Brand Store has been enhanced to improve download performance for PDFs. This optimization is designed to provide a better user experience by streamlining the download process, and minimizing the need for extensive configurations, setups, or multiple clicks when downloading PDFs.
- It has been implemented that a time-triggered event has been added to the Brand Store to automate the cleanup of downloadable files stored in the blob. This enhancement ensures the sustainability of the store's blob storage by efficiently managing storage space and preventing the accumulation of outdated or unnecessary files.
- It has been implemented that the Brand Store now supports wildcard search functionality for product searching. This improvement enhances the accuracy and relevance of search results delivered by the content delivery system, providing users with a more intuitive and efficient product search experience.
-
It has been implemented that the Brand Store now includes clarified terminology for settings related to multi-value search configuration. As a Brand Store Manager configuring the store, this enhancement ensures that the setting's purpose and behavior are easily understandable, enabling accurate configuration and alignment with expected outcomes.
Please see below for the deployed bug fixes:
General
-
We have applied a solution to ensure that the invalid operator error no longer occurs when creating a link rule via the REST API. This fix enhances the reliability and functionality of the API, allowing link rules to be created seamlessly without errors.
-
We have applied a solution to ensure that, as a user of the RestAPI working with LinkRules, you can now correctly map and store the language of a link rule. This fix resolves previous issues with language handling, ensuring accurate and reliable storage of language-specific data for link rules.
-
We have applied a solution to ensure that the Excel export functionality for ODL entities with empty fields now operates correctly. The exported Excel file will consistently include headers and the sys_id column, even when some fields are empty. This fix aligns with user expectations by ensuring all necessary information is present in the export, enhancing the usability and completeness of the exported data.
-
We have applied a solution to ensure that the Control Center UI now handles spaces in extension setting keys consistently when saving. The update permits leading spaces and spaces within the key while blocking trailing spaces, ensuring uniform behavior regardless of the entry method.
-
We have applied a solution to resolve the display issue for the GroupTask custom CVL. Newly added roles now correctly appear under TaskAssignedGroupTask in the Portal. This fix enhances the user experience by ensuring role updates are displayed as expected, improving the ability to configure and manage tasks effectively within the Portal.
-
We have applied a solution to ensure that, as a user in the remoting environment working with DataService.GetAllFieldsByFieldType in ODL environments, you can now correctly retrieve the LastModified date of a FieldType. This fix addresses discrepancies where the LastModified date of a FieldType may differ from that of the Entity, ensuring accurate and reliable data retrieval.
- We have applied a solution to improve error messaging when attempting to delete a Category in the Control Center. The updated message now provides clearer and more detailed guidance, specifying whether the Category is associated with a Field or a Restricted Field Permission, enabling users to address dependencies more effectively.
Content Store
-
We have applied a solution to ensure that the Save button is now clickable when editing the resource format configuration for content stores, even after changes have been made to the configuration. This fix resolves the issue, allowing users to save their updates without interruption, thereby improving the efficiency and reliability of the configuration 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
1 comment
When exporting out using the include cvl keys and values in export,
I get a excel error that says this
Thanks!
I ran it a few more times and it does seem to be working now without the errors
Please sign in to leave a comment.