App Studio provides core features for application development, such as Case design, data management, and user experience. App Studio is designed for low-code users. Typical users include application developers, front-end developers, data engineers, business analysts, and system architects. Use App Studio to get your applications operating quickly.
App Studio workspace
The App Studio workspace helps you visualize the key factors of the desired business process. As you outline the process, you build relationships between stages of the process, participating personas, communication channels, and data required for process resolution. The visual model built in App Studio helps you plan and manage your development team's workload.
The following image shows an App Studio workspace:
As a best practice, technical team members such as system architects, build applications in App Studio to reduce potential errors. Only switch to Dev Studio when configuring advanced features that are unavailable in App Studio, such as integration services or database class mappings.
Check your knowledge with the following interaction:
Support for agile development
App Studio supports agile development best practices to plan and implement the features for your application. Users can quickly build off a business case by developing a working outline of the process to be performed in a Pega Platform™ application.
App Studio also supports real-time UI design as you process the work. For example, a team that is testing the end-user interface of an online shopping application can add new fields and make changes to user controls such as drop-down lists. This ability is helpful for reviews with stakeholders, who can see their suggested feedback implemented in real time.
Tip: Instead of naming items in App Studio as app1, process2, field3, or step5, as a best practice, use business-friendly names, such as Feedback app, Sales process or Send email. When building your application in App Studio, Rules are auto-generated in the background with these same names. It is easier to find a Rule by name when business-friendly names are used.
The Application profile captures and presents user stories, bugs, and feedback items to support agile development best practices. This collection supports collaboration across technical and business members of the team. For example, you can create a feature to support requests for new training modules in your application. Your team can then map development tasks, such as defining a data table of available courses, to this feature by creating stories and other work items. Features support traceability from objectives to development tasks to implementation, keeping all collaborators informed.
Modular application design
Pega Platform applications comprise instructions, called Rules, that govern application behavior, just as the rules of chess govern the behavior of various pieces. The Rules that make up an application are organized into Layers for reuse between applications. For example, your company may have several applications that share a common branding. Once you create the look and feel of your application at the Organization or Framework Layer, you can reuse it for each new application that you build.
Layers and the Rules within them are reusable. Each Layer represents a unique application and is built on one or more Layers, except for the Pega Platform Layer, which includes Rules for the Pega Platform itself (PegaRULES). This modular approach to application design reduces development time and improves application quality and maintenance, even for complex applications. For example, each Layer can be maintained by a dedicated development team and updated on its own schedule based on business needs.
The App Studio overview displays an Application Layers Widget, which provides a visual representation of the Rules that make up your application.
Hovering your pointer over a layer title or graphic highlights the Rules that the layer contributes to the application, as seen in the following figure:
Note: The Application Layers Widget presents a high-level summary of the contents of your Application Layers, not a complete inventory of your application.
The Application Layers Widget also identifies the Pega Platform application type. Pega Platform offers two out-of-the-box (OOTB) application architectures:
- Constellation architecture - Constellation architecture uses the Constellation Ruleset to build applications on the new View-based user-interface (UI) architecture. The example and challenge applications in the Low-Code App Builder mission are built on the Constellation architecture.
- Traditional UI architecture - Traditional UI architecture uses the Theme Cosmos Ruleset to build applications on the traditional, section-based UI architecture.
In the center of the following image, slide the vertical line to compare the Application Layers Widget for the different application architectures:
Tip: You can also determine the type of application by navigating to Dev Studio, opening the Application Definition, and reviewing the Build on applications section. For more information on the Application Definition, see Exploring the Application Definition.
Check your knowledge with the following interaction: