Adding instructions to a Step:

In Pega, instructions for a step are runtime directives for the end-user. When a user processes a case and reaches a specific assignment (step), these instructions are displayed on the screen. The primary purpose is to guide the user on the specific actions they need to perform to successfully complete that task, ensuring consistency and accuracy. This text clarifies what information to enter or what process to follow for that particular step in the case life cycle.

A. Describes the business value of the step.

Business value is a higher-level concept documented in business requirement artifacts, not in the runtime instructions for an end-user.

B. Defines the step.

A step is defined by its name, the view it uses, and its associated automation, not solely by its user-facing instructions.

D. Instructs an app developer how to build the step.

Developer guidance is located in design documents, technical specifications, or implementation notes, not in a field intended for end-user display.

1. Pega Academy: Pega Certified Business Architect (PCBA) 24 course

"Designing a case life cycle" module

"Adding instructions to a step" lesson. The lesson explicitly states

"As a business architect

you add instructions to a step to guide users on how to complete that step." This directly supports the purpose of providing action-oriented guidance to the user.

2. Pega Documentation: Case management > Case life cycle > Steps > Configuring a step. In the section describing the configuration options for a step

the "Instructions for user" field is defined as follows: "Enter text that guides a user to complete the assignment." This confirms the instructions are for the user performing the task.