Direct Capture of Objectives (DCO)
Guardrails help developers to track compliance with Pega best practices.
Guardrails help developers build applications that are easier to maintain and have fewer defects.
Guardrails help managers create schedules for efficiently allocating developer resources.
Guardrails help project managers ensure that applications are completed on time.
Defines what a step should do
Instructs an architect how to build the step
Describes the business value of the step
Describes to an end user what should be done in a step
Subset of data used to resolve case
Transfer for authority
Single actor performing a single action
Significant change in the status of a case
Case status automatically updates.
At the end of the step.
At the beginning of the step.
Case status cannot update automatically.
Have manual access
Exceptions to the normal course of events
A separate, but related business transaction
Be sequenced into primary stages
Goal and deadline intervals can only repeat one time.
Goal and deadline intervals begin at the start of the assignment.
Goal and deadline intervals do not repeat.
Goal and deadline intervals have limited escalation options.
Allowed for a user to advance to the next stage
In which the case or step should be completed
Allowed before an assignment is considered overdue
In which the case or step must be completed
Assign cases to the appropriate case worker
Help ensure timely completion of assignments
Track assignment status over time
Generate service level reports
Verifying prospective employees work references
Declining offer to prospective employee
Offering job to prospective employee
Running a criminal background check
A process that is not part of the primary flow in the case life cycle
A process that executes in the context of another process
A process that executes in the context of the current case
A process that executes over the same time period as other processes
Application users to focus on more nuanced decisions that require business expertise
Architects to improve the performance of the application
Application users to mark a specific location for business exceptions that may arise in the process flow
Architects to spend less time building the application
Subprocesses that run in parallel with the context of the current case
Paths in the case life cycle that are followed based on the context of a parallel case
Subprocesses that run in the context of the current case
Paths in the case life cycle that are chosen by a user at run-time or are based on runtime values
By assigning work to the currently available party.
By assigning work to the party in the appropriate time zone.
By assigning work to the most senior party in a work group.
By assigning work to the most appropriate parties.
The list of approvers
The approval process flow
The approval levels
The salary grades of the approvers
The locations of the approvers
To the user's work group
To the user's manager
To the user
To the user's work queue
Route requests to a work group whose members have the skill rating parameters.
Route requests to a reporting manager who assigns the request to a user to ensure fast processing.
Route directly to users who are members of a work group that uses skill rating parameters.
Route requests to a decision table that routes the request to a work group in a location where there are users who have appraisal skills.
It is not possible to support this requirement. The router must define a specific work queue.
Route the assignment to the correct work queue based on business logic.
Route the assignment based on appraiser skills.
Route the assignment based on an appraiser role.
By applying directed inheritance.
By adding the ruleset that contains the property to the application.
By applying pattern inheritance.
By naming Pega RULES as the built-on application.
The application ignores the checked-out version and uses the previous version in the application ruleset.
The application cannot run because the rule is unavailable.
The application runs the checked-out version of the rule, because that is the most up-to-date version of the rule.
The application returns an error and stops processing the case, because the rule is unavailable for use.
You cannot proceed in an expense report until a manager approves the request.
You need to send an email after a user completes a form.
You need to pause a case until a user uploads a signed document.
You cannot complete a purchase case on a website unless you complete a new account subcase.
Make mortgage a parent case type. Make loan request and appraisal child case types.
Make appraisal a parent case type and loan request a child case type.
Make both loan request and appraisal peer case types.
Make loan request a parent case type and appraisal a child case type.
PO-11 has to be resolved before either Pay-37 and Pac-56 is resolved.
Both Pay-37 and Pac-56 have to be resolved before PO-11 can be resolved.
Pac-56 has to be resolved before Pay-37 is resolved.
PO-11 can be resolved when either Pay-37 or Pac-56 is resolved.