Studio interoperability and the Reuse Library
Pega Platform™ has been model driven from inception and continues to expose more advanced app development features in a simplified way. App Studio and Dev Studio offer a curated low-code development experience for all your needs so that you can use the right workspace for the right job in the right way.
Studio interoperability
App Studio provides a more simplified, collaborative, and inclusive authoring experience which allows a wide range of low-code practitioners to understand, interpret, and author processes and applications. It hides complexity and increases the Case Type literacy of many stakeholders, which helps to better express requirements, feedback, and needs.
Dev Studio provides more robust low-code development features for more experienced Pega architects to configure integrations, complex decisions, security, and advanced features. Think of Dev Studio as a curated authoring environment to create reusable modules and to mark Rules as relevant Records to make them accessible for assembly in the App Studio Case Designer.
Using Dev Studio in conjunction with App Studio can maximize and extend the power of Pega Platform for all low-code project team members so that everyone can work more effectively and collaboratively in App Studio.
Match the numbers to the following image to learn more about the interoperability of App Studio and Dev Studio:
- In Dev Studio, you can build:
- Advanced applications and reusable components by using advanced Pega Platform features, traditional UI authoring, and automated unit testing.
- Reusable modules and mark Rules as relevant records for assembly in App Studio.
- In App Studio, you can configure:
- An application without touching a line of code by using AI-assisted development, The prescriptive UI, relevant records and Configuration Sets.
Relevant records
- Properties, also known as fields
- Paragraphs
- Correspondences
- Service-level Agreements
- Strategies
- Processes, also known as Flows
- User actions, also known as Flow Actions
- Data Transforms
- Decision Tables
- Notifications
- Pulse Feed Rules
- Validate Rules
- When Rules
When you create Fields, Views, Processes, and user actions in App Studio, Pega Platform™ automatically marks them as relevant records.
The following topic contains information that is important for your understanding of the function of relevant records in studio interoperability and modular enterprise reuse and for passing the certification exam: Relevant records and Studio interoperability.
Reuse Library
The Reuse Library in App Studio is a centralized repository that contains all reusable assets in the enterprise. It helps developers of all skill levels discover, understand, and use reusable components.
Combining a well-structured Reuse Library with strong governance enables organizations to accelerate development, improve application quality, and boost business agility. A successful reuse program depends on a clear governance framework that ensures leadership, coordination, and prioritization of reusable assets.
To maximize value, establish processes and tools for:
- Lifecycle management: Define roles and processes to manage asset lifecycles. Choose between centralized or federated models.
- Reuse catalog: Organize assets with tagging and search capabilities in a central, governed catalog accessible to distributed teams.
- Deployment and maintenance: Track where reusable Pega assets are deployed across the organization.
- Value measurements: Use dashboards and reports to monitor asset usage and return on investment (ROI) by asset and consuming application.
- Education and advocacy: Incorporate ongoing training for developers to build reusable components, recognize contributions, and communicate program benefits to foster a culture of reuse.
The following topic contains information that is important for your understanding of the Reuse Library and for passing the certification exam: Reusable assets and the Reuse Library.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?