Reuse, branches and Agile Workbench
Updated 19/11/2026
Reusable capabilities reduce duplication when applications share business needs. Branches isolate development changes before integration. Agile Workbench records work items such as user stories, bugs and feedback so configuration changes can be traced to a need.
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.
Create an acceptance criterion for validating applicant income. Describe an isolated development change and the review and merge checks needed before sharing it.
Return to curriculum