Actions

if workflow is a tree, and conditions are branches, then actions are the leaves of the tree actions are the specific tasks that occur they cannot have child nodes, and are controlled by the defined conditions and actions in the workflow each action type has specific options see the table below for an introduction to each option swimlane workflow action options true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type for more detail on each of these action types, see docid\ fx9kx 99y3t6f12e96etq some fields are not available to be defined in actions, including variable fields like comments, html fields, and other non configurable data types