Constraint Rule maintenance is a batch job that must be run whenever changes are made to rule conditions and when you upgrade to a new version of CPQ.
- Adding or removing a constraint rule.
- Adding or removing a constraint rule condition.
- Modifying anything in a constraint rule condition.
Users who are going to run Constraint Rule Maintenance must have read/write access to ProductConstraintView__c object . All CPQ users must have at least read access. These users should also have ProductConstraintView Visualforce page access and Apex class access enabled.
If the Constraint Rule Maintenance tab is not already available, you can add it as follows:
- Go to App Setup > Create > Apps and click Edit beside Apps Apttus Batch Updates.
- Add Constraint Rule Maintenance and click Save. The tab should now be available.
If the tab is still not available, as a workaround you can manually append apex/Apttus_Config2__ProductConstraint View to your URL in the address bar.
To run a constraint rule maintenance job
- Go to the Constraint Rule Maintenance tab.
- Click Update All.
The batch job is executed. The administration task is complete and an updated history for all the batch jobs is displayed. The key item to observe is Status. When Completed is displayed it means the job has run successfully, even if the percentage indicator remains at 0%.
When you run the Constraint Rule Maintenance job, CPQ inserts new rule records without affecting existing records and the quotes with existing records.
Providing Scalability in Constraint Rules
Despite you have configured large number of constraint rules for your products, CPQ executes the Constraint Rule Maintenance Job seamlessly.
You can set upto 10000 constraint rules and 100 conditions for a single constraint rule in order to meet your business requirements, which in turn gives you flexibility to upscale your product configuration.