Robust, enterprise-grade Pega Platform™ applications depend on cooperation between two key groups of application developers. Domain experts — business analysts, citizen developers, and front-end developers — provide valuable insight into processes and user needs. Implementation experts — system architects, full-stack developers, database administrators, and security administrators — provide the expertise needed to address critical use cases that require complex configurations.
In App Studio, domain experts can access core application development features (case design, data management, and user experience) and apply their knowledge to improve development outcomes. To support advanced rule configuration in applications, Pega Platform provides implementation experts with a second development environment, Dev Studio. In Dev Studio, implementation experts access rule forms directly to address complex or less-common configuration requirements. In addition, Dev Studio provides features for configuring security permissions and access control, managing rules to promote reuse, and addressing the performance limitations of an application. By providing two development environments, Pega Platform supports each group of application developers with an environment tailored to their skill level and optimized for the tasks they perform.
In the following image, click the + icons to examine some of the options available for service-level agreements (SLAs) in Dev Studio, beyond the basic goal and deadline configuration available in App Studio.
Business analysts and citizen developers understand business needs. System architects understand the capabilities of Pega Platform. To help these two groups work together, Pega Platform enables a co-development approach that embraces the strengths of each group. This co-development approach empowers business analysts and citizen developers as core members of a development team, leveraging their knowledge to design better business processes. By working together, domain experts and implementation experts can create better solutions more quickly.
In the following example, click the + to examine how a business analyst and system architect can work together to design a positive user experience when providing a shipping address for an order.
Promote reuse throughout the organization
In App Studio, developers configure rules such as processes, views, correspondence, and service levels for a single case type. In Dev Studio, developers access all the layers of an application and can extend the rule scope from a single case type to an application, division, or even the entire organization to create a library of standardized, reusable rules. Citizen developers and business analysts can use these tested and proven rules to reduce development time for later releases.
In the following image, click the + icons to examine how a system architect can extend the scope of an approval process to improve application quality and reduce time-to-market by allowing a citizen developer to reuse the process in other applications.
Switch between studios as needed
Application developers can switch between App Studio and Dev Studio as needed to configure rule behavior. The upper-left corner of each studio contains a menu listing all the studios available to the user. To switch to another studio, select the studio name from the menu.
In addition, from App Studio, you can open specific rules in Dev Studio. For example, after you configure a goal and deadline in App Studio, you can open the underlying SLA record in Dev Studio.
Naming differences between studios
In Dev Studio, developers can access the rules created by citizen developers, business analysts, and front-end developers in App Studio, though these rules often carry different names. The following table illustrates some common App Studio elements and the different names used for those elements in Dev Studio.
|App Studio||Dev Studio|
|Goal and deadline||Service Level Agreement (SLA)|
|Data Object||Data type|
Note: For example, in App Studio, you add fields to data models and views. The system creates a corresponding property that you can modify in Dev Studio. Similarly, a data type in Dev Studio correlates to a data object in App Studio. Data objects represent the business perspective and are exposed in the case life cycle; data types are the technical implementation. As a result, data types are the objects that developers manipulate in Dev Studio.
Check your knowledge with the following interaction