When an ACES XML file with a specified number of catalogs is processed, all catalogs are processed sequentially and marked as Locked until the end of processing, resulting in issues such as re-processing the catalogs, reports (view or visualize the catalog upload report at individual catalog level), and processing throughput.
To address this issue, the catalog-centric file processing functionality is implemented, which provides the capability to process the XML files at the individual catalog level.
Advantages of using catalog-centric file processing functionality:
- Ease of Re-processing: If a catalog fails during file processing, the remaining catalogs will not be locked for re-upload.
- Better Processing Throughput and Scale Support: This allows for more efficient processing of large volumes of data across multiple catalogs.
- Dashboards: This allows you to create catalog-level reports.
Enable Catalog Centric File Processing Configuration (Vendor)
The configuration file enables the vendor to perform catalog-centric file processing functionality, when an XML file is uploaded for processing.
To access the catalog centric file processing functionality, perform the following.
Configuration Details:
In file-splitter-upload-permission-vendor-config.json file, specify the vendor_ownership_ids under data.jsonData object.
File Details:
The following is a sample file-splitter-upload-permission-vendor-config.json configuration file.
{
"metaInfo": {
"dataIndex": "config",
"collectionName": "configObjects",
"responseObjectName": "response"
},
"configObjects": [
{
"id": "file-splitter-upload-permission-vendor-config",
"name": "file-splitter-upload-permission-vendor",
"type": "appconfig",
"data": {
"jsonData": {
"vendor_ownership_ids": ["130376-USA"]
}
}
}
]
}
Load the updated UI configuration for the respective tenant. See Upload Tenant Seed Data in System Administrator's Documentation. After loading the configuration successfully, login with the appropriate credentials.