Contents Now Platform Capabilities Previous Topic Next Topic Getting started with workflows Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Getting started with workflows The graphical workflow editor provides a drag-and-drop interface for automating multi-step processes across the platform. Each workflow consists of a sequence of activities, such as generating records, notifying users of pending approvals, or running scripts. The workflow starts when a triggering event occurs. Common triggers include a record being inserted into a specific table, or a particular field in a table being set to a specified value. For example, you might create a workflow that runs whenever a user requests approval for an item they want to order from the catalog. When an activity completes, the workflow transitions to next activity. An activity might have several different possible transitions to various activities, depending on the outcome of the activity. Continuing the example above, if the user's request is approved, the activity might transition to an activity that notifies someone to order the item; if the user's request is denied, the activity might transition to notifying the user that their request has been denied. The graphical workflow editor represents workflows visually as a type of flowchart. It shows activities as boxes labelled with information about that activity and transitions from one activity to the next as lines connecting the boxes. At each step in a workflow: An activity is processed and an action defined by that activity occurs. At the completion of an action by an activity, the workflow checks the activity's conditions. For each matching condition, the workflow follows the transition to the next activity. When the workflow runs out of activities, the workflow is complete. Workflow activities A workflow activity contains instructions that are processed by the workflow. Activities can include running scripts, manipulating records, waiting for a set period of time, or logging an event. Workflow conditions determine whether or not the activity is performed. Activities can be added, removed, or rearranged. Transitions can be drawn between activities. This is an activity that triggers a notification: Figure 1. Sample activity For more information on available activities and their behaviors, see Workflow activities. Transitions After the workflow condition is evaluated, the workflow transition determines which activity is performed when the workflow condition is met. This is a transition that always leads from the Change Approved script to the Change Task activity: Figure 2. Sample transition Exit conditions After a workflow activity is performed, the workflow condition is evaluated to determine which transition is activated. The condition determines behavior based on a change being approved or rejected: Figure 3. Sample exit conditions Workflow example During workflow editing or while an unpublished workflow is running, only the person who checked out the workflow can view the changes. After a workflow is published, it is available to other users. The workflow moves through the process as defined in the Workflow Editor. The entire workflow is represented in one screen. For example, this is the Standard Change workflow: Figure 4. Sample change workflow On this page Send Feedback Previous Topic Next Topic
Getting started with workflows The graphical workflow editor provides a drag-and-drop interface for automating multi-step processes across the platform. Each workflow consists of a sequence of activities, such as generating records, notifying users of pending approvals, or running scripts. The workflow starts when a triggering event occurs. Common triggers include a record being inserted into a specific table, or a particular field in a table being set to a specified value. For example, you might create a workflow that runs whenever a user requests approval for an item they want to order from the catalog. When an activity completes, the workflow transitions to next activity. An activity might have several different possible transitions to various activities, depending on the outcome of the activity. Continuing the example above, if the user's request is approved, the activity might transition to an activity that notifies someone to order the item; if the user's request is denied, the activity might transition to notifying the user that their request has been denied. The graphical workflow editor represents workflows visually as a type of flowchart. It shows activities as boxes labelled with information about that activity and transitions from one activity to the next as lines connecting the boxes. At each step in a workflow: An activity is processed and an action defined by that activity occurs. At the completion of an action by an activity, the workflow checks the activity's conditions. For each matching condition, the workflow follows the transition to the next activity. When the workflow runs out of activities, the workflow is complete. Workflow activities A workflow activity contains instructions that are processed by the workflow. Activities can include running scripts, manipulating records, waiting for a set period of time, or logging an event. Workflow conditions determine whether or not the activity is performed. Activities can be added, removed, or rearranged. Transitions can be drawn between activities. This is an activity that triggers a notification: Figure 1. Sample activity For more information on available activities and their behaviors, see Workflow activities. Transitions After the workflow condition is evaluated, the workflow transition determines which activity is performed when the workflow condition is met. This is a transition that always leads from the Change Approved script to the Change Task activity: Figure 2. Sample transition Exit conditions After a workflow activity is performed, the workflow condition is evaluated to determine which transition is activated. The condition determines behavior based on a change being approved or rejected: Figure 3. Sample exit conditions Workflow example During workflow editing or while an unpublished workflow is running, only the person who checked out the workflow can view the changes. After a workflow is published, it is available to other users. The workflow moves through the process as defined in the Workflow Editor. The entire workflow is represented in one screen. For example, this is the Standard Change workflow: Figure 4. Sample change workflow
Getting started with workflows The graphical workflow editor provides a drag-and-drop interface for automating multi-step processes across the platform. Each workflow consists of a sequence of activities, such as generating records, notifying users of pending approvals, or running scripts. The workflow starts when a triggering event occurs. Common triggers include a record being inserted into a specific table, or a particular field in a table being set to a specified value. For example, you might create a workflow that runs whenever a user requests approval for an item they want to order from the catalog. When an activity completes, the workflow transitions to next activity. An activity might have several different possible transitions to various activities, depending on the outcome of the activity. Continuing the example above, if the user's request is approved, the activity might transition to an activity that notifies someone to order the item; if the user's request is denied, the activity might transition to notifying the user that their request has been denied. The graphical workflow editor represents workflows visually as a type of flowchart. It shows activities as boxes labelled with information about that activity and transitions from one activity to the next as lines connecting the boxes. At each step in a workflow: An activity is processed and an action defined by that activity occurs. At the completion of an action by an activity, the workflow checks the activity's conditions. For each matching condition, the workflow follows the transition to the next activity. When the workflow runs out of activities, the workflow is complete. Workflow activities A workflow activity contains instructions that are processed by the workflow. Activities can include running scripts, manipulating records, waiting for a set period of time, or logging an event. Workflow conditions determine whether or not the activity is performed. Activities can be added, removed, or rearranged. Transitions can be drawn between activities. This is an activity that triggers a notification: Figure 1. Sample activity For more information on available activities and their behaviors, see Workflow activities. Transitions After the workflow condition is evaluated, the workflow transition determines which activity is performed when the workflow condition is met. This is a transition that always leads from the Change Approved script to the Change Task activity: Figure 2. Sample transition Exit conditions After a workflow activity is performed, the workflow condition is evaluated to determine which transition is activated. The condition determines behavior based on a change being approved or rejected: Figure 3. Sample exit conditions Workflow example During workflow editing or while an unpublished workflow is running, only the person who checked out the workflow can view the changes. After a workflow is published, it is available to other users. The workflow moves through the process as defined in the Workflow Editor. The entire workflow is represented in one screen. For example, this is the Standard Change workflow: Figure 4. Sample change workflow
