MODULE 1 · Introduction to Pega

App Studio and Dev Studio

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

Learning objectives

Understand the concept

App Studio focuses on application design through business-oriented constructs such as case types, data objects and views. Dev Studio offers deeper access to rules and diagnostic configuration. The studios operate on the application rather than maintaining independent copies of its behavior.

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.

Find a case type in App Studio. Identify its associated configuration in the available development tools. Record which task is easier in each studio without changing generated rules unnecessarily.

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: App Studio and Dev Studio

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

Find a case type in App Studio. Identify its associated configuration in the available development tools. Record which task is easier in each studio without changing generated rules unnecessarily.

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 app studio and dev studio. 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