List of Features
No. | Feature | Description |
1. | Enhancement in Enrich Only Channel Consolidation | A new configuration option allows users to specify which contributing channels are permitted to create new consolidated SKUs. Users can now configure each contributing channel whether it is allowed to:
This configuration parameter determines which contributing channels are permitted to add new consolidated SKUs and which can only update existing ones. How It Works:
|
2. | Item ID Based Matching Configuration for Enrich-Only Channels | Users can now configure Item ID based matching logic between Source and Target catalogs within Enrich Only channels. Item ID is available as a selectable attribute for both Source and Target during the Item Matching Configuration step. The enhancement supports multiple matching scenarios:
When Item ID is selected in either Source or Target attributes, Case-Sensitive Matching is automatically enabled and locked to ensure accurate and consistent SKU matching. This improvement provides greater flexibility and precision when configuring catalog enrichment workflows. |
3. | Consistent ordering of attribute groups and attributes in Product 360 screen | Attribute groups and the attributes within each product are now displayed in ascending order during product creation in the Product 360 screen. Attributes within each group are sorted alphabetically to ensure consistency across sessions. This improvement eliminates inconsistent ordering when restarting the product creation flow and enhances overall usability. |
4. | Configurable Digital Asset Linkage Type Support in Custom Exports | The platform now supports Digital Asset (DA) Linkage Type configuration in Custom Export, enabling seamless integration with external systems. Key Capabilities:
This enhancement ensures precise digital asset classification across exports, onboarding workflows, and downstream integrations, enabling accurate asset delivery to external platforms and improving overall data consistency. |
List of Bug Fixes
No. | Module | Bug Fixes |
1. | SP | Deleting a category template in Draft status fails with an unexpected error when the template contains both Enforce UOM and Enforce LOV constraints configured on the Field Formatting screen. |
2. | PCC | The catalog selection field does not display a dropdown list of available catalogs and returns an error when the user starts typing, instead of showing valid catalog options. |