When rules and business conditions
Original learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain when rules and business conditions in the context of a loan application.
- Identify the configuration decisions and test an expected outcome.
- Recognize a common mistake before it affects users.
Understand the concept
A when rule expresses a reusable Boolean condition. Naming a condition by its business meaning makes its use clearer than duplicating comparisons in multiple steps. Reuse requires consistent input assumptions.
Business rules express policies independently of individual screens. A decision table evaluates structured combinations of conditions. A decision tree makes a sequence of branching decisions explicit. A when rule expresses a reusable true-or-false condition. Keep inputs, outputs and boundary behavior explicit so business stakeholders can review the policy.
Define an IsHighValueLoan condition. List every flow or view that uses it and check whether they agree on currency and amount units.
A configuration example
Define an approval policy using requested amount and risk category. A standard-risk request below a reviewed threshold can route to a loan officer; a larger request requires a specialist. Record the policy owner and test the exact threshold.
Application: Loan Origination Case type: Loan Request Learning focus: When rules and business conditions Given: a known applicant and a documented policy When: the configured step or rule executes Then: compare actual data and routing with the expected outcome
Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.
Try it yourself
Define an IsHighValueLoan condition. List every flow or view that uses it and check whether they agree on currency and amount units.
Write a small decision table for three loan scenarios. Include a value exactly at the threshold and an unknown risk category. Explain which outcome should apply when no normal condition matches.
For this lesson, focus your notes on when rules and business conditions. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
Why test values on both sides of an approval threshold?
Check your understanding
Boundary tests reveal incorrect comparison operators and gaps or overlaps in the decision conditions.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
