Studios

A Pega Platform™ provides four role-based authoring spaces, referred to as studios. Each studio provides specific tools and features for application development. When using the appropriate studio, team members are enabled to complete tasks by using tools that align with their expertise.

Pega Platform studios:

• App Studio: A low-code authoring space that provides features for application development. Users can design Cases, manage data, and design the user interface (UI). Citizen developers and technical staff in roles such as application developer, front-end developer, data engineers, business analyst, and System Architect use App Studio. To learn more about App Studio, see App Studio overview.
• Dev Studio: A low-code authoring space that provides advanced features for application development. Technical users of Dev Studio include full-stack developers, system architects, database and security administrators. To learn more about Dev Studio, see Dev Studio overview.
• Prediction Studio: An analytics space used by data scientists and business decision-makers. Prediction Studio provides features to build machine-learning models for adaptive, predictive, and text analytics. To learn more about Prediction Studio, see Prediction Studio overview.
  Note: To access this studio, users require pxPredictionStudio as one of the Portals associated with their access group.
• Admin Studio: A software administration space managed by IT staff for system administration. This studio provides technical team members with runtime information and configuration options for monitoring and debugging system resources. To learn more about Admin Studio, see Admin Studio overview.

The following image displays the Pega Platform studios:

Each studio speeds application development and enhances productivity by providing users role-based functionality.  

Depending on your screen size, icons replace text-based menu options, as displayed in the following image:

In Pega Platform, you can improve productivity by using studios. For example, front-end developers can design a web portal solely in App Studio, while system administrators switch between App Studio and Admin Studio as they configure advanced deployment functionality and monitor run-time results.

Users can have access to one or more studios. When users log in, the system opens the user's default studio. They can then switch to any other studio they have security access to use.

Studio navigation

Each studio consists of three areas:

• A header
• A navigation pane
• An authoring space

Match the numbers to the following image to learn about each area:

1. Header: The header contains various menus or tools, depending on which studio is active. For example, in the upper right of App Studio, you can click the appropriate icon to access Pega Agile Workbench, a tool that allows you to capture real-time feedback about your application and tracks feature development. All studios have a drop-down arrow in the upper-left corner, which lets you switch between studios to which you have access.
2. Navigation pane: The navigation pane allows you to access parts of an application through explorers. Examples include the Case Type Explorer and the Data Explorer.
3. Authoring space: The authoring space is used to configure the application behavior. In App Studio, you can use the application overview section to review high-level case design information, data management information, user experience information, and so on. Use this page to find and monitor key components in your application to help you decide how you want to allocate your development resources. For example, you can compare the lifecycle of business processes across your case templates to identify inconsistencies and opportunities for reuse. Or review the ways users interact with your application to find new ways to engage customers. 

In the navigation pane, you can find multiple tools for developing and navigating through your application:

• Overview provides basic information about your application, such as Case Types and Channels.

• Case Types are visual representations of reusable business processes or work accomplished by your application. For example, employee onboarding or flight booking.

• Data is the information required to process and resolve business cases. For example, employee details needed in a hiring process. 

• Channels provide ways for users to interact with your application. For example, the interactions can be via a Web Portal or a Mobile Portal.

• Library provides a visual representation of reusable assets (Case Types, data, and logic) in the Reuse Library. For example, you can use the Reuse Library to filter data objects by the MyTown application.
  Note: For more information about the Reuse Library, see Managing reusable assets in the Reuse Library.

• Users are participants interacting with your application to perform various tasks. For example, a Manager or a Customer service representative. 

Check your knowledge with the following interaction:

This Topic is available in the following Modules:

• Low-code defined v8
• Low-code defined v9