Action Classifications and Behaviours

Action Classifications

Actions can be grouped into certain classifications as follows:

  • I/O: This means that this action carries out work that is related to I/O operations and relies on I/O resource types.
  • Process: This means that this action carries out work that is related to processing and computing operations. It also relies on processing resource types.
  • Capacity: This means that this action carries out work that is related to storage and retrieval of files, and relies on capacity resource types.
  • Workflow: This means that the action carries out work that is related to the workflow context, and relies on a workflow instance to operate.

Action Behaviours

An action may or may not support the following behaviours depending upon the way it is executed or the way they handle a single asset or asset groups:

  • Workflow Supported: If an action supports workflows then it can be accessed from within the Workflow Designer and it can be run within a workflow instance.
  • Manual Launch Supported: If an action supports this behaviour then it can be run as a job from the asset toolbar.
  • Group Execution Supported: If this is supported it means that this action can run against an asset group as well as a standalone asset. In this context a single job is created.
  • Group Member Execution Supported: If this is supported it means this action can be run against the members of an asset group. In this context a group job is created.
  • Redo Supported: This means that the action can be redone by executing a linked redo action. Such a redo operation is run as a separate job.
  • Undo Supported: This means that the action can undone by executing a linked undo action. Such an undo operation is run as a separate job.