.
A reviewed reservation
An airline ticket
A reservation
A confirmation email
Stakeholders
Case participants
Subject Matter Experts (SMEs)
Business architects
Approval process
Guardrail compliance
Iterative delivery
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.
Add the date of birth field to all the user views in the case type
Add a date of birth data field to the case type
Add the date of birth field to the case worker's view of the case type
Add a date of birth field to the appropriate stage
Single actor performing a single action
Transfer of authority
Significant change in the status of a case
Subset of data used to resolve the case
Only be accessed manually
A separate, but related business transaction
Exceptions to the normal course of events
Be sequenced into the primary stages
Add a process in a stage.
Add a local action to the case type.
Add an optional process to any stage in the case type.
Add a step in a process.
Allow a user to transfer a case to another employee at any stage of the case.
Reassign any task that remains open after three days to another user.
An application randomly sends a survey to customers once their case is resolved.
Requiring a separate approval process whenever an order exceeds USD 10,000.
Defines what the step should do.
Describes the business value of the step.
Instructs an architect how to build the step.
Describes to an end user what should be done in the step.
At the beginning of the step
Only if the user manually updates the case status
At the end of the step
The status of a case cannot be automatically updated
Approve/Reject
Create Case
Change stage
Collect information
The Continue Shopping buttons are in the same location in both views.
The shopping cart items, price and quantity are in the same location in both views.
The yellow buttons have different labels but they are in the same location in both views.
The quantity fields show the same amount in both views.
The customer name has a one-to-one relationship to the phone number and discount code elements.
The purchase request has a one-to-one relationship with the customer and the line items.
The customer and line items are data objects.
The unique identifier, date, and total are each single value data elements.
You can configure the user view for a step after you add that step to the case life cycle.
You can configure the user view for a step after you create the entire case life cycle.
You can configure the user view for a step before you start creating the case life cycle.
You can configure the user view for a step any time after you configure the pick list data types.
Set the minimum and maximum values to 9 in a text field.
Use an edit validate rule that validates the routing number pattern.
Use a decimal property type and make the field required.
In an edit validate rule, configure a function to test for a routing number pattern.
Associate an edit validate rule with the flow action that references the form
Use two validate rules, one for each condition.
Use a single validate rule to verify both of these conditions.
Use an edit validate rule that validates both conditions.
Use the required option
Use the read-only option
Define the field type as an integer
Add the word "Required" to the field label
Define the field type as a date
You cannot proceed in an expense report until a manager approves the request.
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 child case
You need to send an email after a user completes a form.
Make loan request a parent case type, and appraisal a child case type.
Make both loan request and appraisal peer case types.
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.
Both Pay-37 and Pac-56 have to be resolved before PO-11 can be resolved
PO-11 can be resolved when either Pay-37 or Pac-56 is resolved.
Pac-56 has to be resolved before Pay-37 is resolved.
PO-11 has to be resolved before either Pay-37 and Pac-56 is resolved.
By adding the ruleset that contains the property to the application
By applying directed inheritance.
By applying pattern inheritance.
By naming PegaRULES as the built-on application.
The status of the rule.
The application that uses the rule.
The description of the rule.
The class of the rule.
The type of the rule.
Check the inheritance path to determine if an appropriate data element is already available
Create a data element for each case type, because they may use different status values.
Create one data element in the class group layer for both applications to use.
Create one data element in the org layer for both applications to use.
The application ignores the checked-out version and uses the previous version in the application ruleset.
The application returns an error and stops processing the case, because the rule is unavailable for use.
The application runs the checked-out version of the rule, because that is the most up-to-date version of the rule.
The application cannot run because the rule is unavailable.
Page
Single value
Page list
Value list
Field group (list)
Radio button
Text (paragraph)
Picklist
Page
Single value
Value group
Text
Information about the Pega server.
Data cached from an outside system.
Information about the current operator
Information about a case.
Test whether a declarative expression properly calculates a target value.
Test case behavior by setting property values for an open case.
Review the current values of case data.
Test a rule to determine whether the rule executes correctly.
Apply the pySetFieldDefault data transform to set the .Location property when the user enters the .Destination property value
Set .Destination as the target property equal to .Location as the source property.
Set .Location as the target property equal to .Destination as the source property.
Invoke a when condition to update the .Location property value when the user enters a .Destination property value.
In the Claims data transform, for each subcase type, configure an Update Page action and set the work urgency value.
In each subcase type data transform, set the work urgency to the required value.
Select the Call superclass data transform option in each of the subcase type data transforms.
Select the Call superclass data transform option in the Claims data transform and clear the option in the Personal Injury and Emergency Care data transforms.
Set .Dependents(1).pyLabel to an empty string and a parameter named "Not Applicable"
Set .Dependents(1).pyLabel and a comment action using the value "Not Applicable"
Set .Dependents(1).Relationship to "Not Applicable"
Set "Not Applicable" to equal .Dependents(1).Relationship
Create properties after the case has been created
Execute a flow action
Set default values when creating a case
Copy data from one page to another
Total cost for the hotel room
Number of days at the hotel
Price of each option
Total cost of options
When updating a property that is calculated, you do not need to identify every calculation that updates any of the source values and manually re-calculate them.
A declare expression calculates a specific value that is used on multiple forms.
The system monitors input properties and determines when to update the target property value.
A declare expression updates the total value on all the forms when any form containing the field is submitted.
Apply the declare expression in the approval flow action.
Calculate the total interest rate value by adding all the declare expression target property values
Specify forward chaining in the declare expression that calculates the total interest rate value.
Specify backward chaining in the total interest rate declare expression.
When a value in the child case or spin-off case changes
When a case is created
Whenever a parent's value changes
When a parent's value changes and a data transform is used to configure the data propagation
A decision tree
A data transform
The Update a Case smart shape
A data page
A data transform
The Update a Case smart shape
Data propagation
A calculation
A data page
The property mapper
A data transform
A decision tree
Request
Application
Node
Thread
The data page reloads automatically one hour after it was last accessed.
The data page reloads automatically one hour after it was created.
The data page reloads on the next access one hour after it was last accessed
The data page reloads on the next access one hour after it was created.
Wait until the data page reloads on the next access one hour after it was created.
Update your application to remove any reference to the data page.
Update the data page to change the data source information.
Configure a new data page for the new data source, then update your application to use the new data page.
Insurance policy data
Customer details
Delivery options
Case data
Drop-Down
Text field
Label
Button
Use case data
Use local storage
Use a data page
Use a static list
To access an external database
To add a new employee
To provide a limited set of input values for a field
To add case data
.pxUrgencyWork
.pxUrgencyAssign
.pxUrgencyAssignSLA
.pyUrgencyAssignAdjust
50
100
60
80
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.