An order fulfillment case type allows a customer to update user profile information during the order placement stage. The user profile consists of…

Optional actions (formerly known as local actions) are the standard Pega feature for allowing users to perform discretionary, single-task activities that are not part of the primary case path. By configuring an optional action for each user profile page (Account ID, Contact Info, Open Orders), you empower the customer to update any of this information individually and at any point during the order placement stage. This design provides flexibility without disrupting the main workflow of placing an order.

B. Add an alternate stage to the case life cycle.

An alternate stage is used to model exceptions or deviations from the primary case path, not for optional, user-initiated tasks.

C. Add a button for each profile page to each assignment.

While technically feasible, this is not the standard Pega design pattern. Optional actions are the designated, out-of-the-box feature for this purpose, providing better maintainability.

D. Add an optional process to the case workflow.

An optional process is designed for a multi-step sequence that a user can choose to run. For updating a single page of information, a more granular optional action is the appropriate choice.

---

1. Pega Academy

Business Architect (24.1) Mission

"Case life cycle design" Module

"User actions" Topic.

Reference: This module explains that "An optional action allows a user to perform a single task outside of the primary path of a case." It clarifies that users can launch these actions at any time within a stage or specific assignment

which directly supports the requirement to allow individual updates during the order placement stage.

2. Pega Platform™ 24.1 Documentation

"Adding an optional action to a case type."

Reference: This document states

"Optional actions enable users to perform tasks in any order and at any time

outside of the structured workflow of a case." This directly aligns with the need to allow customers to update profile pages individually and at their convenience.

3. Pega Platform™ 24.1 Documentation

"Alternate stages."

Reference: This section defines the use case for alternate stages: "Use alternate stages to organize process steps that are not part of the normal course of events... For example

a case might transition to an alternate stage if a manager rejects a request." This confirms that alternate stages are for exception handling

making option B incorrect.

4. Pega Platform™ 24.1 Documentation

"Optional processes."

Reference: This document describes an optional process as something users can run "to complete a task that is not a part of the main case workflow." It emphasizes that this is a process (a flow with potentially multiple steps). This distinguishes it from an optional action

which is better suited for the single-screen updates described in the question

making option D less precise than A.