The AccountManage ruleset contains the following versions of a service level named ReviewAccountChange:
The application is being updated with a new patch version of the AccountManage ruleset. As part of the update, the service level is no longer specialized for AccountOpen cases. In the updated ruleset, the circumstancing in the class group applies to all case types.
Which option do you use to reset the circumstancing for the AccountOpen case type?
To reset the circumstancing for the AccountOpen case type, the correct approach is to copy the non-circumstanced rule to the AccountOpen class and select the base rule option. This forces the system to prioritize the base rule, effectively ignoring the circumstanced versions in the specialized class, thus meeting the requirement of no longer specializing the service level for AccountOpen cases.
Should be D. Copy the non-circumstanced rule to the AccountOpen class and select the base rule option. Because the requirement is to remove other circumstances in new patch version. Other will be working only with specific circumstances (please delete the other comment)
should be B , requirement said its for all case types , if you copy the non circumstanced rule for account open , circusntaced rule will be picked in work class
Agree. I you retired the circumstanced, you find an 'base-rule by default'
Answer is D, withdrawn rules does not affect circumstanced rules at runtime, the correct approach is to copy the non-circumstances rule into the child class and select the base rule flag, this will force the system to ignore the circumstanced versions in the specialised class
B. or C. I personally lean to B, because there is no requirement to show error when Silver will be used. A definitely not correct
circumstance rule have their own availability setting. if you with draw a rule itself doesnot masks the circumstance rules. so Answer is D. if the higher version has base rule selected then all previous c. rules are masked.