GETTING STARTED
Process Assistants Overview
Concepts and Terminology
Quick Start Guide
Exploring the Process Apps Store
Building Process Apps from Scratch
What's New
Current Version

CONCEPTS
Flow Builder
Triggers
Logic
Introduction
Split
Merge
GoTo
End
Tasks
Introduction
Human Task
Script Task
Integrations
Introduction
Connect to Data Table
Connect to API
Events
Call a Subflow
Notify
Delay
Forms
Form Creation
Form Components
Form Actions
Simulate
Publish
Self-Service Portal
Dashboard

SETTINGS
General Settings
Members and Roles
Versioning
Channels
Bot Permissions
Alerts
Import & Export
Change Logs
Delete App

HOW TOs
Creating a Process App
Creating a Process App
Importing and Exporting a Process App
Sharing a Process App with Co-Developers
Configuring a Process App
Defining a Digital Form
Defining a Flow for a Process App
Defining Triggers for a Process App
Using Stencil to Define a Logic for a Process App
Using Events for a Process App
Adding Access Controls to a Digital Form
Calling a Subflow from Process App
Deploying a Process App
Configuring Channels to a Process App
Publishing a Process App
Analyzing a Process App
Stimulating a Process Instance
Creating and Publishing a Process App
Viewing a Process App Errors
Viewing Change Logs Made to Process App Definition
Creating or Restoring a Version of Process App
Adding Bot Permissions to let Bot Trigger the Process App

ADMINISTRATION
Introduction
Assistant Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Assistant Management
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Compliance
Using Single-Sign On
Security Settings
Cloud Connector
Billing
  1. ホーム
  2. Docs
  3. Process Apps
  4. How To Articles
  5. How to Simulate a Process Instance?

How to Simulate a Process Instance?

You can simulate the process app by selecting a trigger. The primary purpose of the simulator is to test the workflow. It displays all triggers applicable to the process app and you can select a trigger to simulate.

Simulate Process App

To simulate your Process App, follow the below steps:

  1. On the Flow page, click Simulator on the top-right.
  2. On the Simulations window, you can find the Running and Completed tabs that display the in-progress and completed simulations.
  3. Click +Simulation.
  4. On the Simulations window, you can find triggers. Select a trigger to test the workflow.
    • If the trigger type is a Form, the system opens up the form for you to submit.
    • If the trigger type is Callable, the system displays all the process apps that have Call a Subflow task and are associated with the current process app.
      • Parent process apps are displayed.
        • Select a parent process app to execute. On selection, the system displays the triggers applicable for the parent process app.
        • Select a trigger, and if the selected trigger is a form, you can submit it from the same screen. Else, a text message is displayed according to the trigger.
    • If the trigger type is Scheduled, the system allows you to schedule the process app execution.
      • On the property panel, you can enter the input to trigger.
      • Enter the limit for the process app execution and based on the input, the scheduled trigger execution occurs.
    • If the trigger type is Conversational, you can select the bot to trigger the process app.  Then, open the chat window in the process app to trigger it.
    • If the trigger type is Webhook, the system displays a text message against each trigger as shown below:
      • Webhook Trigger – The system displays a text stating Please do a post-call to the endpoint URL, and if posted successfully, check the execution status under simulator instances.
      • A help text with payload data is added to notify you if simulated through a webhook. This is added as part of the payload for a simulator instance.
    • If the trigger type is Email, the system displays the below details to trigger a process app:
      • From Address – It uses the default platform email setup to send the email to the process app email address.
      • To Address – This will default to the trigger email address of the process application
      • Subject
      • Compose message
      • Trigger
      • Email – An email is sent successfully message is displayed on success. If failed, it displays an error message.
      • Process app is triggered if the email content matches the trigger definition.
  5. Click Exit Simulator to exit the simulation process.

Simulator Instances Information

The system displays all the instances that you can execute in the process app. It also displays process apps that were simulated previously and allows you to check the details of the stimulated instance. You can find the following information:

  • Instance Initiation Date & Time
  • Trigger Type
  • Debug Logs
  • Nodes transitions displayed against each instance
  • Execution Started
  • Execution Successful
  • Step Failed
  • Date and Time
  • Context Data
  • Current Step
  • Instance Execution Status
  • In Progress
  • Failed
  • Completed
  1. ホーム
  2. Docs
  3. Process Apps
  4. How To Articles
  5. How to Simulate a Process Instance?

How to Simulate a Process Instance?

You can simulate the process app by selecting a trigger. The primary purpose of the simulator is to test the workflow. It displays all triggers applicable to the process app and you can select a trigger to simulate.

Simulate Process App

To simulate your Process App, follow the below steps:

  1. On the Flow page, click Simulator on the top-right.
  2. On the Simulations window, you can find the Running and Completed tabs that display the in-progress and completed simulations.
  3. Click +Simulation.
  4. On the Simulations window, you can find triggers. Select a trigger to test the workflow.
    • If the trigger type is a Form, the system opens up the form for you to submit.
    • If the trigger type is Callable, the system displays all the process apps that have Call a Subflow task and are associated with the current process app.
      • Parent process apps are displayed.
        • Select a parent process app to execute. On selection, the system displays the triggers applicable for the parent process app.
        • Select a trigger, and if the selected trigger is a form, you can submit it from the same screen. Else, a text message is displayed according to the trigger.
    • If the trigger type is Scheduled, the system allows you to schedule the process app execution.
      • On the property panel, you can enter the input to trigger.
      • Enter the limit for the process app execution and based on the input, the scheduled trigger execution occurs.
    • If the trigger type is Conversational, you can select the bot to trigger the process app.  Then, open the chat window in the process app to trigger it.
    • If the trigger type is Webhook, the system displays a text message against each trigger as shown below:
      • Webhook Trigger – The system displays a text stating Please do a post-call to the endpoint URL, and if posted successfully, check the execution status under simulator instances.
      • A help text with payload data is added to notify you if simulated through a webhook. This is added as part of the payload for a simulator instance.
    • If the trigger type is Email, the system displays the below details to trigger a process app:
      • From Address – It uses the default platform email setup to send the email to the process app email address.
      • To Address – This will default to the trigger email address of the process application
      • Subject
      • Compose message
      • Trigger
      • Email – An email is sent successfully message is displayed on success. If failed, it displays an error message.
      • Process app is triggered if the email content matches the trigger definition.
  5. Click Exit Simulator to exit the simulation process.

Simulator Instances Information

The system displays all the instances that you can execute in the process app. It also displays process apps that were simulated previously and allows you to check the details of the stimulated instance. You can find the following information:

  • Instance Initiation Date & Time
  • Trigger Type
  • Debug Logs
  • Nodes transitions displayed against each instance
  • Execution Started
  • Execution Successful
  • Step Failed
  • Date and Time
  • Context Data
  • Current Step
  • Instance Execution Status
  • In Progress
  • Failed
  • Completed
メニュー