Câu 10: PEGACSSA72V1: Certified Senior System Architect (CSSA) 72V1
An application contains a flow action in a specific case type class. When updating the application, you save the existing flow action into a higher class so it can be used by more than one case type. How do you prevent the application from using the rule in the child class?
Nội dung câu hỏi
An application contains a flow action in a specific case type class. When updating the application, you save the existing flow action into a higher class so it can be used by more than one case type. How do you prevent the application from using the rule in the child class?
Các lựa chọn
Đáp án được giữ gọn theo nhãn A, B, C, D trong phần bình chọn tương tác.
- A. Save an additional new version of the flow action applied to the parent class and set the availability to "Final".
- B. Save an additional new version of the flow action applied to the child class and set the availability to "Withdrawn". — đáp án hiện tại
- C. Save an additional new version of the flow action applied to the child class and set the availability to "Not available".
- D. Save an additional new version of the flow action applied to the child class and set the availability to "Blocked".
In Pega Rule Resolution: 1. **Withdrawn Availability:** Setting a rule's availability to **"Withdrawn"** masks/blinds that specific instance of the rule and any other instances of the rule with the same name in the same class (or child classes) within that ruleset version or lower. Rule resolution will bypass the child class instance entirely and continue searching up the class hierarchy to find the generalized rule in the parent class (`-Work`). 2. **Blocked vs. Withdrawn:** Setting a rule to **"Blocked"** halts rule resolution immediately and throws an error, whereas **"Withdrawn"** allows rule resolution to fall back to higher parent classes in the class inheritance hierarchy.
Cộng đồng
0 bình luận công khai. Tên thành viên được ẩn một phần.