Glossary:Service Activity

Service Activity, service activity

An activity that is referenced by a service rule. At run time, the activity operates as a BATCH requestor type to perform background processing, and returns the results to the client or calling external system.

An activity that is referenced by a service rule. At run time, the activity operates as a BATCH requestor type to perform background processing, and returns the results to the client or calling external system.

An activity that is referenced by a service rule. At run time, the activity operates as a BATCH requestor type to perform background processing, and returns the results to the client or calling external system.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.

Data instances that define the types of requestors that can access Pega Platform, such as a browser session, an external application, or an internal background process.