Defining application behavior
When you define how your application behaves at run time, you provide an experience that optimally meets the needs of end users and customers. You can also define how design-time actions correlate to run-time behavior, and how actions that users perform affect processing in your application.For example, you can define which actions users need to perform toward the resolution of your business process, and which actions an application performs automatically.
In App Studio, a low-code environment to create and configure applications, you can define application behavior in the following areas of your application:
Build reusable templates for your business processes in a visual and user-friendly way by placing user actions and application automations in a sequential order. You can enrich your case processing by implementing various functionalities, such as notifications about case events, service-level agreements, or optional actions that take part in processing only under specified circumstances.
For more information about case configuration and processing, see Case management.
Data objects and integrations
Define objects to store data that your application uses while processing work, and then organize those objects into a logical model. By connecting the objects, you can conveniently reuse data across your application. For example, you can create an object that stores contact details of a customer, and then reuse the object in various places of your application.
For more information about managing data objects, see Exploring the visual data model and Creating a data object.
Create channels through which run-time users can interact with your application. You can select among numerous options to meet your unique needs, such as web portals, mobile channels, and digital messaging. by implementing different means of communication and interaction, you can expand your application to wider audiences.
For more information about creating and configuring conversational channels, such as Facebook Messenger, WhatsApp Messenger, or SMS/MMS (Twilio), see Conversational channels.
For more information about adjusting your application to mobile devices, see Pega Sales Automation mobile application.
Invite collaborators to your application for more robust project development, manage personas to organize types of run-time users, and define types of access for different user types to ensure that both developers and end users interact only with the parts of your application that are relevant to their role. You can also implement authorization mechanisms to increase security.
For more information about managing personas, see Adding personas to organize users.
For more information about low-code security solutions, see Security in App Studio.
Provide an inclusive, intuitive, and clear user interface so that end users can create and process work in your application. For low-code and user-friendly application development experience, Pega Platform automatically builds your user interface for you, for example, when you drop different UI elements.
For more information about user interface, see Theme Cosmos and Cosmos React.
The following figure summarizes main elements that you need to consider when you define your application behavior:
- Differences in naming between App Studio and Dev Studio
When you create resources in App Studio, Pega Platform creates one or more rules and potentially classes. Dev Studio provides visibility into all the created records while App Studio usually exposes only objects with less complex configurations. In some cases, App Studio and Dev Studio refer to the same resource, but use different terms. By understanding the differences, you can better understand how Dev Studio stores the elements of your application that you create in App Studio.
Previous topic Integrating Agile Workbench with Jira in Pega Platform 7.3.x to 7.4.x Next topic Differences in naming between App Studio and Dev Studio