Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Paris Now Platform Capabilities Now Platform capabilities Process Automation Designer Process Automation Designer triggers

    Process Automation Designer triggers

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Process Automation Designer triggers

    Process Automation Designer triggers specify when to start running your process.

    In Process Automation Designer, triggers indicate when your process should start running. Each trigger has a type and conditions that, when met, start running your activated process definition.

    You can choose a trigger when you create a process definition in Process Automation Designer. Start by adding a trigger, which defines the trigger type. Then, set conditions and other options to refine your trigger so that it fires in a way that makes sense for your business process. For more information, see Create a process definition.

    If there are no triggers that fit your use case, you can create your own trigger definition instead. For more information, see Create a trigger definition.

    Figure 1. How triggers work
    When the conditions specified in your trigger are met anywhere in the Now Platform, your automated process starts running.

    Trigger types

    In your Trigger Definition [sys_pd_trigger_definition] record, you can choose a trigger type, which determines when your trigger fires. These trigger types represent record operations that can occur in the Now Platform®. The following trigger types are available in your instance by default:

    Record Created
    The process runs when a user creates a record anywhere in the Now Platform.
    Record Updated
    The process runs when a user updates an existing record anywhere in the Now Platform.
    Record Created or Updated
    The process runs when a user creates a record or updates an existing record anywhere in the Now Platform.
    Note: Triggers only fire for record operations that are interactive, or made by users. Triggers don't fire for non-interactive record operations. For more information, see Non-interactive sessions.

    Conditions to run

    After you add a trigger to your process, you can then set conditions and other options that determine when and how your trigger fires.

    Option Action
    Conditions Use the condition builder to create field conditions for when your process runs. See Condition builder.
    Run my process Choose an option for when your process runs. Options include:
    • Once: Triggers the process definition once for the life of the triggering input record.
    • For each unique change: Triggers the process definition for every unique update to a non-system field even if the flow is currently running.
      Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the process definition runs. However, if the State field then changes back to In Progress, the process definition doesn't run.
      Note: Process definitions that have a trigger that runs For each unique change can produce recursions when run in a non-interactive session. When such processes make a change to the trigger record, the change meets the process definition's trigger conditions and causes a recursion.
    • Only if not currently running: Triggers the process definition for every unique change if a process execution is not currently running.
    • For every update: Triggers the process definition every time the input record is updated, regardless of whether there has already been or there currently are any running process executions.
    Run on extended Select this option to trigger the process on tables that extend from your selected table. For example, if you enable this option and select the Configuration Item [cmdb_ci] table, your process runs when record operations occur on the Server [cmdb_ci_server], Computer [cmdb_ci_computer], and other extended tables. For more information, see Table extensions and classes.

    Design considerations

    Refer to these design considerations when working with triggers:
    Create unique filter conditions for record triggers on the same table
    To prevent processes from overwriting each other, create unique filter conditions for each process that runs on the same table. If multiple processes on the same table have the same filter, there is no way to know the order in which the processes will run.
    Avoid duplicating triggers used in Flow Designer flows
    Process Automation Designer triggers do not override Flow Designer triggers. For both applications, when the trigger conditions are met, the automated processes run.
    Ignore records added or updated by import and update sets
    Record triggers ignore records that were added or updated by applying an update set or importing an XML file. These operations apply to the entire application or table instead of an individual record.
    • Create a trigger definition

      Define the type of trigger that determines when to start running your process.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Process Automation Designer triggers

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Process Automation Designer triggers

      Process Automation Designer triggers specify when to start running your process.

      In Process Automation Designer, triggers indicate when your process should start running. Each trigger has a type and conditions that, when met, start running your activated process definition.

      You can choose a trigger when you create a process definition in Process Automation Designer. Start by adding a trigger, which defines the trigger type. Then, set conditions and other options to refine your trigger so that it fires in a way that makes sense for your business process. For more information, see Create a process definition.

      If there are no triggers that fit your use case, you can create your own trigger definition instead. For more information, see Create a trigger definition.

      Figure 1. How triggers work
      When the conditions specified in your trigger are met anywhere in the Now Platform, your automated process starts running.

      Trigger types

      In your Trigger Definition [sys_pd_trigger_definition] record, you can choose a trigger type, which determines when your trigger fires. These trigger types represent record operations that can occur in the Now Platform®. The following trigger types are available in your instance by default:

      Record Created
      The process runs when a user creates a record anywhere in the Now Platform.
      Record Updated
      The process runs when a user updates an existing record anywhere in the Now Platform.
      Record Created or Updated
      The process runs when a user creates a record or updates an existing record anywhere in the Now Platform.
      Note: Triggers only fire for record operations that are interactive, or made by users. Triggers don't fire for non-interactive record operations. For more information, see Non-interactive sessions.

      Conditions to run

      After you add a trigger to your process, you can then set conditions and other options that determine when and how your trigger fires.

      Option Action
      Conditions Use the condition builder to create field conditions for when your process runs. See Condition builder.
      Run my process Choose an option for when your process runs. Options include:
      • Once: Triggers the process definition once for the life of the triggering input record.
      • For each unique change: Triggers the process definition for every unique update to a non-system field even if the flow is currently running.
        Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the process definition runs. However, if the State field then changes back to In Progress, the process definition doesn't run.
        Note: Process definitions that have a trigger that runs For each unique change can produce recursions when run in a non-interactive session. When such processes make a change to the trigger record, the change meets the process definition's trigger conditions and causes a recursion.
      • Only if not currently running: Triggers the process definition for every unique change if a process execution is not currently running.
      • For every update: Triggers the process definition every time the input record is updated, regardless of whether there has already been or there currently are any running process executions.
      Run on extended Select this option to trigger the process on tables that extend from your selected table. For example, if you enable this option and select the Configuration Item [cmdb_ci] table, your process runs when record operations occur on the Server [cmdb_ci_server], Computer [cmdb_ci_computer], and other extended tables. For more information, see Table extensions and classes.

      Design considerations

      Refer to these design considerations when working with triggers:
      Create unique filter conditions for record triggers on the same table
      To prevent processes from overwriting each other, create unique filter conditions for each process that runs on the same table. If multiple processes on the same table have the same filter, there is no way to know the order in which the processes will run.
      Avoid duplicating triggers used in Flow Designer flows
      Process Automation Designer triggers do not override Flow Designer triggers. For both applications, when the trigger conditions are met, the automated processes run.
      Ignore records added or updated by import and update sets
      Record triggers ignore records that were added or updated by applying an update set or importing an XML file. These operations apply to the entire application or table instead of an individual record.
      • Create a trigger definition

        Define the type of trigger that determines when to start running your process.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login