An application contains a flow action with an Apply to: class of TRB-HRApps-Work-Feedback in a locked ruleset. When updating the application, you save the existing flow action into a new minor version of the ruleset this time applied to TRB’HRApps-Work so it can be used by more than one case type.
How do you prevent the application from using the rule in TRB-HRApps-Work-Feedback?
A . Save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Blocked".
B . Save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Withdrawn".
C . Save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Not available".
D . Save an additional new version of the flow action applied to TRB-HRApps-Work and set the availability to "Final".
Answer: B
Explanation:
To prevent the application from using the rule in TRB-HRApps-Work-Feedback, you would save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Withdrawn". This marks the rule as no longer valid for use in the application.
Reference: Pega official documentation on rule availability.
Latest PEGACPSSA23V1 Dumps Valid Version with 141 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund