Datapolis Process System

Search:

Contents
:
IndexBookmarkPrint
Home > User Guide > Creating Workflows > Workflow Designer > Actions

Actions

 

Actions represent transitions between states. On the workspace actions are shown as lines connecting  two states.

Actions are launched by users (Launch Action) , by self-timers (Self-Timers), or even by other workflows.

 

Note: Because action represents transition between states, its direction is important. The direction is marked by a small arrow in a circle:

In other words, it is important that, when creating actions, you begin in a state from which the action should start, and end in a state to which the action should lead.

Note: The action coming from the starting point (the “Start” state) is a special action which is always executed when workflow starts. Its default name is “Initial action” and has disabled permission, execution conditions and launch form management (these functionalities are described later in this document).

 

Actions are very important objects in Datapolis Workflow Architecture. Actions (beside states) create skeleton of entire process logic. Actions enable communication between users (workflow participants) and process and finally there may be automatic activities (like sending an email, editing SharePoint list etc...) defined and executed during the action launch.

 

Example: Simple Approval process:

When the process is in the "Waiting for Approval" state user may launch "Approve" or "Reject" action. When the user choose "Reject" action we want him to give the reason of rejection, then we want to send the email to the applicant with the result of an application ("Application was rejected") and with the reason of rejection. To obtain such a functionality we need to define "Launch Form" for "Reject" action and email activity for this action.

 

Note: It is important to remember that:

  1. Action is a transition from one state to another (usually launched by the user)
  2. Action may have its own Form to interact with the user
  3. Action may have defined activities which will be automatically executed after action is launched.

To edit action properties open the properties window by double-clicking the action line or by clicking the “Edit action” icon, which appears when you point the mouse cursor over the action:

 

More about action properties you may find here.