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 architecture

    Process Automation Designer architecture

    • 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 architecture

    Understand how Process Automation Designer works in the Now Platform® to automate cross-functional processes and consolidate them into task-oriented views for your end users.

    Process Automation Designer consists of a design time environment that lets you produce a runtime view of a record's life cycle. The design time environment is a space where process owners can create process definitions. Meanwhile, the runtime experience is where end users, such as Workspace agents, follow the process to complete records.

    Design time environment

    The Process Automation Designer design time environment consists of these components:

    Process definitions
    A process definition is where a process owner configures and organizes multiple instances of Flow Designer content into a coherent business process. A process definition consists of a trigger, a sequence of lanes, and a sequence of activities.
    Trigger definitions
    A trigger definition specifies the conditions that must be met to run a process definition. A user with the admin, pd_admin, or pd_trigger_author role typically creates and configures a trigger definition that process authors can use as a template. A trigger definition specifies the record operation and table conditions that must be met to start running a process definition. A process owner typically selects a trigger template when creating a process definition.
    Trigger instances
    A trigger instance is produced when you select a trigger template. The trigger instance stores the conditions that a record must meet to start running the process.
    Lanes
    A lane is a logical grouping of activities in a process definition. A process owner creates a lane to group activities and specify the start rule for when the lane should start running. A lane represents one stage in your overall business process.
    Activity definitions
    An activity definition maps Flow Designer inputs and outputs to an activity instance. An activity definition contains:
    • The automation plan to map the triggering input record data to action or flow inputs
    • The activity experience to map action or flow outputs to a user-facing view of the process definition

    A user with the admin, pd_admin, or pd_content_author roles typically specifies the automation plan and activity experience when creating an activity definition.

    Activity instances
    An activity instance is produced when you add an activity to a process definition. The activity instance stores the automation plan data mappings from the activity definition. You can change these data mappings when the default values do not fit your process. The process can specify the start rules for when the activity should start running.
    Start rules
    A start rule specifies when a lane or an activity starts running. A process owner can use start rules to specify what parts of a process run simultaneously and what parts run serially.
    For more information about how to use and navigate the Process Automation Designer user interface, see Exploring Process Automation Designer.

    Runtime experience

    Process Automation Designer produces these runtime components:

    Process executions
    A process execution stores the details of running a process definition in a context record. You can use a process execution to troubleshoot and verify that process definitions run as expected.
    Activity executions
    An activity execution stores the details of running an activity instance in a context record. You can use an activity execution to troubleshoot and verify that process definitions run as expected.
    User-facing views
    A user-facing view is a user interface that displays the output or results of a process definition, such as a playbook. A workspace administrator can specify a user-facing view as part of setting up a playbook experience. See Set up a playbook.
    During runtime for a process definition, your instance:
    1. Evaluates any conditions specified in the trigger definition and processes the trigger.
    2. Processes the event and starts running the process definition in the background.
    3. Builds the automation plans from each activity into an entire process plan.
    4. Runs the process plan for your process definition.
    5. Stores the process execution information in the Process Execution [sys_pd_context] table.
    6. Supplies data for a user-facing view of your process execution.
    Your instance processes a process definition during runtime by evaluating trigger conditions, processing the event in the queue, building and running a process plan, storing process execution details, and providing data for a user-facing view.
    • Exploring Process Automation Designer

      Get an overview of the Process Automation Designer landing page and design environment.

    • Process Automation Designer system properties

      Review the system properties for Process Automation Designer. You can configure these properties to control how the system handles Process Automation Designer events.

    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 architecture

      • 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 architecture

      Understand how Process Automation Designer works in the Now Platform® to automate cross-functional processes and consolidate them into task-oriented views for your end users.

      Process Automation Designer consists of a design time environment that lets you produce a runtime view of a record's life cycle. The design time environment is a space where process owners can create process definitions. Meanwhile, the runtime experience is where end users, such as Workspace agents, follow the process to complete records.

      Design time environment

      The Process Automation Designer design time environment consists of these components:

      Process definitions
      A process definition is where a process owner configures and organizes multiple instances of Flow Designer content into a coherent business process. A process definition consists of a trigger, a sequence of lanes, and a sequence of activities.
      Trigger definitions
      A trigger definition specifies the conditions that must be met to run a process definition. A user with the admin, pd_admin, or pd_trigger_author role typically creates and configures a trigger definition that process authors can use as a template. A trigger definition specifies the record operation and table conditions that must be met to start running a process definition. A process owner typically selects a trigger template when creating a process definition.
      Trigger instances
      A trigger instance is produced when you select a trigger template. The trigger instance stores the conditions that a record must meet to start running the process.
      Lanes
      A lane is a logical grouping of activities in a process definition. A process owner creates a lane to group activities and specify the start rule for when the lane should start running. A lane represents one stage in your overall business process.
      Activity definitions
      An activity definition maps Flow Designer inputs and outputs to an activity instance. An activity definition contains:
      • The automation plan to map the triggering input record data to action or flow inputs
      • The activity experience to map action or flow outputs to a user-facing view of the process definition

      A user with the admin, pd_admin, or pd_content_author roles typically specifies the automation plan and activity experience when creating an activity definition.

      Activity instances
      An activity instance is produced when you add an activity to a process definition. The activity instance stores the automation plan data mappings from the activity definition. You can change these data mappings when the default values do not fit your process. The process can specify the start rules for when the activity should start running.
      Start rules
      A start rule specifies when a lane or an activity starts running. A process owner can use start rules to specify what parts of a process run simultaneously and what parts run serially.
      For more information about how to use and navigate the Process Automation Designer user interface, see Exploring Process Automation Designer.

      Runtime experience

      Process Automation Designer produces these runtime components:

      Process executions
      A process execution stores the details of running a process definition in a context record. You can use a process execution to troubleshoot and verify that process definitions run as expected.
      Activity executions
      An activity execution stores the details of running an activity instance in a context record. You can use an activity execution to troubleshoot and verify that process definitions run as expected.
      User-facing views
      A user-facing view is a user interface that displays the output or results of a process definition, such as a playbook. A workspace administrator can specify a user-facing view as part of setting up a playbook experience. See Set up a playbook.
      During runtime for a process definition, your instance:
      1. Evaluates any conditions specified in the trigger definition and processes the trigger.
      2. Processes the event and starts running the process definition in the background.
      3. Builds the automation plans from each activity into an entire process plan.
      4. Runs the process plan for your process definition.
      5. Stores the process execution information in the Process Execution [sys_pd_context] table.
      6. Supplies data for a user-facing view of your process execution.
      Your instance processes a process definition during runtime by evaluating trigger conditions, processing the event in the queue, building and running a process plan, storing process execution details, and providing data for a user-facing view.
      • Exploring Process Automation Designer

        Get an overview of the Process Automation Designer landing page and design environment.

      • Process Automation Designer system properties

        Review the system properties for Process Automation Designer. You can configure these properties to control how the system handles Process Automation Designer events.

      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