Comparison and deployment scenarios
This reference provides a comprehensive overview of comparison and deployment scenarios for product catalogs, focusing on product configurations, source and target tenants, and deployment manager displays.
Primary Comparison Key SKU
Primary Comparison Key Product Name
Rate Plan Deployment Scenarios
Rate Plan Charges Deployment Scenarios
Known system behavior with natural keys or product number
- Always standardize the prefix for Product Number in source and target tenant. A difference in the configurations of prefixes in source and target will result in comparison being displayed as different every time.
- In the pre-deployment phase, the tenant is configured with a set of products, rate plans, and rate plan charges. Subsequently, during the post-deployment phase, newly introduced products, rate plans, and rate plan charges will be assigned incremental product numbers derived from the latest numbers already present in the target tenant. It is recommended to select auto-generate Product Number in this scenario. If not, the system will throw a validation error.
- When deploying products in the target tenant which does not have existing products, rate plans, rate plan charges, either the clone of Product Number or auto generate product number options may be selected for deployments.
- If deploying a newly configured product, rate plan or rate plan charge between tenants that have been already baselined accurately and up-to-date, the option of cloning product number from source to target may be selected.