List of Features
No. | Feature | Description |
1. | Ability to map one input field to multiple template entities on the AI Mapping Finalization screen in SOP | Enhanced the AI Mapping Finalization screen to allow users to map a single input field in the uploaded file to multiple target entities on the AI mapping finalization screen in SOP. The AI mapping returns all recommended template fields for an input field instead of only the highest-scoring one. Users can accept multiple AI recommendations for an identified field in the uploaded file or create the mappings manually. The input value is applied to each mapped target field, and the mapping status changes to Done when at least one mapping is accepted or created manually. |
List of Improvements
No. | Improvement | Description |
1. | Support for node mapping at Taxonomy Root node and Branch node levels in SOP | Added support for selecting Root nodes and Branch nodes as mapping targets on the Node Mapping screen during template creation in SOP. Users can select Root nodes or Branch nodes in the Target Taxonomy tree and add rules or mapping conditions directly to those nodes. |
2. | Duplicate column header validation for uploaded files in SOP | Added validation to reject Excel (.xlsx, .xlsm, and .xls), CSV, and TXT files containing duplicate column headers during AI mapping. Leading and trailing spaces are removed before headers are compared. The comparison is case-sensitive. Files containing duplicate headers are not processed, and an appropriate message is recorded in the error file. |
3. | Improved SKU search performance for large result sets in PCC | Enhanced SKU search processing to retrieve the records required for the requested page without first retrieving the complete set of matching SKUs. The improvement applies to paginated SKU results, including product listing, Advanced SKU Search, and applicable Public API requests. |
4. | Improved Audit Trail processing performance on the Product 360-degree screen in PCC | Enhanced Audit Trail processing to reduce delays when importing SKU data and saving changes on the Product 360-degree screen in PCC. |
5. | Optimized activity logging in PCC | Removed the creation of unused activity records when users save SKUs, create or update SKUs through APIs, import product data, or perform bulk updates. |
List of Bug Fixes
No. | Module | Problem Summary | Resolution |
1. | PCC | Standard Horizontal Excel and Standard Horizontal Delimited exports can return zero SKUs without displaying an error when certain saved filter conditions are used, even when matching SKUs exist. The same issue can cause additional empty Digital Asset columns in Custom Export when a matching saved filter is applied. | Corrected saved filter processing so that the affected exports return matching SKUs and Custom Export correctly determines the Digital Asset columns required by the selected settings and filter conditions. |
2. | PCC | On Product 360-degree screen, the “Add Pending Attributes” option is not consistently available when an attribute group contains unpopulated attributes. In some cases, all attributes are displayed automatically, resulting in inconsistent attribute group behavior. | Corrected attribute group display behavior and the availability of “Add Pending Attributes” so users can consistently view populated attributes and add the remaining attributes. |
3. | PCC | During synchronization, a document can be selected as the Primary Digital Asset even when the incoming data includes a photo for the same SKU. Override synchronization can also fail when no Primary Digital Asset is specified. | Corrected Digital Asset type handling and primary selection during synchronization. |
4. | PCC | When a SKU is created with a manually entered Item ID, the SKU Title and derived attribute generated by the Formula Master take the value of the Item ID instead of a system-generated value. | Corrected the Internal Unique SKU Key formula section to always use the internal SKU key, so that generated SKU Titles and derived attributes no longer reflect the entered Item ID. |
5. | SOP | Users cannot create a Category Template using a root node that has no child nodes. Although the root is the only node in the taxonomy, it is not treated as a leaf node for template creation. | Updated Category Template creation to recognize a root node without child nodes as a leaf node, allowing users to create a template directly from it without adding child nodes to the taxonomy. |