PEGAPCBA87V1-PRACTICE-QUESTIONS practice question 3 of 15

Which scenario is a use case for the Wait step?

Full set: 74 questions
Answer options
A: The customer needs to log in to their account before receiving a membership discount on an online purchase.
B: An agent need to send a confirmation email to an insured customer after they complete a form.
C: A payroll user cannot process a salary increase until the department manager approves the increase. Correct answer
D: The customer cannot complete an application for a checking account until a bank representative reviews their credit report.
Correct Answer:
C. A payroll user cannot process a salary increase until the department manager approves the increase.
Explanation

The Wait step is a configuration in a Pega case life cycle designed to pause the processing of a case until a specific condition is met. This is typically used for time-based delays or for case dependencies. Scenario C is a classic example of a case dependency: the main case (processing a salary increase) must be paused until a dependent process (the manager's approval, often modeled as a subcase) reaches a resolution status (e.g., "Approved"). The Wait step enforces this dependency, ensuring the case does not proceed until the required approval is secured.

Why Incorrect

A. This describes a prerequisite or a validation check. The system checks for a logged-in state before allowing an action, which is not the same as pausing an in-flight case.
B. This is an automated action, such as a 'Send Email' utility, that executes after a step is completed. It does not involve pausing the case to wait for an event.
D. While this also describes a dependency, scenario C ("cannot process") is a more precise description of the Wait step's function, which is to halt the backend case processing. Scenario D ("cannot complete") describes the user-facing symptom rather than the underlying case management mechanism.

References

1. Pega Platform 8.7 Documentation, "Adding a Wait step to a case": This document outlines the two main use cases for the Wait step: pausing for a set duration (timer) or pausing until another case dependency is resolved. The documentation states, "For a case dependency, the current case pauses until the dependent case or all dependent cases reach a specific status." The approval scenario (C) is a direct implementation of this principle, where the salary increase case waits for the approval subcase to reach a status like 'Approved'.

2. Pega Academy, "Case Management" (8.7) Module, "Pausing and resuming case processing" Lesson: This lesson explains that a Wait step is used to enforce dependencies between cases. It provides examples such as a parent case waiting for one or all of its subcases to be resolved before it can continue. A manager's approval is a canonical example of a process that would be configured as a subcase, requiring the parent case to wait.

3. Pega Platform 8.7 Documentation, "Flow shapes - Wait": This reference details the configuration of the Wait shape. It specifies the options for "Case Dependency" which include waiting for a case to reach a specific status. This directly supports the implementation described in scenario C, where the salary increase process waits for the "Approved" status from the manager's approval case.

Scroll to Top