Skip to main content


Updated on October 2, 2020

It is day 1 of your first Sprint. You have completed Sprint Planning. The 3 pillars of Microjourneys™ (in the form of case types), personas (and the channels they use) and data have been captured in your application already. Your user stories are ready. You have a great starting point. Now it’s time to start configuring using Pega’s best practices.

If you are a citizen developer, configuring a Pega application is a much more guided process using App Studio entirely. What we describe here is aimed at how a certified Pega System Architect would approach the configuration, using both App Studio and Dev Studio. We’ve also made some assumptions; you have created your organization structure and you’ve created your application already using the new application wizard. 

We recommend using App Studio as much as possible, especially for the first MLP release where we want you to deliver speed to value using out-of-the-box features and minimum configuration. Dev Studio provides more flexibility and advanced configuration features; you will use Dev Studio to navigate rule types (e.g. in the record section), create complex user interfaces and configure integrations that are not REST (use App Studio for REST) and to create connections to 3rd party systems.

In App Studio, you will start with the case designer. During Directly Capture Objectives (DCO) workshop sessions, you can create new case types or enhance existing case types by adding new stages e.g. for data collection, approval/rejection. You can add steps within each stage, then overlay the personas and channels, and identify what data you need. DCO is a powerful way of working that will enable the Product Owner to get an early view of the workflow before it is fully built. Using the model designed during DCO, the build team can add routing rules, Service Level Agreements (SLAs) etc and formulate the data model for the case type, adding views for fields you want to display within the workflow. The Pega Platform will automatically add rules which can be used to access and save data.

Now it’s time to start editing the User Interface (UI). Run the application and create a case to get started. You can create a simple UI or a complex UI; you can use various available layouts to select the UI look and feel.

Use the Integration Designer to configure your REST services and connectors within App Studio.

You can view the application on the target device type. For example, you can build a fully native mobile application from within App Studio. Or you can build an omni-channel UI.

Finally, it’s time to setup the security structure. You can setup authorization to the application by configuring native Single Sign-on (SSO) and setup roles for different access groups.

What happens next? Once a user story has been configured, unit tested, and deployed to a test environment, business representatives in your team will test your hard work. They may raise bugs or ask for clarification. Once a user story has met the Definition of Done it will be showcased to the wider team during the Sprint Review at the end of the sprint and will be ready for deployment or hardening. Configuration is an iterative process. You will move onto the next sprint, taking any learnings from this sprint into the next one.

The related content links below provide methods and tools to help you.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us