Prev |
The action system allows an activity in a ProEd project to execute a simple, easily constructed Java class on the workflow server without having to create a full blown hook class. This facilitates the use of existing classes that are already able to perform some desired function, as well as accessing web services. The terms Actions, Action Classes and Connectors have all been used to refer to this system.
An action may be defined at either the process level or for a specific activity. Both the process dialog and activity dialog have an actions tab that displays the actions for the process or activity as well as provide buttons to add/edit/delete actions. At least one hook or action definition is required for activities that have an "Automatic" start mode. The actions tab is accessed in the following ways:
For process actions:
For activity actions:
The "Actions" tab of the process dialog is shown:
The action type and class name is displayed in the list box. The following operations are available using the buttons on the right hand side:
|
Prev | ||
Chapter 2 : Define hooks | Chapter 2 : Add a participant and a mapper
|