List of Features
No. | Feature | Description |
1. | Product Dashboard Widgets Now Display Meaningful Empty-State Messages and Illustrations | PCC now displays a neutral illustration instead of the "No Data Found" icon when Product Dashboard widgets have no data to display. Previously, empty widgets displayed a "No Data Found" icon, which could give the impression of an error even when the absence of data was expected, such as when there were no pending reviews or tasks. With this enhancement, the Overall Reviews for Overall Reviews for My Catalog widget, My Task List, and Syndication widgets now display a contextual illustration with user-friendly messages such as All Reviews Completed, All Tasks Completed, and Activate Channels, providing a clearer and more positive dashboard experience. |
2. | Support for Updated ROC Connector Authentication with ‘Client Secret’ key | PCC now includes a new ‘Client Secret’ field in the ROC Connector configuration to support authentication with the latest version of the ROC service. With the ROC service upgraded to a newer version, the additional Client Secret credential is now required to establish a successful connection between PCC and ROC connector. Users can now configure the Client Secret along with the existing ROC connection details during connector setup, ensuring compatibility with the updated authentication requirements and enabling uninterrupted connectivity. |
List of Bug Fixes
No. | Module | Problem Summary | Resolution |
1. | SOP | During supplier catalog import, some digital assets were incorrectly marked as the primary asset. | Updated the SKU onboarding process to correctly assign the primary digital asset based on the imported data. |
2. | SOP | Large templates in the SKU onboarding flow could fail when moving SKUs from Approved to PIM-Ready. | Optimized the SKU Onboarding flow to improve the processing of large templates, enabling reliable transitions from Approved to PIM-Ready for high-volume SKU uploads. |
3. | PCC | Inconsistent field names were displayed on the Package Unit details screen. | Updated the field names on the Package Unit details screen to follow a consistent naming convention. |
4. | SOP | The Node Mapping screen perform ance improvement. | Optimized the UI and API to improve the performance of the Node Mapping screen. |
5. | SOP | A data integrity error could occur when mapping a new supplier to a cloned template, preventing users from proceeding to the Node Mapping step. | Updated the template cloning to allow users to map a new supplier and continue to the Node Mapping step without encountering a data integrity error. |