About Activity
rules
|
|
| New | Steps | Parameters | Pages & Classes |
| Security | History | More.... | Methods |
Activities automate processing. Activity rules contain a sequence of structured steps. Each step calls a method rule or contains a control instruction such as Call or Branch. Each activity has a type that characterizes its purpose and affects which other rules can call it.
The Steps tab contains the logic of the activity. These topics describe this tab:
When a requestor session runs an activity rule for the first time, the system converts information from the activity rule into Java, compiles the Java, and executes it. Later executions (of the same activity in the same RuleSet, version, and so on) reuse the compiled Java.
After you complete and save the Activity rule form, you can
test it interactively with the Run toolbar button (
). See How to unit test an
activity.
Don't use an
activity for calculations or property validations that you can
implement as constraints rules or Declare Expression rules. Use
of a declarative rule
(rather than an activity) eliminates the need to control how
and when an activity executes. The Pegasystems Implementation
Methodology approach promotes declarative processing rather
than activities when feasible.
Use the Application Explorer to access activity rules that apply to the work types in your application. Use the Rules by Type Explorer to list all activity rules available to you.
Activity rules are part of the Technical category. They are instances of the Rule-Obj-Activity class.
Home