Dev Studio
Robust enterprise-level Pega platform™ applications rely on the cooperation between two key application developer groups: Domain experts-business analysts, citizen developers, and front-end developers—provide value to processes and user needs Insights. Implementation experts-system architects, full-stack developers, database administrators and security administrators-provide the expertise needed to solve critical use cases that require complex configurations.
In App Studio, domain experts can access core application development functions (case design, data management, and user experience) and use their knowledge to improve development results. In order to support advanced rule configuration in applications, the Pega platform provides Dev Studio, a second development environment for implementation experts. In Dev Studio, implementation experts directly access the rule form to solve complex or less common configuration requirements. In addition, Dev Studio also provides features to configure security permissions and access control, and manage rules to promote reuse.
Initialization behavior
In Dev Studio, if the task is completed before it is sent to the work list or work queue, then customize the initial emergency of the SLA and delay the start of the target and deadline timer.
Variable interval length
In Dev Studio, the interval time is applied programmatically (rather than explicitly) to adjust the SLA behavior according to the specific situation.
Account for business days
In Dev Studio, when calculating the SLA interval, exclude non-working days from holidays and weekends
Additional escalation actions
In Dev Studio, configure upgrade options other than notifications, such as reassigning tasks or resolving cases.
Co-develop solutions
Business analysts and ordinary developers understand business needs. System architects understand the capabilities of the Pega platform. To help these two groups work together, the Pega platform uses a joint development approach that includes the strengths of each group. This joint development method enables business analysts and ordinary developers to become core members of the development team, using their knowledge to design better business processes. Through cooperation, business experts and system experts can create better solutions faster.
Business analyst
Business analysts design views in App Studio to capture the billing and shipping address of the order. The user must manually enter the shipping address, even if the address matches the billing address.
System architect
The system architect added the ability to automatically copy the billing address to the shipping address when prompted by the user. In addition, system architects create test cases to ensure that features work as expected and identify regression errors in future versions of the application.
User
During checkout, the user clicks the checkbox on the completed view to send the order to their billing address
Promote reuse throughout the organization
In App Studio, developers configure rules for processes, views, communications, and service levels for a single case type. In Dev Studio, developers can access all layers of the application, and can extend the scope of rules from a single case type to applications, departments, and even the entire organization to create a standardized and reusable rule base. Public developers and business analysts can use these tested and proven rules to reduce development time for subsequent versions.
1Using App Studio, business analysts design the approval process for insurance claims as part of the property insurance policy management application.
2 Because the approval process is consistent in many types of consumer insurance products, system architects use Dev Studio to extend the scope of the approval process to the entire consumer department.
3 By using App Studio, business analysts can reuse the approval process in travel and auto insurance policy management applications, thereby shortening time to market and improving application quality.
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 that lists all the studios that the user can use. To switch to another studio, select the studio name from the menu.
In addition, in App Studio, you can open specific rules in Dev Studio. For example, after configuring goals and deadlines in App Studio, you can open the underlying SLA records in Dev Studio.
Naming differences between studios
In Dev Studio, developers can access the rules created in App Studio by ordinary developers, business analysts, and front-end developers, although these rules usually have different names. The following table shows some common App Studio elements and the different names these elements use in Dev Studio.
