Product catalog terminologies and facts
This reference defines Product Catalog statuses in the List view interface and outlines key deployment behaviors for products, rate plans, and rate plan charges.
Product Catalog terminologies in List view interface
| Status | Description |
|---|---|
| Submitted | The compare job is initiated and is in queue. |
| Compare in Progress | The system is retrieving and validating data in the backend. |
| Compare Done | The comparison between source and target tenant is complete. |
| Compare Failed | The comparison job has failed due to a breakage in the backend integration logic. |
| Canceled | The comparison job is canceled if the job runs for more than 15 minutes and is considered a failure. The user can initiate a new job with the same tenants. |
| View Details | The comparison results are available for validation and deployment on the compare screen. |
| Auto-Generate SKU | The deployment manager will generate a new SKU based on the last SKU present in the target tenant while creating a new product. |
| Clone Source Tenant SKU | The deployment manager will clone the product, including the SKU, from the source to the target tenant. |
Deployment facts for Product, Rate Plans, and Rate Plan Charges
-
If you select to validate and deploy a product name as the primary key for comparison, then the system behaves as follows based on the selection:
-
Product Name - If multiple products have the same name in the source tenant, Deployment Manager does not support comparison and deployments of these products.
-
SKU and Product Number - If the user selects SKU as the primary comparison key, the products with no validation will be displayed for validation and deployment.
-
-
Deployment Manager does not support comparing and deploying Rate Plans and Rate Plan Charges with the same name. The primary key for comparing the Rate Plans and Rate Plan Charges is the name; hence multiple rate plans with the same name are not compared and displayed by the compare screen.
-
Product catalog deployments deal with a large volume of data, and the deployment manager does not compare and display the products configured only in the target.