Flow Actions

1. What are the types of Flow Actions?

A flow action rule controls how users interact with work object forms to complete assignments.
Each flow action is defined by an instance of the Rule-Obj-FlowAction rule type.
Flow actions are of two types:
 Connector flow actions appear as lines on Visio presentation in the Diagram tab of a flow rule. A line exits
from an assignment shape and ends at the next task in the flow. At runtime, users choose a connector flow
action, complete the assignment, and advances the work object along the connector to the next task.
 A local flow action, when selected at runtime, causes the assignment to remain open and on the current
user's work list. Local flow actions are recorded in the Assignment Properties panel and are not visible on
the Visio flow diagram.

2. What is the Difference between Connector Flow Action and Local Flow Action?
A local flow action permits users at runtime to update, but not complete, an assignment. Local flow actions
always are optional. Users may perform none, one, or multiple local flow actions, or repeat a local flow action
multiple times.
At runtime, users choose a connector flow action, complete the assignment, and advances the work object
along the connector to the next task.

3. Explain about Pre Activity?

At runtime, the system runs this activity before it does other processing for this flow action. This
activity is not visible on the Visio flow diagram. This activity executes only once, the first time a
user selects this flow action for this assignment.

4. Explain about Post Activity?

Activity to run after other successful processing of this flow action.
For screen flow rules By default, when this flow action appears as a step in a screen flow rule, and
the user at runtime clicks away to a different step in the screen flow rule, this activity rule does not
run. To cause this activity to execute when the user clicks away to a different step, select the Post
Action on Click Away? check box on the Assignment shape properties panel.

5. Explain about Local Flow Action?

A local flow action permits users at runtime to update, but not complete, an assignment. Like
connector flow actions, local flow actions are referenced inside an assignment task in a flow.
At runtime, users can select local flow actions to update assignment or work object properties,
change the assignee, and so on but do not complete the assignment. If a service level rule is
associated with the assignment, the service level continues to run.
Local flow actions always are optional. Users may perform none, one, or multiple local flow actions,
or repeat a local flow action multiple times.
On the Action tab of the Flow Action form, we can mark a flow action rule as local, or connector, or
both.

6. How do we make one Local Action available in all Assignments?

On the Design tab of the Flow form, we can list local flow actions that are to be available at every
assignment in the flow.