...
When you want to change a validation to a PC for a QA that is the factor of premium calculation, please make sure that you provide the rate for the factor (QA) that can drop below the limit when user approve the PC. For ex: if you have PC for MainDriverAge < 18, but don’t have rate for MainDriverAge < 18, you can get the system error because system can’t find the rate to calculate premium.
Please verify the premium after converting validation to PC and adding factor value.
When one QA needs multiple rules setup on it, please use the different name for each rule to not confuse system when running the rules. If several rules have the same name, they cannot be displayed correctly in Product Builder tool as well.
On the same QA, please do not setup rules that conflict to each other (same conditions but one is validation, one is PC). For ex: one validation rule for MainDriverAge < 18, and one PC rule for the same condition “MainDriverAge < 18”. This will cause system running unexpectedly (you might see validation is raised instead of PC or vice versa). Please remove one.
Please see an example here: change a validation when MainDriverAge < 18 to purchase constraint.
Whenever you got error when updating product version, you can always roll back. Roll back to previous product version if you got error with the current active version
...