Question
HCL
IN
Last activity: 3 Jul 2024 1:54 EDT
Which is the scenario where Wait Step best fits ?
Need a help in the following questions:
Which scenario requires Wait Step ?
A. A customer needs to login before receiving membership discount
B. A agent needs to send a confirmation email to an insured customer after they complete form
C. A payroll user cannot process the salary increase until the department manager approves the increase
D. The customer cannot complete an application for a checking account until a bank representative reviews their credit report.
In my view, D should be the right answer. But the actual right answer given is C. Can't C be implemented using Approval/Reject step ?
Accepted Solution
Updated: 3 Jul 2024 1:54 EDT
Eclatprime Digital Private Limited
AU
Hi @SPD Murthy
The correct understanding and usage of the Wait step in Pega scenarios can be clarified by understanding what the Wait step is specifically designed for. The Wait step in Pega is used to pause the execution of a case until a certain condition is met or a specific event occurs.
Explanation of the Scenarios:
A. A customer needs to log in before receiving a membership discount.
- This scenario doesn't fit the Wait step usage because the login process should be a prerequisite or initial step rather than something that requires a conditional wait.
B. An agent needs to send a confirmation email to an insured customer after they complete a form.
- This scenario involves a simple sequence of actions (completing the form and then sending an email) and doesn't necessarily require waiting for an external condition to be met.
C. A payroll user cannot process the salary increase until the department manager approves the increase.
Hi @SPD Murthy
The correct understanding and usage of the Wait step in Pega scenarios can be clarified by understanding what the Wait step is specifically designed for. The Wait step in Pega is used to pause the execution of a case until a certain condition is met or a specific event occurs.
Explanation of the Scenarios:
A. A customer needs to log in before receiving a membership discount.
- This scenario doesn't fit the Wait step usage because the login process should be a prerequisite or initial step rather than something that requires a conditional wait.
B. An agent needs to send a confirmation email to an insured customer after they complete a form.
- This scenario involves a simple sequence of actions (completing the form and then sending an email) and doesn't necessarily require waiting for an external condition to be met.
C. A payroll user cannot process the salary increase until the department manager approves the increase.
- This scenario involves a dependent action (processing a salary increase) that cannot proceed until a specific event (manager's approval) occurs. This is exactly what the Wait step is designed for: to pause the case until an external event (the approval) is completed.
- While it is true that an Approval/Reject step can handle the approval process itself, the Wait step ensures that the case does not proceed to further processing steps until the approval is confirmed. This step pauses the workflow explicitly until the condition (approval) is satisfied.
D. The customer cannot complete an application for a checking account until a bank representative reviews their credit report.
- This scenario indeed involves waiting for an external action (credit report review). However, the Wait step is more appropriately used when the case needs to be paused for an event or condition that is more complex or not directly part of the immediate workflow steps. In this case, while the review is an external action, it’s usually implemented as a review step followed by a decision point, rather than a condition requiring a Wait step.
Why C is the Correct Answer:
The key point with scenario C is the explicit dependency on an external condition (manager's approval) before proceeding. The Wait step in Pega is optimal here because:
-
Pause Until Condition is Met: The Wait step allows the case to be paused until the manager’s approval is received, ensuring no further action is taken until the condition is satisfied.
-
External Event Handling: It explicitly models the need to wait for an event (approval) that is not guaranteed to happen immediately.
-
Case Progression Control: While the Approval/Reject step handles the approval process, the Wait step provides an explicit pause in the workflow until the condition (approval) is met, making the case status and progression clear and manageable.
In conclusion, C is the right answer because it involves waiting for an approval before the case can proceed. This is a textbook use case for the Wait step in Pega, ensuring that the case only moves forward once the necessary condition (manager's approval) is fulfilled.
Rulesstack Private Limited
IN
Hi @SPD Murthy,
Yes the correct answer is C,
C. A payroll user cannot process the salary increase until the department manager approves the increase
Here's why:
- In scenario (A), the wait step isn't necessary because the system can immediately check the login status.
- In scenario (B), the email can be sent automatically after form completion without a wait.
- In scenario (D), the application process can proceed until the credit report review is complete.
In scenario (C), the payroll user's action (processing salary increase) depends on an external action (manager approval). A wait step is needed to ensure the manager has had a chance to review and approve before the user proceeds.
.
Thanks,
Mohd Qizer Uddin
HCL
IN
Thanks for the reply.
Do we have to look in this way : In (C), the payroll cannot even start the processing before the manager approves the increase. But in (D), the customer can still proceed with the application even though he cannot complete, until the bank representative has reviewed the credit report ?
Eclatprime Digital Private Limited
IN
Hi @SPD Murthy,
In Pega, the Wait step is used to pause the progression of a case until a specific condition is met. This can be particularly useful in various business scenarios where a delay or a specific event needs to occur before the case can move forward. Using the Wait step, you can ensure that the case accurately reflects the real-world process and dependencies, enhancing the workflow's reliability and efficiency.
In this option C, the case will wait for the managers response for the salary increase, if he doesn't increase the salary then previous salary will be credited. So here we cannot use the Approve/Reject shape. So best option is to be use the Wait shape.
Thanks,
Sai G
HCL
IN
Thanks for the reply.
If we use Wait Step and the manager rejects, then previous salary will be creditted. The same can still be achieved using Approval/Reject step. On rejection, the previous salary can be credited. On approval, the new salary.
Lantiqx Systems India Private Limited
IN
Hi,
I think both D is correct. As we can set the wait shape with the case status until the review-completed case should not process.
Regards,
Mamatha Adiraju
Eclatprime Digital Private Limited
IN
@SPD Murthy Option C can be implemented using approve/reject step. But here the thing to find the best optimal solution for a problem. if i will go with option C I am getting the result as per the wait shape because wait shape logic correctly defined there to have a dependency on a case status Definitely D can work via other methods easily because its a credit score task where it can proceed. C is the correct answers
Maantic Inc
IN
C is correct because the process has to wait for the manager to approve based on which case dependency can be configured.
Eclatprime Digital Private Limited
AU
Hi @SPD Murthy, As @Somil0607 said, One requirement can have multiple solutions but we need to choose the best fits in terms of configuration, maintenance and complexity. So option C suits best. Thanks
Accepted Solution
Updated: 3 Jul 2024 1:54 EDT
Eclatprime Digital Private Limited
AU
Hi @SPD Murthy
The correct understanding and usage of the Wait step in Pega scenarios can be clarified by understanding what the Wait step is specifically designed for. The Wait step in Pega is used to pause the execution of a case until a certain condition is met or a specific event occurs.
Explanation of the Scenarios:
A. A customer needs to log in before receiving a membership discount.
- This scenario doesn't fit the Wait step usage because the login process should be a prerequisite or initial step rather than something that requires a conditional wait.
B. An agent needs to send a confirmation email to an insured customer after they complete a form.
- This scenario involves a simple sequence of actions (completing the form and then sending an email) and doesn't necessarily require waiting for an external condition to be met.
C. A payroll user cannot process the salary increase until the department manager approves the increase.
Hi @SPD Murthy
The correct understanding and usage of the Wait step in Pega scenarios can be clarified by understanding what the Wait step is specifically designed for. The Wait step in Pega is used to pause the execution of a case until a certain condition is met or a specific event occurs.
Explanation of the Scenarios:
A. A customer needs to log in before receiving a membership discount.
- This scenario doesn't fit the Wait step usage because the login process should be a prerequisite or initial step rather than something that requires a conditional wait.
B. An agent needs to send a confirmation email to an insured customer after they complete a form.
- This scenario involves a simple sequence of actions (completing the form and then sending an email) and doesn't necessarily require waiting for an external condition to be met.
C. A payroll user cannot process the salary increase until the department manager approves the increase.
- This scenario involves a dependent action (processing a salary increase) that cannot proceed until a specific event (manager's approval) occurs. This is exactly what the Wait step is designed for: to pause the case until an external event (the approval) is completed.
- While it is true that an Approval/Reject step can handle the approval process itself, the Wait step ensures that the case does not proceed to further processing steps until the approval is confirmed. This step pauses the workflow explicitly until the condition (approval) is satisfied.
D. The customer cannot complete an application for a checking account until a bank representative reviews their credit report.
- This scenario indeed involves waiting for an external action (credit report review). However, the Wait step is more appropriately used when the case needs to be paused for an event or condition that is more complex or not directly part of the immediate workflow steps. In this case, while the review is an external action, it’s usually implemented as a review step followed by a decision point, rather than a condition requiring a Wait step.
Why C is the Correct Answer:
The key point with scenario C is the explicit dependency on an external condition (manager's approval) before proceeding. The Wait step in Pega is optimal here because:
-
Pause Until Condition is Met: The Wait step allows the case to be paused until the manager’s approval is received, ensuring no further action is taken until the condition is satisfied.
-
External Event Handling: It explicitly models the need to wait for an event (approval) that is not guaranteed to happen immediately.
-
Case Progression Control: While the Approval/Reject step handles the approval process, the Wait step provides an explicit pause in the workflow until the condition (approval) is met, making the case status and progression clear and manageable.
In conclusion, C is the right answer because it involves waiting for an approval before the case can proceed. This is a textbook use case for the Wait step in Pega, ensuring that the case only moves forward once the necessary condition (manager's approval) is fulfilled.