List of Features
No. | Feature | Description |
1. | Enhanced GraingerSKUs API to Return Linked Digital Assets | Currently, the GraingerSKUs GET API does not return digital assets linked to SKUs, limiting visibility of associated asset data. This has been enhanced by including digital assets for each SKU in the API response, following the same JSON structure used in the Public SKU API (i.e., as an array under each SKU). This improvement ensures consistent data representation and enables consumers to access complete SKU-related information in a single response. |
2. | Introducing Auto-Publish & Auto-Approve for SKUs in SKU Onboarding Portal Workflow | Introduced configurable automation for SKU status transitions based on Template–Supplier mappings. Distributors can now enable Auto Publish, and Auto Approve flags to automatically progress SKUs through the defined workflow sequence (Valid → Published → Approved → Accepted → Onboarded). When enabled, a scheduler-driven orchestration processes SKUs sequentially based on their current status and triggers existing APIs to advance them to the next stage. For example, SKUs in “Valid” status are automatically published if Auto Publish is enabled, and subsequently approved if Auto Approve is enabled, while existing automation continues to manage acceptance and onboarding stages. This enhancement streamlines the onboarding process, reduces manual effort, and ensures consistent workflow execution. It also incorporates duplicate prevention (idempotency) by selecting SKUs strictly based on their current status. Once a SKU successfully transitions to the next stage, it is automatically excluded from reprocessing in that step, preventing redundant actions and ensuring data consistency. |
List of Bug Fixes
No. | Module | Bug Fixes |
1. | PCC | The Domain Master import where importing a file with new records but without including existing records caused attribute values of the omitted existing records to be removed is now resolved. |
2. | PCC | Resolved an issue where deleting a supplier displayed an error message (“Something went wrong, please try again later”) even though the supplier was successfully set to an inactive state. |
3. | PCC | The scheduled export failed to generate child exports due to a missing condition reference. The issue occurred because the associated condition was deleted from the Condition Master, preventing the export from executing. The system now restricts deletion of conditions that are linked to scheduled or in-progress exports, ensuring uninterrupted execution. |
4. | PCC | Attribute property values for domains were not displayed on the UI after linking the domain to SKUs. The system now correctly shows the associated attribute properties when the domain is linked. |
5. | SP | Side navigation buttons and field rendering issues in the SKU Onboarding Portal while editing SKUs:
|
6. | PCC | Resolved an issue where importing multiple domains with the same attribute resulted in the attribute being created in only one domain. The system now correctly creates the attribute in each respective domain when the same attribute is included across multiple domains in the import file. |
7. | SP | Multi-select LOV fields in both Supplier and Distributor side no longer allow duplicate selection of the same value via the magic wand, preventing repeated entries for a single product record. |