Build workflows -- Transform manual tasks and mundane work into digital workflows. Modernize legacy processes with automation. Enable app development at all levels — no-code, low-code, and pro-code — from one platform.
Workflow Studio -- Integrate workflow authoring, configuring, and monitoring into a single page experience. Consolidate playbooks, flows, actions, decision tables, and integrations into one design environment.
Explore -- Work with playbooks, flows, subflows, actions, data streams, and decision tables from a single consolidated interface. See operational details of your workflow applications and configure integration connections and credentials.
Getting started with process automation -- Learn how process automation applications can help you use the ServiceNow AI Platform to transform your manual business processes into digitized, automated workflows.
Configure -- Enable access to Workflow Studio and allow management of workflow applications.
Update to the latest version of Workflow Studio -- Workflow Studio is automatically installed on your instance. However, Workflow Studio is a ServiceNow Store application, so to get the latest features, you must update your version manually to the most recent version.
Playbooks -- Workflow Studio playbooks streamline and standardize complex processes. Automate tasks, ensure consistency, and enhance operational efficiency across your organization with intuitive, low-code workflows.
Explore -- Playbook enable process owners to author cross-enterprise workflows and create a single, unified process. Build the underlying processes for playbooks that Playbook Experience agents and fulfillers use.
Playbook builder -- Playbooks is a component in Workflow Studio. Workflow Studio gives you a streamlined way to author, configure, and monitor playbooks, flows, subflows, actions, and decision tables in one place.
Playbook Experience -- Understand how Playbook work in the ServiceNow AI Platform to automate cross-functional processes and consolidate them into task-oriented views for your end users.
Now Assist features for Playbooks -- Now Assist provides AI-powered capabilities across the Playbook experience, from generating and recommending playbooks to enabling autonomous, agentic execution.
Domain separation in Playbooks -- Data separation is supported for Playbooks. The domain value of the triggering input record determines the domain context. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Configure -- Set up and monitor Playbooks and Playbook Experience.
Activate Playbooks -- Activate the Workflow Studio application to create flows, playbooks, and more for any of your use cases.
Administering Playbooks -- Monitor and troubleshoot issues by reviewing playbook executions.
User access to Playbooks in Workflow Studio -- Administrators can grant users access to Playbook by assigning delegated development permissions or directly assigning a user role. Administrators can also specify which features and content a user can access based on user roles.
Archive process contexts -- Improve database query performance by archiving unneeded records for playbooks that are in a Complete, Error, or Cancelled state.
Build Playbooks -- Playbooks are ServiceNow AI Platform representations of cross-enterprise processes for your organization. Create and activate a playbook to run your digitized business process on the ServiceNow AI Platform.
Building your first playbook -- Learn the basics of designing an automated process for your organization. Get an overview of how Workflow Studio Playbooks work in the ServiceNow AI Platform.
Create a sample playbook -- Create a sample playbook to standardize and automate how Service Desk agents handle chat interactions with VIP users.
Create a scheduled trigger for Playbook -- Create a scheduled trigger that starts your playbook at the required time and interval. You can schedule a trigger in any time zone, with or without an end date for the schedule.
Stages and activities -- In Playbook, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process.
Activity definitions -- Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.
Create an activity definition -- Specify the action or subflow you want an activity to run. Configure the inputs you want playbook designers to set when adding the activity to a playbook. Select the experience you want end users to have when the activity runs.
Use AI agent as an activity -- Use an existing AI agent as an activity in your playbook to automate tasks. The AI agent gathers the required context, performs the work, and produces outputs that subsequent activities can consume.
Use an AI skill as an activity -- Use an existing AI skill as an activity in your playbook to perform lightweight, focused AI tasks. When the playbook reaches the activity, the skill runs, produces structured outputs, and passes those outputs to subsequent activities.
Automation Assets -- Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.
Start with delay input properties -- Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions.
Optional activities -- Enable your agents and fulfillers to add additional activities as they go through a playbook.
Decision activities -- Create and define branches with different conditions for different paths between activities.
Decision stages -- Create and define branches with different conditions for different paths between stages.
Questionnaire activity -- Collects inputs from a user during a playbook run to use later in the playbook.
Create a questionnaire -- Create and insert a new questionnaire for agents to respond to.
Go back activity -- The Go back activity defines a conditional return point in a playbook, enabling the playbook to loop back to an earlier activity, stage, or the start of the playbook based on an outcome.
Add a Go back activity to a playbook -- Add a Go back activity to a decision branch in your playbook and configure where the playbook returns to when the activity runs.
Parallel branches -- Add branches for activities and stages that run in parallel to another branch of activities and stages.
Add dynamic inputs to an activity -- Configure your activity to show a certain set of fields based on the value of another input, such as a selected catalog item, selected decision table, or even a REST API response.
Create a playbook -- Create a playbook to set up an automated business process. Use Playbook builder in Workflow Studio to add stages, activities, triggers, and runtime permissions, then activate the playbook to make it available to agents and fulfillers.
Playbook generation from text prompt or image -- Generate a playbook using AI from text prompt or image inputs. For example, you can enter a text description to generate a playbook for managing customer support cases.
Playbook generation from a KB article -- Generate a playbook directly from an existing knowledge base article to reduce manual effort when creating playbooks for documented processes.
Generate a playbook from a knowledge base article -- Use an existing knowledge base article to generate a playbook using AI. The stages and activities are automatically populated based on the article content.
Generate recommendations for placeholder activities -- Select the activity definition for a placeholder activity from a list of AI-generated recommendations. The system generates recommendations based on an activity’s name and description.
Preview an activity's runtime UI -- See how an activity will appear to end users when the playbook runs. Use the preview to confirm the activity's appearance in real-time, and adjust its configuration before publishing the playbook.
Test a playbook -- Verify that your playbook works as expected by running the playbook with test trigger data. Identify and resolve all errors before activating your playbook.
Enabling playbook restart -- Learn how playbook restart during runtime works and how restart rules control the behavior of stages and activities during a restarted run.
Configure restart for Playbooks -- Configure restart so that agents and fulfillers in Playbook Experience can restart a playbook from the beginning, or from a specific stage or activity.
Duplicate a playbook -- Make a copy of an existing playbook with the same trigger, stages, activities, and experience configurations as the original. Edit the duplicated playbook to quickly create a working variation.
Playbook summarization -- Use AI-generated overviews of a playbook's stages, activities, triggers, and inputs to understand its purpose and flow without going into the details of what is being done at activity and stage level.
Generate a playbook summary -- Generate an AI-generated summary of the stages, activities, triggers, and inputs of a playbook from the Workflow Studio canvas.
Add translations for Playbooks -- Make Playbooks available in multiple languages during runtime, to support worldwide business processes.
Design Playbook Experience -- After building playbooks in Workflow Studio, Playbook Experience administrators can configure the layouts and further customize playbook functions during runtime.
Customize Playbook Experience -- Customize the layout of your Playbook Experience with base system modular components, templates, and more via integrated UI Builder functionality.
Customize a playbook in UI Builder -- Use UI Builder pages and modular components for custom playbook layouts to customize the end user's Playbook Experience in a configurable workspace, Service Portal page, or mobile web page.
Playbook layout bundles -- Playbook layout bundles are pre-wired component sets in UI Builder that determine how a playbook renders for end users at runtime. Each bundle packages a controller, supporting components, and styling so that authors can drop a complete playbook experience onto a page without configuring each component individually.
Set up mappings between themes -- Make sure that playbooks run as expected in your Service Portal by setting up mappings between your Service Portal theme and the UXF theme used in UI Builder.
Configure a playbook for ServiceNow mobile -- Configuring a playbook for ServiceNow mobile is exactly the same as in a configurable workspace, but with an additional step for embedding the playbook.
Reflow for playbook components -- Apply reflow to out-of-the-box standalone and custom layout Playbook Experience components so that the UI adjusts when you resize your window or zoom.
Apply Reflow to playbook components -- Apply reflow to out-of-the-box standalone and custom layout Playbook Experience components so that the UI adjusts when you resize your window o r zoom.
Playbook record generator -- Use the playbook record generator to guide a user through the record creation process using the Playbook Experience.
Configure a Guided Decision Playbook -- Configure a Guided Decision Playbook to walk users through decision-driven questions and actions toward a recommended outcome, delivered as a seamless runtime experience that runs standalone or inside another playbook. The Guided Layout removes the activity and stage pickers and consolidates previous responses into an accordion.
Configure guest user access -- Set up a playbook, public audience record, and UI experience so that guest users can run playbooks without a ServiceNow login through a public URL.
Configure a Wizard layout playbook -- Build a wizard-driven Playbook to present a playbook as a guided, step-by-step experience that walks end users through a process one activity at a time. The Wizard layout adds numbered step navigation and forward and back controls to a standard playbook.
Nested Playbooks -- Embed or "nest" a child playbook within a parent playbook to organize your processes and then present the appropriate sequence of steps in the runtime experience. Creating child playbooks that can be used in other parent playbooks enables you to define sets of activities that can be re-used across multiple playbooks to avoid duplication.
Create a child playbook -- Nest a child playbook within a parent playbook to organize your processes. Creating child playbooks that can be used in other parent playbooks enables you to define sets of activities that can be re-used across multiple playbooks to avoid duplication.
Create a parent playbook -- After you have created a nestable child playbook, then you can create a parent playbook to host the child playbook.
Wizard layout -- Wizard layouts present a playbook as a guided, step-by-step experience that helps end users complete a process in a clear and structured way.
Configure wizard layout -- Configure a wizard layout that presents a playbook as a guided, step-by-step experience for end users.
About Playbook Experience -- Interact with a business workflow in real time from within Workspace. Agents can use Playbook Experience to update records, upload attachments, and complete tasks across multiple workflow activities.
Add an activity -- Add preselected optional activities to a Playbook Experience if available.
Testing support -- The Automated Test Framework (ATF) can be used to create automated tests to confirm your playbooks run as planned.
Configure testing support -- Configure the Automated Test Framework (ATF) to support testing playbooks by authoring tests in the ATF UI on your ServiceNow instance.
Run a test -- After creating your test and adding steps, run and monitor the progress of your automated test.
Restart a playbook -- Restart a playbook from the beginning, an activity, or a stage.
Cancel a playbook -- Cancel a playbook to stop a business workflow when no longer valid.
Using activity stream -- Use activity stream within a playbook to add comments or notes, and view communication and task history for the parent or associated record.
Playbooks reference -- Guides, lists, tables and more that you can reference as you work with Playbooks and their associated components.
Playbooks system properties -- Review the system properties for Playbooks. You can configure these properties to control how the system handles Playbooks events.
Playbooks roles -- Grant users one or more Playbooks roles to enable them to create triggers, playbooks, and activity definitions.
Playbook statuses and activation states -- View your playbook's status in the main header of the Playbooks builder. This status indicates whether the playbook is active or inactive.
Process executions -- A process execution is a single, runtime instance of a playbook. Process execution records provide runtime information about playbooks, such as the current state and input record.
Activity executions -- Activity execution records provide runtime information about activities in a playbook, such as the activity's current state and associated record.
Create Task activity -- Create a task record from previously gathered or generated data.
Instruction activity -- Display a simple message to guide end users through your playbook.
User Form activity -- Use this activity to surface a record to the end user. This activity requires you to select a table and record, and the desired form view that should be surfaced to the end user in your playbook. The end user can then interact with this record accordingly. Display a form during runtime to collect input values for your playbook.
Placeholder activity -- Display an activity card in Playbooks to indicate what a future activity does.
Interactive activities -- An interactive activity prompts a user for input in your playbook as it runs.
Adobe Acrobat Sign activities -- Enable agents and fulfillers to collect electronic signatures during a playbook run, via Workflow Data Fabric's Adobe Acrobat Sign spoke.
Collect User Data activity -- Collects inputs from a user during a playbook run to use later in the playbook.
Create Record activity -- Pause the playbook and prompt the end user to create a record in a form view. Use this activity to allow the end user to create a record. This activity requires you to configure the desired table for which record to create, and the desired form view that the end user will see when creating the record.
Create Child Case activity -- Enable agents and fulfillers to create a child case during a playbook run.
Create Child Task activity -- Enable agents and fulfillers to create a child task during a playbook run.
Docusign activities -- Enable agents and fulfillers to collect electronic signatures during a playbook run, via Workflow Data Fabric's Docusign spoke.
Guided Decision activity -- Choose a decision tree from your Guided Decisions framework to step agents through how to proceed with a task.
Invoke PaCE activity -- Enable the Policy as Code Engine (PaCE) activity in Playbooks to develop playbook processes.
Microsoft Teams activities -- Enable agents and fulfillers to send direct messages and post in Microsoft Teams channels during a playbook run, via Workflow Data Fabric's Microsoft Teams spoke.
Request Multi-Level Approval activity -- Enable agents and fulfillers to submit an approval requests to first and second-level managers during a playbook run.
Request Ad Hoc Approval activity -- Enable agents and fulfillers to specify which user(s) should complete approval request(s) during a playbook run.
Send Email activity -- Create an email from previously gathered or generated data. Use this activity to send an email. This activity requires the playbook author to define who the email should be sent to, the subject, and the body. This activity surfaces the pre-defined content for the email to the end user so that the end user can confirm before sending the email.
Slack activities -- Enable agents and fulfillers to send direct messages and post in Slack channels during a playbook run, via Workflow Data Fabric's Slack spoke.
Two Step Instruction activity -- Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message.
Wait For Condition activity -- Pause the playbook until a record has field values that match a set of conditions.
Non-Interactive activities -- A non-interactive activity runs entirely behind-the-scenes on the ServiceNow AI Platform and doesn't require any user input.
Automated Create Record activity -- Create a record without pausing the playbook to ask for user input. When the activity runs, it immediately creates the record and continues to the next activity in the playbook. The record must meet server-side validation rules such as data policies, business rules and dictionary-defined mandatory fields but ignores UI policies.
Automated Send Email activity -- Create an email from previously gathered or generated data without pausing the playbook to ask for user input. When the activity runs, it immediately sends the email and continues to the next activity in the playbook.
Automated Update Record activity -- Update a record without pausing the playbook to ask for user input. When the activity runs, it immediately updates the record and continues to the next activity in the playbook. The record must meet server-side validation rules such as data policies, business rules and dictionary-defined mandatory fields but ignores UI policies.
Autocompleting User Form -- Display a form during runtime to collect input values for your playbook.
Make a Decision-First Match activity -- Execute rules in a decision table. When this activity runs, it will immediately finish and continue the process execution. The activity returns the result of the first matching decision rule, based on the rank of the rules. To return results from all matching rules, add the decision table to a subflow.
Agentic Playbooks -- Agentic Playbooks use AI agents to help you work more efficiently. AI agents complete tasks and generate outputs for your playbook activities.
Explore -- Integrate AI agents into your workflows, and enable automation, adaptability, and transparency across your business processes.
Configure -- As a playbook author in Workflow Studio, configure AI Agents to perform a playbook activity.
Use -- Monitor and complete agentic activities as needed.
Reference -- Reference topics provide associated roles and guidelines for configuring Agentic Playbooks.
Roles -- The following roles are required for runtime users to access Agentic Playbooks, and come with the Now Assist for Platform AI agents skill.
Getting started -- Create a sample flow with a trigger and base system actions that requires an approval.
Build your first flow -- Step through an example of how to build, test, and activate a sample flow in Workflow Studio.
Build a flow from a template -- Step through an example of how to build, test, and activate a flow using a flow template in App Engine Studio.
Use the help panel -- Browse topics in the side help panel to learn more about building flows and actions, working with data and spokes, and stepping through guided tours in Workflow Studio.
Flows -- Flows automate a repeatable multi-step process. When the flow trigger conditions are met, the flow runs a sequence of reusable actions and flow logic to complete the process.
Architecture Overview -- Understand how Workflow Studio works within the ServiceNow AI Platform to activate, trigger, and process flows and actions.
Data pills -- Each time you add an action to a flow, Workflow Studio adds a data pill to store its results. The data pill name indicates its sequence in the flow and its data type.
Domain separation and Workflow Studio -- Domain separation is supported in Workflow Studio. Workflow Studio supports domain separation of business logic, which lets each tenant domain have its own flows, actions, and subflows. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Generate group approvals for domain separated requests -- Configure Workflow Studio to generate approvals for all members of a group or to restrict approvals to only group members who are visible from the domain of the request.
Explore actions -- Actions automate a repeatable task or operation within a flow. Flows run actions by passing them data as inputs. Actions run a sequence of steps to complete the task, and pass data to the flow as outputs.
Conversational actions -- Run a Workflow Studio action from a Now Assist conversation. Create and configure the conversational skill from Workflow Studio.
Available conversational actions -- Workflow Studio provides a set of actions that are preconfigured to be compatible with and callable by conversational interfaces such as Now Assist.
Check for conversational compatible actions -- Run a compatibility check on new or all actions to determine if they are conversational compatible. Review the inputs of an action to determine if their data types are compatible.
Explore subflows -- Subflows automate a repeatable multi-step process that also produces an output needed by another process. When a playbook, flow, or script calls a subflow, the subflow runs a sequence of reusable actions and flow logic to complete the process and produce output values.
Conversational subflows -- Run a Workflow Studio subflow from a Now Assist conversation. Create and configure the conversational skill from Workflow Studio.
Available conversational subflows -- Workflow Studio provides a set of subflows that are preconfigured to be compatible with and callable by conversational interfaces such as Now Assist.
Check for conversational compatible subflows -- Run a compatibility check on new or all subflows to determine if they are conversation compatible. Review the inputs of a subflow to determine if their data types are compatible.
Flow diagramming view -- Create and view flows as diagrams. See the paths a flow can follow and the connections between elements.
Flow execution details -- View run-time information about an action or flow directly from the design environment, such as the current state, items run, and values produced. Open related records from embedded ServiceNow AI Platform editors or in a new tab.
Flow debugger -- Debug flows and subflows from a dedicated Workflow Studio tab. Set breakpoints and step through a paused flow to review configuration and runtime values.
Saved flow triggers -- Save a set of trigger definitions as a reusable trigger. Enable flow authors to select the saved trigger from some or all application flows. Specify whether flow authors can see the trigger details or add conditions to the trigger.
Configure flows -- Configure user access, API access, and properties for Workflow Studio flows.
Flow administration -- Identify and troubleshoot potential issues by reviewing action and flow executions, their result state, and their runtime duration.
Flow execution details retention -- Due to the large amount of data consumed by flow execution details, your instance uses data retention policies to delete this data after a set time period.
Flow execution settings -- Specify the runtime settings for an individual flow, subflow, or action such as the run priority, reporting level, and logging level.
Activate flow reporting -- Choose whether to generate execution details for all flows and actions run, just for individual flows and actions, or just when you test a flow or action. Specify the level of detail the execution details contain.
Activate reporting for an individual flow, subflow, or action -- Choose whether to generate execution details for all flows and actions run, just for individual flows and actions, or just when you test a flow or action. Specify the level of detail the execution details contain.
Activate reporting for all items -- Choose whether to generate execution details for all flows and actions run, just for individual flows and actions, or just when you test a flow or action. Specify the level of detail the execution details contain.
FDIH Dashboard -- Use a single dashboard to view usage, execution, and debug information for Workflow Studio and Integration Hub transactions. Open links to related Workflow Studio properties, logs, events, and editors.
Flow priority -- Specify the priority that you want a background flow to have in relation to other flows waiting to be run. Run a group of higher priority flows before running any lower priority flows.
Show flow priority field -- Configure the Setting list and form to show the Flow Priority field.
Set flow priority -- Determine the order in which worker threads run background flows. Use a mix of flow priorities to distinguish between flows to defer and flows to run first.
See related flows for action -- See the list of flows that include a custom action. Determine the impact that changes to an action have on published and draft flows.
User access to flows -- Administrators can grant users access to Workflow Studio flows by assigning delegated development permissions or directly assigning a user role. Administrators can also specify which features and content a user can access based on user roles. Application developers can access Workflow Studio functionality through APIs for flows, subflows, and actions.
Manage access -- Restrict access to individual Workflow Studio flow features by user role. Specify what additional roles a user must have to access an individual feature such as copy a flow.
Content filtering -- Specify which content a user can access based on the user's role.
API access -- Application developers can access Workflow Studio functionality through APIs for flows, subflows, and actions. Flow authors can enable individual flows, subflows, and actions to be client callable during design.
Restricted caller access -- Track flows and actions that require access to cross-scope resources. Allow or deny flows and actions access to cross-scope resources.
Build flows -- Workflow Studio is the default ServiceNow AI Platform process automation builder used to create flows. Workflow Studio replaces the Workflow Editor.
Create a flow -- Run a sequence of actions and flow logic when the trigger conditions occur.
With Now Assist -- Use generative AI to create a flow from text directions and images.
With Kafka message trigger -- Build a flow that processes events from a Kafka stream. Start the flow when an event is available in the specified topic.
With a MetricBase trigger -- Start a flow when a MetricBase trigger is met. MetricBase triggers track time series data and can monitor when a threshold is reached, when a trend is detected, or when a system stops reporting data.
With a Performance Analytics trigger -- Use Performance Analytics indicators to start a flow. Define the flow start conditions as a set of Proactive Analytics KPI scores and KPI threshold values.
With a Service Catalog trigger -- Start a flow when a Service Catalog item is requested to automate the fulfillment process.
With an SLA Task trigger -- Configure your Service Level Agreement (SLA) definition to run a flow as the action plan.
With an external trigger -- Set up a flow with a base system external trigger definition. The flow responds to an event-driven external trigger from a third-party system. For example, run a flow when an issue is created in a third-party issue-tracking system.
With specified roles -- Create a flow or subflow that runs with assigned roles. Assigning roles enables you to create a user-initiated flow that runs with its own roles rather than the user's roles.
Create flow Service Catalog variables -- Create Service Catalog variables that are only available to a specific Service Catalog flow. Flow-specific variables are available to catalog tasks and actions in the flow.
Create a decision table in a flow -- Create the structure for a decision table while you author your flow in Workflow Studio. Use data from the flow to create inputs, conditions, and results for the decision table, all in a convenient modal. For example: You can store the logic for incident assignments in a Decision Table, and then use that Decision Table within a flow.
Copy a flow -- Copy a flow to give it a new name and move it to another application scope.
Default read-only flows -- Open existing flows in a read-only state to protect them from accidental changes. While a flow is in a read-only state, you can only review, test, deactivate, or request to edit it.
Flow and subflow stages -- Communicate the current stage of a request, flow, or subflow with an end user.
Configure and add stages -- Configure when stages display to a user, define stage state labels, and add stages to a flow or subflows within Workflow Studio.
Flow error handler -- Enable flows to catch errors. Run a sequence of actions and subflows to identify and correct issues. For example, have flows log output values, send notifications, and run corrective subflows when they produce an error.
Add an error handler to a flow -- Run a sequence of Workflow Studio actions and subflows to identify and correct issues that are caused by flow errors.
Flow history -- View and manage the history of a flow. See past configurations of a flow to copy, restore, or remove them.
View flow history -- View the change history of a flow by date and user.
Add an annotation -- Add a text description to a flow history entry. Summarize the purpose or contents of a particular flow history entry.
Flow history compare view -- Compare two flow history entries in a side-by-side view. Use the step highlighting and change type icons to determine what flow components have been added, removed, and changed.
Compare flow histories -- Compare two flow histories to see what content was added, removed, and updated.
Delete an entry -- Delete a flow history entry from the flow history list.
Restore a flow -- Restore a flow to a previous configuration. Create a new flow history entry for the restore operation.
Save a copy -- Create a copy of a flow history entry and save it as a new flow.
Flow roles -- Create flows and subflows that run with specific roles. Assigning roles enables you to create user-initiated flows that run with their own roles rather than the user's roles.
Flow Template Builder -- Enable citizen developers to create their own flow templates. Flow Templates guide flow authors to create flows for common use cases. Use the flow template builder to define flows, actions, and flow template variables.
Create a template using Flow Template Builder -- Enable citizen developers to create their own flow templates. Flow Templates guide flow authors to create flows for common use cases. Use the flow template builder to define flows, actions, and flow template variables.
Create a flow from a template in App Engine Studio -- Enable citizen developers to create their own flow templates. Flow Templates guide flow authors to create flows for common use cases. Use the flow template builder to define flows, actions, and flow template variables.
Inline scripts -- Enable users with coding experience to write inline scripts that set and modify input values during the configuration of an action or flow. Use inline scripts to modify input values that require small format conversions, data transformations, or math operations.
Save as you go flows -- Save flows, subflows, and actions automatically as you work on them.
Summarize a flow -- Generate a summary of a flow with Now Assist for Creator.
Variables -- Similar to Workflow scratchpad variables, create variables that you can use and modify directly in your flow. Access flow variables as data pills directly in the Data panel.
Create a variable -- Create a flow variable to store and retrieve a value throughout a flow.
Build subflows -- Workflow Studio is the default ServiceNow AI Platform process automation builder used to create subflows. Workflow Studio replaces the Workflow Editor.
Create a subflow -- Reuse an entire flow's content as a subflow. Define the input data the subflow uses and the output data it generates. Call subflows from other flows or script.
Create conversational subflow skill -- Create a skill for the conversational subflow and make the skill available for users in a conversation. You can have multiple skills for the same subflow.
Copy a subflow -- Copy a subflow to give it a new name and move it to another application scope.
Create a decision table in a subflow -- Create a decision table structure while you author your flow in Workflow Studio. Use data from the subflow to create inputs, conditions, and results for the decision table, all in a convenient modal.
Convert items to subflow -- Convert consecutive items of a flow into a new subflow that preserves data pill references between the converted items. Update the original flow to replace the converted items with a call to the new subflow.
Create a template value input -- Enable flow authors to set field values for a record being created or updated. Use a template value input to set different field values each time you add an action or subflow to a flow.
Add an annotation -- Add a text description to a subflow's flow history entry. Summarize the purpose or contents of a particular flow history entry.
Delete an entry -- Delete a subflow's flow history entry from the flow history list.
Restore a subflow -- Restore a subflow to a previous configuration. Create a new flow history entry for the restore operation.
Save a copy -- Create a copy of a flow history entry and save it as a new subflow.
Test a subflow -- You can test a subflow alone, or when added to a flow. When testing a subflow alone, you must define the inputs that the subflow uses in its actions. Because a subflow does not have a trigger, testing a subflow runs the actions using the defined input values. Unless updated, subsequent tests use the same inputs defined in the initial test run.
Test conversational subflow -- Test a conversational subflow to verify it responds correctly to user inputs and performs the expected operations before deploying it in production.
Build actions -- Workflow Studio is the default ServiceNow AI Platform process automation builder used to create actions. Workflow Studio replaces the Workflow Editor.
Getting started with actions -- Transform the Ask for Approval action into a reusable action that always requires manager approval.
Test an action -- Test an action before publishing it for other users.
Copy an action -- Copy an action to give it a new name and move it to another application scope.
Dynamic inputs -- Generate a list of action inputs or input values each time that someone configures the action in a flow. Dynamic inputs can display a list of related action inputs, a list of fields from a record, or a list of options available in a choice list.
Get started with dynamic inputs -- Create a sample action that illustrates using all available types of dynamic inputs in a flow.
Dynamic outputs -- Access action and subflow outputs as dynamically generated data pills during flow design. You can also build data gathering actions to generate complex objects from ServiceNow AI Platform and Integration Hub outputs.
Action error evaluation -- Enable actions to catch step failures and continue running. Identify when specific error conditions occur and return your own action status code, status message, and error state.
Add error condition -- Enable an action to return custom status information when specific conditions are met. Specify whether a flow considers your custom action status as an error or a successful run.
Retry policy -- Automatically retry failed requests when a step encounters an intermittent issue such as a network failure or request rate limit. Set a retry policy to prevent having to manually trigger the step again.
Create a retry policy -- Automatically retry failed requests when a step encounters an intermittent issue such as a network failure or request rate limit. Set a retry policy to prevent having to manually trigger the step again.
Create conversational action skill -- Create a skill for the conversational action and make the skill available for users in a conversation. You can have multiple skills for the same action.
Test conversational action -- Test a conversational action to verify it responds correctly to user inputs and performs the expected operations before deploying it in production.
Complex data -- Use a graphical interface to work with collections of complex structured data. Help design users understand the organization of structured data, and add, remove, or configure its individual elements.
Create data structure -- Organize multiple data variables into a structure to process them as a unit and identify the individual items within it.
Save data structure -- Save the data structure of child variables within an Object variable for later reuse.
Load data structure -- Load a data structure of child variables within an Object variable.
Script support for complex data -- Create and reference complex data from a script. Use a script when your source data comes from a data stream, a REST step response, or a Look Up Records step.
Build triggers -- A trigger contains the start conditions for your automation. You can create separate triggers for each flow or create a reusable saved trigger that you can use in multiple flows.
Create record based trigger -- Create a reusable trigger definition that responds to a record-based event. When a record is created or updated in a specific table, the trigger activates and starts the flows where it is used. You can allow flow authors to select the saved trigger, view its conditions, or add their own conditions.
Create a scheduled trigger -- Create a scheduled trigger that starts your flow when you need. Schedule the trigger to start your flow on a specific date and time or repeatedly at scheduled intervals. Reuse the trigger in flows that need to run on the same schedule.
Create trigger using business calendar -- Schedule a recurring trigger to run based on a business calendar, so your automation run only when your business is actually operating, on working days, active shifts, or custom production schedules.
Create an external trigger -- Save a set of trigger definitions as a reusable trigger that responds to external events through webhooks. When an event occurs in the configured third-party application that meets the specified conditions, the trigger is activated.
Managing external event sources -- Create and manage external event sources for a spoke or a scoped application that listen to events occurring in an application outside ServiceNow. Then, you can create external trigger definitions and associate them with the external event sources. When the event that you specify in the external trigger definition occurs, it starts one or more flows on your ServiceNow instance.
Create an external event source -- Create and manage external event sources for a spoke or a scoped application that listen to events occurring in an application outside ServiceNow. Then, you can create external trigger definitions and associate them with the external event sources. When the event that you specify in the external trigger definition occurs, it starts one or more flows on your ServiceNow instance.
Update an external event source -- Create and manage external event sources for a spoke or a scoped application that listen to events occurring in an application outside ServiceNow. Then, you can create external trigger definitions and associate them with the external event sources. When the event that you specify in the external trigger definition occurs, it starts one or more flows on your ServiceNow instance.
Delete an external event source -- Create and manage external event sources for a spoke or a scoped application that listen to events occurring in an application outside ServiceNow. Then, you can create external trigger definitions and associate them with the external event sources. When the event that you specify in the external trigger definition occurs, it starts one or more flows on your ServiceNow instance.
Use a saved trigger -- Instead of creating a trigger, use a saved trigger in your flow. Using a saved trigger enables you to reuse standardized trigger logic across flows, reducing the effort, improving consistency, and simplifying ongoing maintenance.
Edit trigger -- Edit a saved trigger in Workflow Studio to update the trigger definitions or other options according to your business needs.
Detach trigger -- View a list of flows that are associated with a saved trigger, and detach it from any of the flows. Detach a saved trigger before you specify different start conditions for your flow or before you delete the trigger.
Delete trigger -- Delete a saved trigger that you no longer need.
General guidelines -- Create, run, troubleshoot, and monitor your Workflow Studio components more effectively. Use these guidelines to optimize the performance of your Workflow Studio components.
Actions -- Actions can be added to any flow, enabling process analysts to automate ServiceNow AI Platform features without having to write code.
Add Worknote Link to Context action -- Add a journal field entry containing a link to the current flow context record. Use the link to view the flow execution details of the current flow. You can add a flow context link to any record that has a journal field.
Ask for Approval action -- Request approval for a record. Configure a set of rules to automatically approve, reject, or cancel an approval request without having to write script. Add a due date to automatically approve, reject, or cancel when a decision has not been made by a designated time.
Associate Record to Email action -- Associate a record with an Email [sys_email] record so that you can track which record is affected by the email.
Create Catalog Task action -- Creates a record in the Catalog Task [sc_task] table associated to a requested item in the Requested Items [sc_req_item] table. Adds the catalog task record as data to be used in the flow.
Create Flow Data action -- Collect data from agents interacting with a Workspace playbook. Use this data to create reusable activities for process owners using Playbooks.
Create Record action -- Creates a record on any table. You can dynamically add and configure fields for the record.
Create or Update Record action -- Create or update a record in a ServiceNow table using a single operation. Update a record that exists, or create a record using the values provided.
Create Task action -- Create a task record in an extension of the Task table. After you choose the task table, you can dynamically select the fields to configure the action. Defining the Parent field associates the task to a parent record.
Copy Attachment action -- Copies an attachment from the Attachments [sys_attachment] table to a target record.
Delete Attachment action -- Removes one or all attachments associated with a record and deletes the attachment record from the Attachments [sys_attachment] table.
Execute Skill action -- Run a published Now Assist skill and use the skill outputs in a flow or subflow.For existing actions and subflows, copy the short description from the product documentation, or insert a content reference to it. For new actions and subflows, create reusable content and insert a content reference to the short description.
Fire Event action -- Create a system event record in the Event [sysevent] table to be processed by a scheduled event handler. Pass event parameters using flow data.
Get Attachments on Record action -- Access the list and count of the attachments associated with the provided source record as data pills in a flow. Use flow logic or scripting to process each attachment in the list of the attachments that the action returns.
Get Catalog Variables action -- Select variables from multiple template catalog items and variable sets using the Get Catalog Variables action.
Look Up Record action -- Look up a record from any table based on defined conditions.
Look Up Records action -- Look up multiple records on any table using defined conditions.
Move Attachment action -- Associates a record from the Attachment [sys_attachment] table with a target record. Removes the attachment from any other associated records.
Move Email Attachments to Record action -- Move attachments from an email to a record so that the files are available to your users when they view the record.
Record Producer action -- Create a Task record from a Record Producer Catalog Item [sc_cat_item]. The Task record inherits values from the catalog item's variable values.
Send Email action -- Send an email to specified users or groups as an action in a flow.
Send Notification action -- Send an email notification to predefined recipients with predefined content. Select or create a Notification [sysevent_email_action] record to configure the email notification.
Send SMS action -- Send an email-based SMS text message to specified users or groups using your instance email server. Recipients must have an SMS device configured to receive the message.
SLA Percentage Timer action -- Identify when a task SLA record reaches a specific percentage value and perform other actions or flow logic that is based on the SLA percentage. For example, send a notification when an SLA percentage timer completes.
Update Multiple Records action -- Look up and update multiple records as a single action. Using this action removes the need to separately look up a list of records and then process the list with For Each flow logic. Set field values with a template or add and configure them using data pills.
Update Record action -- Update an existing record in a table. You can dynamically add and configure fields for the record.
Use an AI agent action -- Use flow data to run an AI agent and configure the expected agent output for use later in the flow.
Wait For Message action -- Pause a flow until it receives a specific message from the flow API. Specify the string message that resumes running the flow, and optionally provide a time out value to resume the flow if no message is received after a specific amount of time.
Flow logic -- Enable flows and subflows to specify conditional or repeated actions. Combine the elements of flow logic to create workflows in a graphical interface with little or no scripting.
Assign subflow outputs flow logic -- Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
Call a workflow flow logic -- Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
Do the following until flow logic -- Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
Dynamic flows flow logic -- Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
End Flow flow logic -- Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
Exit Loop flow logic -- Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
For Each flow logic -- Apply one or more actions to each record in a list of records.
Go back to flow logic -- Return to a prior step in the flow to repeat a sequence of actions.
If flow logic -- Selectively apply one or more actions only when a list of conditions is met.
Make a decision flow logic -- You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
Set Flow Variables flow logic -- Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
Skip Iteration flow logic -- Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
Try flow logic -- Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.
Wait for a duration flow logic -- Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.
Flow integrations -- Expand the capabilities of Workflow Studio flows with additional subscriptions and spokes.
Spokes -- Add application-specific content to Workflow Studio by installing spokes.
Benchmarks Spoke -- Provides read-only actions for the read-only Benchmark Recommendation Evaluator flow.
Connect spoke -- Provides actions to automate the creation of conversations, to add users to a conversation, and to send messages to a conversation. These actions work with Connect API version 3 and later.
Customer Service Spoke -- Provides actions for flow designers to use when creating Customer Service Management business processes. Requires the Customer Service Management [com.sn_customerservice] plugin.
External Related Files spoke -- The External Related Files spoke stores information about files in third-party systems and helps you manage the information.
Field Service Spoke -- Provides actions for flow designers to use when creating Field Service Management business processes.
ITSM spoke -- Provides flow and actions associated with ITSM. Requires the ITSM application suite.
Machine Learning solutions for Flow Designer -- With Predictive Intelligence for Flow Designer (com.snc.ml_flowdesigner), you can deploy machine learning solutions in your instance. This spoke provides actions to incorporate Predictive Intelligence model predictions into flows.
Robotic Process Automation (RPA) Spoke -- With Robotic Process Automation, your flow designers can use actions to assign and unassign users to and from an attended automation process, add work items to a queue, update work items, fetch process jobs, get the status of a process job, and trigger a bot process.
Security Operations spoke -- Provides Security Operations actions for flow designers to manage Security Incident Response flow templates.
Visual Task Board (VTB) Spoke -- Provides VTB actions for flow designers to manage the boards, lanes, cards, board members, and assignees.
Flow trigger types -- Each trigger type defines when a flow starts and the starting data available to it. There are triggers for record operations, dates, and application operations.
Input and output data variables -- Actions and subflows use variables to store input and output data. The variable data type determines what kind of data it stores and its advanced configuration options.
Approval rules data type -- Store the conditions for approving or rejecting an approval requests.
File attachment data type -- Store a single file attachment as part of the action or flow's associated record rather than a record in the system Attachment table.
Integer data type -- Store numeric integer data. Integers are whole numbers only. Fractions and decimals values are not supported.
JSON data type -- Store JSON formatted text values. JSON values can be generated by integration steps or by scripts.
List.[Table] data type -- Stores a list of record Sys IDs associated to a specific table. This variable supports ServiceNow AI Platform List field options such as default records and reference qualifiers.
Records.[Table] data type -- Stores one or more Sys ID references to records in a specific table. The Records data format is also known as a Glide List since it stores a list of GlideRecord Sys ID values.
String data type -- Store alphanumeric text values using JavaScript data conventions.
Table name data type -- Store a table name value as specified in the database dictionary. Table names are always alphanumeric strings.
True/false data type -- Store true or false values using JavaScript data conventions.
Variables.[Table] data type -- Store a reference to a specific table of Glide variables such as a decision input variable.
Steps -- A step performs a single operation in an action. You can use Workflow Studio to add steps to a custom action.
Ask for Approval step -- Request approval for a record. Configure a set of rules to automatically approve, reject, or cancel an approval request without having to write script. Add a due date to automatically approve, reject, or cancel when a decision has not been made by a designated time.
Call Now Assist Skill step -- Run a published Now Assist skill from an action. Configure the Now Assist skill inputs and skill outputs from the step inputs and step outputs.
Create Record step -- Creates a record on any table. You can dynamically add and configure fields for the record.
Create or Update Record step -- Create or update a record in a ServiceNow table using a single operation. Update a record that exists, or create a record using the values provided.
Create Task step -- Create a task record in an extension of the Task table. After you choose the task table, you can dynamically select the fields to configure the action. Defining the Parent field associates the task to a parent record.
Delete Multiple Records step -- Look up and delete multiple existing records as a single operation. This Workflow Studio step removes the need to first look up a list of records and then delete each record in the list.
JDBC step -- Create a reusable action to send SQL commands to a relational database.
Test -- Test the JDBC step before testing or publishing an action that contains the JDBC step.
JSON Builder step -- Create a JSON payload to use in another step. Enter values or use data pills to produce a dynamic payload. This step supports several data types, including objects and arrays for nested structures.
Kafka Producer step -- Create an action that publishes events to a topic in your Kafka environment.
Log step -- Logs a message in the Workflow Studio log table sys_flow_log.
Look Up Record step -- Look up a record from any table based on defined conditions.
Look Up Records step -- Look up multiple records on any table using defined conditions.
Map and Transform Data step -- Map complex nested JSON objects to a target schema with dynamic field creation and data transformation.
Notification step -- Trigger a notification as a step within an action by selecting a record (such as an incident, change request, problem, or user record) to trigger a notification and defining the associated notification.
Payload Builder step -- Enable action designers to easily create name-value pairs in JSON and XML payloads using dynamic data.
PowerShell step -- Run PowerShell scripts on remote machines from your ServiceNow instance through a MID Server.
REST step -- Send an outbound REST web service request to an external system.
Script step -- Add custom JavaScript to execute within a reusable action. While most core actions and steps fit common use cases, you can build a Script step to execute behavior not satisfied by the core steps.
Send Email step -- Send an email to specified users or groups as an action in a flow.
SFTP step -- Create a reusable action to manage files and directories on an SFTP server and to move files from one SFTP server to another.
Copy File -- Copies a file from the source SFTP server to target SFTP server.
Copy Directory -- Copies a directory from the source SFTP server to the target SFTP server.
Copy Files To This Instance -- Attaches the specified files in the SFTP server to the specified record in ServiceNow instance.
SSH step -- The SSH step executes SSH commands on an external nix system through a ServiceNow MID Server. The step also stores scripts and commands for the nix systems.
SOAP step -- Enable action designers to send outbound SOAP web service requests to external systems.
Update Multiple Records step -- Look up and update multiple records as a single step. Using this step removes the need to separately look up a list of records and then process the list with a Script step. Set field values with a template or add and configure them using data pills.
Update Record step -- Update an existing record in a table. You can dynamically add and configure fields for the record, or use a template to set field values.
Wait For Condition step -- Pause an action until record values match a specific set of conditions.
ZIP step -- Manage the attachments in a record by performing archive operations such as zip and unzip. You can also view the details of a zipped file.
Zip operation -- Compress one or more record attachments into a single zip archive. You can also manage the contents of a zip archive by removing specific attachments from the zipped file.
Unzip operation -- Extract one or more compressed attachments from a zip archive. You can extract all the compressed attachments in an archive or choose specific attachments to unzip.
Supported input data types for conversational subflows and actions -- Conversational subflows and actions support a limited number of input data types. To be compatible with conversational interfaces, an action or a subflow must only include inputs that use supported data types.
Transform functions -- Transform data pill values without the need to write a script. Use transform functions to reformat text, perform mathematical calculations, sanitize potentially unsafe SQL statements, and serialize complex objects to raw XML.
Date and time -- Use date and time transform functions to recalculate or reformat data pills for Date/Time values.
String -- Use string transform functions to reformat or perform calculations on String data pills.
Utilities -- Use utilities transform functions to return a Complex Object from an Array, or a value associated with a specific key.
Simple math -- Use simple math transform functions to perform basic mathematical calculations on Number data pills.
Sanitize shell arguments -- Use sanitize shell arguments transform functions to remove any potentially unsafe command injections in String data pills to be used for Bash shell scripting.
Sanitize SQL -- Use sanitize SQL transform functions to escape special characters and prevent injection in String data pills to be used for SQL statements.
Complex data -- Use complex data transform functions to serialize Complex Object data pills into an XML format.
Decision tables -- Create and maintain decision logic in a table rather than in code.
Decision tables -- Decision tables in Workflow Studio enable developers to decouple decision logic from their code by creating and maintaining decision rules.
Decision tables workflow -- Learn how to create and maintain decision tables in Workflow Studio for use in flows, subflows, playbooks, and anywhere on the ServiceNow AI Platform where you write code.
Filter decision tables -- Apply filters to both condition and result columns in the Decision Tables in Workflow Studio. Filters can enhance the usability and efficiency of managing large Decision Tables. This feature can be used to view, modify, and reorder a subset of rows directly within the Decision Tables, without exporting the table to Excel.
Decision tables -- Workflow Studio is installed automatically with each family upgrade. By updating to the latest version of Workflow Studio, you have the latest updates to decision tables. Configure Workflow Studio and assign roles to your staff based on the permission level they require.
Decision tables personas and roles -- Workflow Studio is installed automatically with each family upgrade. By updating to the latest version of Workflow Studio, you have the latest updates to decision tables. Configure Workflow Studio and assign roles to your staff based on the permission level they require.
Using decision tables -- Using decision tables in Workflow Studio, you can create, modify, test, and update decision tables for use in your workflows and applications. You can also create decision tables in Workflow Studio and then modify them in Excel.
Create decision tables in Workflow Studio -- Create decision tables in Workflow Studio to embed business logic into a series of if-then decision rules. Use decision tables when business logic is complex or may be reused in multiple places.
Duplicate a decision table -- Save time creating similar decision tables by duplicating existing tables in Workflow Studio.
Edit decision tables using draft authoring -- Edit published decision tables in Workflow Studio when draft authoring is enabled. Without draft authoring enabled, decision tables are active and available to use as soon as they're created.
Define default result values -- Evolve with your business logic by modifying the rows, default result values, or content of your decision table in Workflow Studio.
Modify a decision rule in a decision table -- Evolve with your business logic by modifying the rows, default result values, or content of your decision table in Workflow Studio.
Duplicate rows in a decision table -- Evolve with your business logic by modifying the rows, default result values, or content of your decision table in Workflow Studio.
Reorder decision rows in a decision table -- Evolve with your business logic by modifying the rows, default result values, or content of your decision table in Workflow Studio.
Use decision tables -- Decision tables built in Workflow Studio are executed in flows with flow logic or in scripts with API calls.
Manage decision tables in Excel -- If you have large decision tables to build or want to enhance decision tables outside of the ServiceNow AI Platform, manage them in Excel. Export a decision table to an Excel file, edit the downloaded file to add and edit rows, and then import the file back into Workflow Studio.
Test a decision table in Workflow Studio -- Test your decision table in Workflow Studio before publishing to make sure the rules provide the desired outcome for a given set of input data.
Create decision table code snippets -- Create code snippets of published decision tables in Workflow Studio to execute the decision table from any script and make it easier to replace hard-coded logic with decisions.
Modify Decision Tables in the Classic UI -- Workflow Studio supports decision tables that were created in the classic environment. However, some data types and conditions from the classic environment aren’t fully supported in Workflow Studio. For unsupported field types and decisions with complex conditional logic, use the decision rule view to modify these condition expressions.
Delete a decision table -- Delete decision tables that you no longer need from the list of decision tables in Workflow Studio.
Use enhanced reference record -- View and manage records when referring to other records in the current Decision Tables, without switching to another screen.
Set rows active or inactive -- Activating a row in a Decision Tables includes its conditions and rules when executing the Decision Tables, while deactivating rows excludes the logic while executing the Decision Tables. This feature lets you use or skip conditions in the rows when executing the Decision Tables without deleting them.
Decision tables reference -- Reference topics provide additional information about decision tables properties and administration in Workflow Studio.
Decision Builder system properties -- Use system properties to set limits on the maximum number of inputs and decisions for decision tables created in Decision Builder.
Domain separation and Decision Builder -- This is an overview of domain separation as it pertains to Decision Builder. Domain separation allows you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.
Building spokes using Spoke Generator -- Automate integration tasks by creating a sequence of reusable actions to develop custom integrations called spokes.
Intelligent approvals -- Use AI to automatically evaluate incoming approval requests against your organization's policy documents. Requests that clearly meet policy criteria are approved or rejected automatically, while ambiguous cases are routed to human reviewers for approval.
Explore -- Learn how intelligent approvals automate approval decisions by directly connecting to approval policy documentation.
Configure -- Configure your instance to support intelligent approvals.
Build intelligent approvals -- Intelligent approvals use AI to automate approval decisions based on policy documents you upload and configure. The system analyzes approval requests against your policies and provides automated decisions or recommendations.
Update source document -- Update an existing intelligent approval by uploading a new source document. Regenerate the intelligent approval using the uploaded source document.
Deactivate intelligent approval -- Stop using an intelligent approval to make approval decisions and set its state to inactive.
Create an allowlist configuration -- Manage access to specific tables by specifying the additional user roles necessary to create an intelligent approval on a specific table.
Reference -- Reference topics for intelligent approvals, including the user roles required to access the Intelligent Approvals homepage and create AI-generated approval policies.
Classic approvals -- Classic approvals are a legacy process to require authorization on tasks before the work is done. In earlier releases, you could create approval records to define approval tasks and associate users or groups to approve or reject them.
Approval engines -- The differences in the way that companies handle their approvals, as well as the differences between approvals for the various applications (such as Service Catalog Requests and Change Management), calls for supporting flexibility in setting up approvals within applications.
Set up an approval engine -- To manage the approvals for each of the Task tables in the system, set up an approval engine.
Approval rules -- Many organizations rely on an approval process to ensure that requests are reasonable and fit an organization's budget.
Set automatic approval rules -- Approval rules can automatically set the approval state to something other than Not yet requested. As a result, an approval rule can create a set of approvers. You can also start the approval process by setting the approval state to Requested.
Gating approvals -- A gating approval acts as a gate through which a request must pass before it can start.
Process approvals -- Once a request has passed its gating approvals, any relevant execution plans are initiated.
Approve with a process guide -- Process guides work similarly to approval rules in that their execution is controlled via a condition.
Schematic of a hypothetical approval process -- In the diagram below of a hypothetical approval process, the gating approval is color coded blue and an in-process approval is orange.
Approval summarizer formatter -- The approval summarizer formatter creates the summary at the bottom of an approval form.
Summarizers -- Approval summarizers are stored in the Macro [sys_ui_macro] table.
Create a new custom approval summarizer -- After you add a new table that has approvals to an instance, you can add a custom activity formatter by creating a new UI macro and then add it to the appropriate form.
Approval with e-signature -- Approve or reject an approval record by re-entering your login credentials. See the history of an approval from its activity stream or its audit history.
Activate Approval with e-Signature plugin -- The Approval with e-Signature plugin (com.glide.e_signature_approvals) allows users to approve requests by re-entering their login credentials.
Select an approval table -- By default, activating the Approval with E-signature plugin enables e-signature for all tables for which an approval exists.
Approval status -- The approval status of a change request is determined by looking at the current status of all the approvers.
Generate an approval using approval rules -- The system can automatically generate an approval request to individuals or groups when specific criteria are met. The automatic generation of approval requests is driven using the System Policy feature.
Generate approvals using Workflow flows -- Workflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.
Multiple approvers -- With multiple approvers, all approvers must authorize the request before the status will change to "Approved".
Receive notifications -- Individuals who are designated approvers automatically receive approval notifications, including approval status updates.
Embed an approval request within the Outlook email client -- Embed an interactive approval request for service catalog requests in the email notification sent to a user. The user can accept or reject the approval request from the email client.
Dynamic approval forms -- When you are looking at an approval request, the form has a context-appropriate summary of the item to be approved.
Scripts and engines execution order -- Scripts, assignment rules, business rules, workflows, escalations, and engines all take effect in relation to a database operation, such as insert or update. In many cases, the order of these events is important.
Classic Business rules -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
How business rules work -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Scoping -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Create a business rule -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Global variables -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Controlling field values with business rules -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Using NULL as a field value -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Display rules -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Task Active State Management -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Example scripts -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Compare date fields -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Parse XML payloads -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Abort an action -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Determine the triggering operation -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Use an OR condition -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Reference a Glide list -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Find a Glide list string -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Lock user accounts -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Default before-query -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
System Events -- System Events in ServiceNow are crucial for automating processes and maintaining platform efficiency. They act as triggers for business rules, notifications, work-flows, and other actions, ensuring timely and consistent execution of tasks. By monitoring and responding to these events, organizations can streamline operations, improve response times, and enhance user experiences.
Exploring system events -- Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response.
System Events -- Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response to the conditions.
Event registry -- The events registry lists the events the system recognizes. Use registered events to automate other activities, such as script actions or notifications.
Configuring system events -- Plan, configure, and implement system events without having to complete any extra configurations first. Follow the task listed in the configuration overview to implement automated job scheduling.
Automated scheduling -- Implement the message processing framework (automated jobs scheduling) by using the Queue Registration link on the Event Registration form.
Managing system events -- Managing system events involves creating, monitoring, and handling events to drive automation and streamline processes. Administrators and developers can define custom events, register them in the system, and set up actions or work-flows that respond to these events. This functionality helps ensure efficient task execution, helps improve system monitoring, and enables more robust error handling for enhanced operational reliability.
Create event -- If you do not find a suitable existing event, you can create your own.
Move event -- Accelerate the execution process by moving high priority events from the default queue to an isolated queue.
Passing event parameters -- Pass two event parameters that send information about a record or related records from a work-flow to a notification.
Register event -- You can register an event for a specific table and a business rule that fires the event.
Reprocess event -- You can fire the event again for testing or diagnostic purposes.
Event logs -- The event log records all system events that occur within the ServiceNow AI Platform.
Event states -- The event state describes where in the life cycle the event is.
Incident events -- The incident events business rule comes with the system and defines a number of events that can be triggered by different actions in the Incident table.
Global events -- Your instance has a global function called global_events() that triggers from a business rule when certain conditions occur.
Script actions -- You can use script actions to create server-side scripts that perform a variety of tasks, such as modifying a configuration item (CI), or managing failed login attempts. Script actions are triggered by events only.
Service Creator -- Service creator enables a department to offer custom services through the service catalog, such as the HR department offering tuition reimbursement for further education.
Service creator process -- The service creator process involves requesting and publishing a service category, designating editors and service fulfillers, creating and publishing services, and submitting and fulfilling service requests.
Activate Service Creator -- If the Service Creator plugin is not already activated, an administrator can activate it to access the application.
Components created with new service categories -- When you publish a new service category using the Service Creator application, the ServiceNow system creates components for the services in that category.
Manage a service -- Using the Service Creator, department managers can request a new service category, designate editors and service fulfillers for that category, and create and publish services.
Designing services -- Service creator includes an interface for designing services.
Notification configurations -- All service categories start with a set of associated notifications, such as the notification when a task to fulfill a service request is assigned.
Create the category and table -- After the request has been submitted, a catalog administrator can approve or reject the request.
Delete a template notification -- Deleting a template notification prevents new service categories from using the notification, but does not delete notifications for service categories that have already been created.
Designate an editor -- Editors can create and modify services within a service category.
Publish a service -- A service must be published to appear in the service catalog. When first created, new services appear in the Draft Services related list for the service category. Published services appear in the Services related list for the service category. The manager of a service category can publish draft services.
Classic Workflow -- Workflow is a legacy application that provided 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 graphical Workflow Editor represents workflows visually as a type of flowchart. It shows activities as boxes labeled with information about that activity and transitions from one activity to the next as lines connecting the boxes.
Getting started with workflows -- The graphical Workflow Editor provides a drag-and-drop interface for automating multi-step processes across the platform.
Workflow editor -- The Workflow Editor is an interface for creating and modifying workflows by arranging and connecting activities to drive processes.
Workflow palette -- The default workflow palette contains workflow activities and existing workflows you can use as subflows.
Workflow editor title bar -- When a workflow is opened in the canvas, the title bar displays the workflow title and the workflow status in italics. Possible states are Checked out by and Published.
Workflow editor keyboard navigation -- The platform includes accessibility features that makes the interface accessible to users with disabilities.
Workflow management -- Create, edit, validate, and publish workflows to automate multi-step processes across the platform. Understand workflow activities and variables and how to use them effectively. Take a deeper look at how workflows are constructed, validated, and used.
Create a workflow -- Automate a multi-step process by creating a workflow with the Workflow Editor.
Workflow properties -- In the properties of a workflow, you can configure settings such as its application scope, start conditions, schedule, inputs, stages, and run time metrics. You can also view information such as the workflow author, version, and history.
Create a workflow from a table -- Automate a multi-step process by creating a workflow from the list view of any table that supports workflows.
Ending workflows with multiple branches -- A workflow is complete when it reaches the End activity, even if there are still active branches of the workflow in progress. To ensure that both branches are completed, add a Join activity to resolve the branches.
Work on workflows -- To complete a workflow, you add workflow activities, validate the workflow, and publish it.
Add a workflow activity -- To complete a workflow, you add workflow activities, validate the workflow, and publish it.
Validate a workflow -- To complete a workflow, you add workflow activities, validate the workflow, and publish it.
Publish a workflow -- To complete a workflow, you add workflow activities, validate the workflow, and publish it.
Prepare a subflow -- Review the process of preparing a subflow for use in a parent workflow, and for preparing the parent workflow to use a subflow.
Prepare a workflow to use a subflow -- Review the process of preparing a subflow for use in a parent workflow, and for preparing the parent workflow to use a subflow.
Current variables -- Within workflow there are several different types of variables that are available.
Workflow catalog variables -- Workflows that are associated with the Requested Item [sc_req_item] table have a specific type of workflow input.
Declaration -- Workflows that are associated with the Requested Item [sc_req_item] table have a specific type of workflow input.
Global variable declaration option 2 -- Workflows that are associated with the Requested Item [sc_req_item] table have a specific type of workflow input.
Translate workflow stages -- You can add default stages to use for a table, and stages to existing workflow
Workflow stage sets -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Create a new stage set -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Use a default stage set -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Import stages from a choice list -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Export a stage set from a workflow -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Add a stage set to a workflow -- Stage sets are named groups of workflow stages commonly used together. Create a stage set and assign it as a default set to any number of tables. You can import the choice list values of a workflow field as stages for a workflow, and export a stage set to create a new one.
Create a workflow stage field -- Workflows can provide a summary of workflow progress by updating any field of the Workflow type. If the field is a workflow field, it displays an icon to indicate the workflow stage progress.
Select a stage field -- A Stage field allows the workflow context to show additional workflow information, such as the stage name and the estimated completion time for an activity.
Display approvers in workflow stage fields -- Enable workflow stage fields to display approvers, change the number of approvers to display, or disable displaying approvers.
Workflow validation -- Workflow validation examines different characteristics of a workflow to locate issues that might prevent the workflow from being published or cause it to fail. The validation report summarizes the results of each separate workflow validation.
Workflow validator -- ServiceNow offers several workflow validators for workflow designers to test their workflows.
ValidateTransitionOut -- The ValidateTransitionOut validator finds activity conditions with no exit transitions.
ValidateTransitionIn -- The ValidateTransitionIn validator finds activities that do not have inbound transitions and cannot execute in the workflow.
ValidateDanglingTransition -- The ValidateDanglingTransition validator finds and reports any transitions that do not terminate on an activity.
ValidateSubflows -- The ValidateSubflows validator detects any workflows included as subflows that are either inactive, deleted, or not available as a published workflow for the current user.
ValidateScriptForCurrentDotUpdate -- The ValidateScriptForCurrentDotUpdate validator finds workflow activities with scripts that use the current.update() function.
ValidateLowestCommonTable -- The ValidateLowestCommonTable validator reports the lowest table in the Glide hierarchy that the workflow uses.
ValidateTableChange -- The ValidateTableChange validator reports any activities in the workflow that are invalid given the table associated with the workflow version.
ValidateParentFlow -- The ValidateParentFlow validator reports any workflows that use the workflow as a subflow.
ValidateSingleEnd -- The ValidateSingleEnd validator finds and identifies multiple End activities in a single workflow.
ValidateUpdateSetDependencies -- The ValidateUpdateSetDependencies validator identifies all the subflows called in the current workflow and determines if any of those subflows are being edited in a different (in progress) update set.
ValidateUpdateSetParentDependencies -- The ValidateUpdateSetParentDependencies validator identifies all the workflows that call the current workflow as a subflow and determines if any of those parent workflows are being edited in a different update set that is in progress.
ValidateInputVarUpdateSetDependencies -- The ValidateInputVarUpdateSetDependencies validator examines update sets to ensure that workflow input variables for a given workflow have not been deleted in different update sets than those currently In progress.
ValidateWorkflowEndStages -- The ValidateWorkflowEndStages validator checks that in workflows with stages, the end activity of the workflow has a stage named Complete or Completed.
ValidateWorkflowStageColumn -- The ValidateWorkflowStageColumn validator detects and reports when the stage field (stage column) for a workflow is not correct or is unusable.
ValidateWorkflowStateValues -- The ValidateWorkflowStateValues validator checks a number of stage aspects in workflow activities for correctness.
Workflow concepts -- You can do many things using the Workflow Editor.
Workflow versions -- To prevent users from making changes to a workflow that affect other users of the system, workflows must be checked out before they can be edited.
Workflow scope -- Workflow application scope determines the access that an application has to the information in a workflow, specifically to the data contained in the activities in that workflow.
Workflow scope restrictions -- Workflow application scope determines the access that an application has to the information in a workflow, specifically to the data contained in the activities in that workflow.
Domain separation and Workflow -- Domain separation is supported in the Workflow application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Workflows and delegated administration -- Domain separation is supported in the Workflow application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Workflow permissions -- Domain separation is supported in the Workflow application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Workflows and data separation -- Data separation restricts workflow contexts to users who are either in the same domain of the workflow or are members of a parent domain.
Workflow engine operation order -- The workflow engine runs in a predefined order relative to business rules and database operations. It caches commonly-used published workflows to improve performance.
Workflow caching -- The workflow engine runs in a predefined order relative to business rules and database operations. It caches commonly-used published workflows to improve performance.
Workflow tables -- For full flexibility, workflows store information over a number of different tables.
Workflow roles -- Certain roles are required to use workflows.
Administering workflow contexts -- The workflow context performs the activities and transitions defined in the workflow with the new record as current.
Cancel a workflow -- Canceling a workflow stops the workflow from executing and sets the workflow context State to Canceled. To cancel an executing workflow, you can use the cancelContext(context) script. You can define an onCancel script to clean up unresolved workflow activities.
Cancel a workflow with the cancelContext(context) script -- Canceling a workflow stops the workflow from executing and sets the workflow context State to Canceled. To cancel an executing workflow, you can use the cancelContext(context) script. You can define an onCancel script to clean up unresolved workflow activities.
Define an on-cancel script -- Canceling a workflow stops the workflow from executing and sets the workflow context State to Canceled. To cancel an executing workflow, you can use the cancelContext(context) script. You can define an onCancel script to clean up unresolved workflow activities.
Scheduling a workflow -- In addition to being run based on conditions, workflows can also be scheduled to perform at a particular time, similar to a scheduled job.
Workflow movement with update sets -- The system tracks workflows in update sets differently than other records because workflow information is stored across multiple tables.
Input variable removal -- Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set.
Input variable removal risk -- Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set.
Input variable removal solution -- Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set.
Input variable removal prevention -- Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set.
Avoiding duplicate workflows -- Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.
Commit a workflow in an update set -- Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.
Update set migration example -- Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.
Update set migration risk -- Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.
Workflow timelines -- The system provides a timeline view of history activities associated with a workflow context.
Use a timeline -- The system provides a timeline view of history activities associated with a workflow context.
Timeline for a selected activity -- The system provides a timeline view of history activities associated with a workflow context.
Workflow error handling -- The personalized JavaScript that users create in workflow activity variables is vulnerable to run-time syntax errors. Available error information is available in a tooltip when you point to a workflow activity in an error state.
Workflow error tracking features -- Error handling provides visual cues within the workflow, such as error descriptions for activities in pop-ups, and detailed log records.
Create an error condition exit -- An administrator can reroute the workflow when a script error occurs by creating an error condition exit for specific activities within the workflow. This allows the workflow to process script errors in a predictable way and not create undesirable results.
Workflow run time metrics -- You can enable the collection of workflow run time metrics to determine whether workflows are performing as expected or consuming additional resources.
Enable workflow run time metrics -- You can enable the collection of workflow run time metrics to determine whether workflows are performing as expected or consuming additional resources.
Outlying workflow run times -- You can enable the collection of workflow run time metrics to determine whether workflows are performing as expected or consuming additional resources.
Workflow estimated run time updates -- You can enable the collection of workflow run time metrics to determine whether workflows are performing as expected or consuming additional resources.
Workflow pause utility -- Workflow Pause Utility provides functionality you can use to pause or resume all workflow contexts, a subset of qualified workflow contexts, or individual workflow contexts. You designate the data and time of day at which the paused workflows should resume, and can manually resume individual workflows as needed.
Request workflow pause utility -- You can request the Workflow Pause Utility plugin (com.glideapp.workflow.pause) if you have the admin role. This plugin may include demo data and activates related plugins if they are not already active.
Pause and resume individual workflows -- Pause individual workflow contexts. Specify the date and time of day at which the workflow context should resume.
Pause and resume all or multiple workflows -- Use Workflow Pause Group Requests to pause, or resume, groups of workflows, or all active workflows. If pausing a group of workflows, use filtering functions to select the workflows. If pausing all active workflows, select the Pause All check box to indicate that all currently active workflows should be paused.
Encrypted workflow scratchpad -- The Encrypted Workflow Scratchpad plugin (com.snc.encrypted.scratchpad) provides encrypted scratchpad support for workflow context and workflow executing activities.
Request encrypted workflow scratchpad activation -- The Encrypted Workflow Scratchpad plugin (com.snc.encrypted.scratchpad) provides encrypted scratchpad support for workflow context and workflow executing activities.
Troubleshoot workflows -- Troubleshooting tools for workflows enable administrators to isolate execution paths, compare contexts, and track incomplete activities.
Execution path troubleshooting in timelines -- Troubleshooting tools for workflows enable administrators to isolate execution paths, compare contexts, and track incomplete activities.
Execution history table -- Troubleshooting tools for workflows enable administrators to isolate execution paths, compare contexts, and track incomplete activities.
Use the Workflow Operations Dashboard -- On the Workflow Operations Dashboard, view and add widgets to help you monitor workflows. Review the performance of workflows and determine which workflows must be improved.
Workflow gauges -- On the Workflow Operations Dashboard, view and add widgets to help you monitor workflows. Review the performance of workflows and determine which workflows must be improved.
Workflow performance timing -- The workflow engine can generate detailed performance timing data that is useful for troubleshooting slow workflows.
Workflow estimated run time properties -- The workflow engine can generate detailed performance timing data that is useful for troubleshooting slow workflows.
Enable workflow performance timing -- The workflow engine can generate detailed performance timing data that is useful for troubleshooting slow workflows.
Approval Coordinator workflow activity -- The Approval Coordinator activity creates an approval whose outcome depends on the outcome of one or more child activities, including one or more Approval - User, Approval - Group, and/or Manual Approval activities.
Generate workflow activity -- The Generate activity immediately creates task or approval records from any task or approval activities placed after the Generate activity in the workflow path. These pre-generated tasks and approvals start when the task and approval activities are reached during flow execution. This allows a task to have a set of associated pre-generated sequential tasks or approvals, but still require them to be completed in order.
Manual Approvals workflow activity -- The Manual Approvals activity watches and manages any approvals that users add manually outside of the workflow process. This activity only selects approvals that are in the Not requested state.
Rollback To workflow activity -- The Rollback To activity transitions directly to the activity specified by the outgoing transition line arrow.
Rollback To behavior -- The Rollback To activity transitions directly to the activity specified by the outgoing transition line arrow.
Rollback To activity -- The Rollback To activity transitions directly to the activity specified by the outgoing transition line arrow.
Condition Workflow activities -- Condition activities provide conditional branching and logical operation functionality for workflows.
If workflow activity -- The If activity checks a condition or script to determine if a Yes or No transition should be taken.
Switch workflow activity -- The Switch activity checks if the value of a passed field or variable is equivalent to one of several case values.
Wait for condition workflow activity -- The Wait for condition activity causes the workflow to wait at this activity until the current record matches the specified condition.
Wait for WF Event workflow activity -- The Wait for WF Event activity causes the workflow to wait at this activity until the specified event is fired.
REST Message legacy workflow activity -- The legacy REST Message activity enables an administrator to override the REST endpoint or supply the variables configured in the REST Message module.
Return Value workflow activity -- The Return Value activity returns a value to a parent workflow, when run from a subflow.
Run Script workflow activity -- The Run Script activity runs the specified script in the scope of the workflow version.
Set Values workflow activity -- The Set Values activity sets values on the current record when the workflow quiesces or ends.
SOAP Message legacy workflow activity -- The legacy SOAP Message activity uses SOAP messages defined in the System Web Services plugin and can call the messages using a MID Server.
Turnstile workflow activity -- The Turnstile activity limits how many times a workflow can pass through the same point.
Unlock workflow activity -- The Unlock activity releases a lock that was previously placed by the Lock activity.
Parallel Flow Launcher example -- This example shows how to use the Parallel Flow Launcheractivity with an array of input values and with a WorkflowCoordinator object.
Using workflow approval activities and rolling back workflows -- When you work with approvals, you need to understand how approval activities interact with approval engines, how to correct a skipped approval workflow activity, and how rollbacks work.
Approval workflow activities and approval engines -- When you work with approvals, you need to understand how approval activities interact with approval engines, how to correct a skipped approval workflow activity, and how rollbacks work.
Correct a skipped workflow approval activity -- When you work with approvals, you need to understand how approval activities interact with approval engines, how to correct a skipped approval workflow activity, and how rollbacks work.
Publish a custom workflow activity -- When a user creates a custom activity and saves or submits it, that activity appears in the Custom and Packs tabs of the designer palette, but is only visible to the user who created it.
Workflow activity pinning -- Workflow administrators can pin a custom activity to prevent the system from automatically updating that activity when a new version is downloaded from the ServiceNow Store.
Create a business rule -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Create a business rule -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Create a business rule -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Create a business rule -- A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.