Pega Flow Design and Workflow Concepts

Decision shapes in Pega do not require separate connectors for every possible return value. You can define a set of possible return values on the Results tab and create connectors only for the specific outcomes you want to handle explicitly. The system allows you to have fewer connectors than total return values, making the design more flexible and efficient.

An Integrator shape in Pega flows is specifically designed to invoke connector rules for external system integration. While it cannot invoke arbitrary service rules, its primary purpose is to call connector rules that interact with external systems. Integrator tasks are not automatically parallel - they execute according to the flow design. Option B correctly identifies the Integrator's core capability.

Pega allows users to create custom Router shapes in addition to the standard routers provided by the system. Custom routers can be configured to meet specific business routing requirements that the standard routers don't address. The statement claiming you cannot create your own routers is false, making Option B (False) the correct answer.

The Split Join shape in Pega enables parallel processing by allowing multiple subflows to execute simultaneously on the current work object. It specifically works with subflows associated with the current work object, not arbitrary work objects. The parent flow resumes only when ALL subflows complete, not just the first one. Option A correctly describes this parallel execution capability.

When an activity doesn't appear in the SmartPrompt for a Utility shape, the most common cause is that the activity hasn't been designated as a Utility activity in its rule configuration. Activities must be specifically set up as Utility-type activities to appear in the Utility shape's activity selector. This is a configuration issue, not a class or initialization problem.

SmartPrompt for Decision shape connectors is enabled by listing all possible return values on the Results tab of the Decision rule. This configuration allows the system to suggest appropriate connectors based on the defined outcomes. The system doesn't automatically enable this feature - you must explicitly configure the return values. Option B correctly identifies this configuration requirement.

A standard process flow in Pega can only have one Start shape to define the entry point of the flow lifecycle. Subflows or different routes can exist, but multiple Start shapes are invalid, making the assertion 'True' incorrect and 'False' the correct answer.

To set a status in an activity (utility) that can be evaluated during flow transitions, Pega uses the TaskStatus-Add method. This adds a custom status to the task list. Java steps, history methods, and transitions themselves do not perform this specific status-adding function.

Decision trees are flow shapes specifically designed for conditional 'if...then' logic in Pega. They evaluate multiple conditions and route flow execution based on the outcomes, making them ideal for complex branching logic. Utility shapes execute activities, Routers direct assignments, and Split for Each handles iteration - none are primarily designed for conditional path execution like Decision trees are.

Work parties represent people, departments, or companies associated with a case. They have a stake in its progress and resolution but do not necessarily perform the processing tasks within the application itself. The other options confuse them with workbaskets, operator records, or case relationships.

To answer this question, the user needs to understand the concept of adding a Connector to an Assignment.

When adding a Connector to an Assignment, the Likelihood associated with the Action represents the probability or chance that the work will follow the specified path. In other words, it is an indication of how likely it is that the work will be completed as planned and that the specified path will be followed.

Option A is incorrect because the Likelihood associated with the Action does not represent the likelihood that a benchmark will be met. A benchmark is a standard or reference point that is used to measure progress or performance, and it is not directly related to the Likelihood associated with the Action.

Option C is also incorrect because the Likelihood associated with the Action does not represent the likelihood that a goal will be met. Although completing the work as planned may contribute to achieving a goal, the Likelihood associated with the Action only represents the probability or chance that the work will follow the specified path.

Option D is incorrect because the Likelihood associated with the Action does not represent the likelihood that a goal will not be met. The Likelihood associated with the Action is a positive indicator of how likely it is that the work will be completed as planned, and it does not represent the likelihood of failure.

Therefore, the correct answer is:

The Answer is: B. An indication of how likely it is that the work follows the specified path.

SmartBuild best practices recommend keeping flows compact, readable, and modular. Spanning a flow across multiple Visio pages indicates excessive complexity and violates the principle of modularity (subflows should be used instead). Having multiple flow actions, subflows, or utilities is standard design.

In Pega, WorkParties represent people, organizations, or other entities interested in or involved with a case (work object) during its lifecycle. A Worklist holds assignments for individual users, a Workbasket holds them for groups, and Workgroups are logical collections of operators.

A local flow action allows users to perform optional actions or update work item details (like uploading an attachment) without advancing the flow configuration along connector paths. Connector flow actions advance the process, whereas templates, correspondence, or assignments themselves do not represent the action to attach a sheet.

Routing an Assignment shape configured for a Worklist (which expects a user router) using a workbasket router like ToWorkBasket causes a routing mismatch at runtime. In Pega, this validation/execution failure suspends the flow execution and transfers control to the FlowProblems flow for troubleshooting.

A workbasket in Pega is a shared pool of assignments that can be processed by any member of a work group, not tied to a specific user. Unlike a worklist (personal to one user) or work group (the team itself), a workbasket holds assignments awaiting processing by any qualified team member. This enables flexible workload distribution and ensures work doesn't sit unassigned if a particular user is unavailable.

Routers in Pega are specifically designed to direct assignments to their destinations - whether to a workbasket, a specific user, or based on complex criteria. This statement about routers telling assignments where to go is TRUE and describes their fundamental purpose. The other statements are actually true: routers aren't required on every assignment (optional), they execute activities to determine routing, and multiple routers with the same name can exist in a flow.

In Pega flows, activities create work objects using the Call Add method, which properly initializes the work object and adds it to the database. The Flow-New method and Utility shape serve different purposes, and activities can indeed start flows.

Pega has four standard assignment activity types: Worklist (personal queue for individual users), Workbasket (shared queue for groups), Agent (system-driven automatic assignment), and External (assignment outside Pega system).

Activity parameters in Pega are versatile configuration options that can control both the work object's status (the overall case state) and the individual assignment's status during processing.