Actions
This content applies to legacy design tools (such as K2 Studio, K2 for Visual Studio, or the Silverlight-based K2 workflow design tool). If you have upgraded from K2 blackpearl 4.7 to K2 Five , these tools may still be available in your environment. These legacy tools may not be available in new installations of K2 Five . These legacy tools may also not be available, supported, or behave as described, in future updates or versions of K2. Please see the legacy component support policy for more information about support for these components.
Actions define the possible decisions that users can take on a task. A user always has to take an Action on a task before the task can be completed, and in most cases the workflow will follow a particular path based on the action selected. Multiple actions can be defined on a task and the Actions can be anything you wish, such as Approve, Decline or Rework.
Actions are specified on the first page of a user task wizard by typing the name of each action on a separate line.
Each action is linked by default to an outcome to determine the next step in the workflow. See the Outcomes topic for more information on configuring outcomes.