{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":47835,"path":"servicenow-platform/legacy-workflow/getting-started-workflows.md","title":"Getting started with workflows","bundle":null,"doc_type":null,"release":"australia","body":"\n# Getting started with workflows\n\nThe graphical Workflow Editor provides a drag-and-drop interface for automating multi-step processes across the platform.\n\n## Workflow support\n\n**Important:** As of the Zurich release, new customers no longer receive the legacy workflows created and published by ServiceNow, Inc.. All legacy workflow functionality has been replaced by Workflow Studio content. Only customers who upgraded from prior versions retain the ability to use and edit existing legacy workflows. While all customers retain the ability to create legacy workflows, you are strongly encouraged to instead use Workflow Studio to create process automation content. Only Workflow Studio will receive new features and enhancements.\n\n## Parts of a workflow\n\nWorkflows consist of these parts.\n\n-   **Properties**\n\n    Specify configuration settings such as the workflow name, the table whose records the workflow acts on, and the conditions under which to run it.\n\n-   **Activities**\n\n    Specify the sequence of operations the workflow performs such as generating records, notifying users of pending approvals, or running scripts.\n\n-   **Transitions**\n\n    Specify the conditions under which to run an activity.\n\n-   **Exit conditions**\n\n    Specify the conditions under which to run a transition.\n\n-   **Contexts**\n\n    Store historical runtime information about a specific workflow run in a Workflow Context record.\n\n-   **Versions**\n\n    Store historical design information about a specific workflow in a Workflow version record.\n\n\n## Workflow life cycle\n\nA 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. You can also schedule workflows to run periodically or call them from scripts such as business rules.\n\nWhen an activity completes, the workflow transitions to the 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.\n\nThe 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.\n\nAt each step in a workflow:\n\n1.  An activity is processed and an action defined by that activity occurs.\n2.  At the completion of an action by an activity, the workflow checks the activity's conditions.\n3.  For each matching condition, the workflow follows the transition to the next activity.\n\nWhen the workflow runs out of activities, the workflow is complete. The [Workflow Context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/legacy-workflow/r_AdministeringWorkflowContexts.md) stores the execution history of the activities and transitions run. The [Workflow Version](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/legacy-workflow/c_WorkflowVersions.md) stores the design history of the activities, transitions, and exit conditions available to run.\n\n## Workflow properties\n\nThe workflow properties specify when to run a workflow and what records it acts on. For more information about workflow properties, see [Workflow properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/legacy-workflow/r_WorkflowProperties.md).\n\n## Workflow activities\n\nA workflow activity contains instructions that are processed by the workflow.\n\nActivities 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.\n\nThis is an activity that triggers a notification:\n\n\\[Omitted image \"WfActivity.png\"\\] Alt text: Sample activity\n\nWorkflow runs activities as the user session that starts them. Workflows started from record operations will run activities as the user session that performed the record operation. Workflows started from schedules or restarted from timers run activities as the System user. Workflows started from script calls run activities as the user session that started the script.\n\nFor more information on available activities and their behaviors, see [Workflow activities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/workflow-activities/c_WorkflowActivities.md).\n\n## Transitions\n\nAfter the workflow condition is evaluated, the workflow transition determines which activity is performed when the workflow condition is met.\n\nThis is a transition that always leads from the Change Approved script to the **Change Task** activity:\n\n\\[Omitted image \"WfTransition.png\"\\] Alt text: Sample transition\n\n## Exit conditions\n\nAfter a workflow activity is performed, the workflow condition is evaluated to determine which transition is activated.\n\nThe condition determines behavior based on a change being approved or rejected:\n\n\\[Omitted image \"WfCondition.png\"\\] Alt text: Sample exit conditions\n\n## Workflow example\n\nDuring workflow editing or while an unpublished workflow is running, only the person who checked out the workflow can view the changes.\n\nAfter 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:\n\n\\[Omitted image \"RoutineChange.png\"\\] Alt text: Sample change workflow\n\n"}}