Activities, libraries, and functions — Concepts and terms |
Activities are the primary processing rules in Process Commander. Each activity is a rule, saved as an instance of the Rule-Obj-Activity rule type. Process Commander includes hundreds of useful standard activities that your application can call. Developers create and debug additional custom activities.
As an activity executes, it can create or remove clipboard pages, create, and update properties on these pages, save them to the PegaRULES database, and interact with a human user by sending and receiving HTML documents and forms.
Activities process a sequence of steps. Each step can contain:
Activities can be called from many places:
When you save an Activity rule form, the system converts the activity into Java code. You can review the resulting Java source code, but not alter this code. You can also generate an English-language description (known as the verbalization) of the activities processing, in the form of a text only HTML page that can become a part of your application's documentation.
A library is a collection of Java functions that share a common name prefix, prerequisite Java packages, and other initial conditions. A library is an instance of the Rule-Utility-Library class. A function rule encapsulates a Java function and makes it accessible to Process Commander developers as a rule. A function is an instance of the Rule-Utility-Function class.
Three tools support developers as they work with activities: