MODULE 1 · Introduction to Pega

Applications, rulesets and class inheritance

Original learning guide · Pega ’25 path · Content v1.0.0

Learning objectives

Understand the concept

An application includes rulesets that organize rule definitions and versions. Classes organize related behavior and data. Inheritance provides reuse, while rule resolution uses context to determine applicable behavior. A similarly named rule in another context is not necessarily the rule that will execute.

Pega models business work as cases. A case combines the information, decisions, assignments and milestones needed to reach an outcome. App Studio provides a business-oriented authoring experience; Dev Studio exposes deeper rule configuration. Rules belong to classes and rulesets, so inheritance and reuse influence which behavior executes.

Write a proposed class and ruleset organization for reusable applicant data and loan-specific behavior. Explain why a shared validation rule belongs in a reusable layer.

IntakeAssessmentDecisionResolution

A configuration example

For a loan request, define a Loan application and a Loan Request case type. Keep shared applicant information in a reusable data object. Capture the desired business outcome before configuring individual screens.

Application: Loan Origination
Case type: Loan Request
Learning focus: Applications, rulesets and class inheritance

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

Write a proposed class and ruleset organization for reusable applicant data and loan-specific behavior. Explain why a shared validation rule belongs in a reusable layer.

Write a short loan application story. Identify the customer, loan officer and credit reviewer. List the work each persona performs. Explain which rules should be shared with a future credit-card application.

For this lesson, focus your notes on applications, rulesets and class inheritance. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

Creating a separate rule for every screen can duplicate policy. First identify whether a reusable data model or inherited behavior already meets the need.

Knowledge check

Why separate a reusable Applicant data object from the Loan Request case?

Check your understanding

Applicant data can be reused across case types while the Loan Request case owns the lifecycle and loan-specific work.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives