You are working on an update to an application which only affects some rules for a certain case type. For migration to a production system, the customer wants the updated rules released as a new patch version of the application ruleset.
Flow do you create the new ruleset version?
To release updated rules as a new patch version of the application ruleset, the correct approach is to lock the current ruleset and then roll (increment) the ruleset version. This method ensures that the changes are managed within the appropriate version without affecting other parts of the application. Skimming or merging rules would be excessive for a patch update, and creating a branched ruleset is more suited for extensive changes or parallel development.
Skim is too heavy for 'some rules in patch version', So answer is C
Answer should be 'C'
as per pega SSA track for Minor and Major use Skimming while for Patch is rock and roll. so answer is C