List of Features:
No. | Feature | Description |
1. | Session Timeout Handling in PCC | Session timeout handling in PCC has been improved to prevent users from navigating across screens after session expiry. Previously, users could continue accessing different pages after the session had expired and only encountered the session expiry message when attempting to submit data. The system now immediately redirects users to the login page upon session expiry, ensuring a more secure and consistent user experience. |
2. | Introducing AI Mapping Finalization Control for Option 3 | Introduced a new configuration to control who can finalize AI Mapping recommendations in Option 3. Users can now choose between three options: Both (Distributor and Supplier), Distributor Only, or Supplier Only. Based on the selected configuration, only the designated user(s) can finalize the mapping, after which the import process is automatically triggered. This enhancement provides greater control over the mapping workflow, improves governance, and streamlines the import process. |
3. | Template Attribute Mapping Rule for Value and UOM Separation in SOP | Enhanced the SOP attribute mapping process to support automatic separation of values and their corresponding Units of Measure (UOM). Attributes containing combined value and UOM inputs (e.g., “100 kg”) are now parsed to store the numeric value and UOM in their respective fields. The enhancement includes validation of UOMs against the system master data, with support for dynamically adding new UOMs if not already present. It also supports predefined (static) UOM values for applicable attributes, ensuring consistent and accurate mapping without additional processing. This improvement integrates seamlessly into the existing transformation workflow and ensures more accurate, standardized, and reliable handling of value and UOM data across SOP. |
4. | Fully Custom Data Quality Score (DQS) | Introduced a fully customizable Data Quality Score (DQS) feature for SKUs. DQS rules, thresholds, and scoring behaviour can now be managed dynamically without requiring code changes. This enhancement provides:
This enhancement improves flexibility in SKU quality validation and supports varying business and data governance requirements. |
5. | SKU - Domain Relationship Metadata Support in GET and POST API | Enhanced the SKU GET and POST APIs to support domain relationship metadata, enabling users to retrieve and manage relationships between domain attribute values (such as Brand, Manufacturer, Country, and State) along with their associated relationship attributes (e.g., Discount, Margin, Size). A new optional GET parameter, IncludeRelationshipAttributeData, returns a domainRelationshipMetaData section with linked domain pairs and attributes. The POST API now supports ingestion of this metadata via a structured payload. This improves data consistency, context, and integration capabilities for domain relationships. |
6. | Inter-Entity Relationship Enhancement (Phase 1) SKU–Domain | Introduced support for Inter Entity Relationships, enabling SKUs to be linked with related entities such as SKU, Domains, and Digital Assets. For example: A single SKU like “Running Shoes” can now be associated with multiple vendors (PUMA, Adidas, Sparx) along with vendor-specific details such as address, country, and ratings. By enabling relationship attributes for SKU–Domain relationships, users can now capture relationship-specific details in a structured and scalable way. Users can associate relationship attributes with both Supplier-Specific Domains and Unspecified Domains. SKU–Domain relationships are now visible within the Product 360 screen, allowing users to view these associations directly in the product context. This capability is currently supported for SKU–Domain relationships and will be extended to additional entity relationships in future phases. |
7. | Interchange Mapper UI Improvements for Package Attribute Mapping | Enhanced the Interchange Mapper UI to improve support for package attribute mapping and ensure proper handling of entity value. Previously, the UI did not provide a mechanism to select or retain package attribute names in the screen. With this enhancement:
These updates align the package mapping experience with SKU attribute mapping, improving consistency and reliability. |
List of Bug Fixes:
No. | Module | Bug Fixes |
1. | SP | SKU Onboarding Portal Improvements:
|
2. | PCC | Searching for a non-existent Domain Record in the filter screen no longer redirects users to the Domain Catalog page. The system now retains the user on the filter screen and displays an appropriate “Domain Record Not Found” message. |
3. | PCC | Updates to Digital Asset linkage types in the catalog were not retained after saving. The system now correctly persists linkage type changes in the Digital Asset mapping screen. |
4. | PCC | Data from BIF and standard horizontal imports no longer requires re-importing, as it now loads successfully into the catalog on the first attempt. |
5. | PCC | Digital Asset links generated in the manifest report were using an outdated URL, resulting in incorrect asset references. The system now uses the updated base URL, ensuring all Digital Asset links point to the correct asset hosting location. |
6. | SP | Fixed an issue in the SKU Onboarding Portal where uploading data through Option 2 could create duplicate attributes in the supplier catalog when attribute names contained leading or trailing spaces. |
7. | PCC | The Digital Asset Manifest report now returns all linked digital assets for SKUs and corrects active status handling, ensuring consistency across systems. |
8. | PCC | Improved the performance of the Custom Export template field selection by reducing load time. The API previously fetched all attributes (~5,000+) in a single request, resulting in delays exceeding 40 seconds. Server-side pagination has been introduced to load data incrementally, significantly improving responsiveness and user experience during export configuration. |
9. | SP | Resolved an issue during data import using Option 1 and Option 3 in SOP where imports were failing with the error “Multiple taxonomy node found using name” when duplicate taxonomy node names existed in the supplier catalog. |
10. | PCC | Improved taxonomy loading performance in PCC, reducing taxonomy data and default taxonomy node selection load times in the Import Configuration screen to under 5 seconds. |