{"id":29847,"date":"2021-08-13T13:30:43","date_gmt":"2021-08-13T12:30:43","guid":{"rendered":"https:\/\/multisite.korebots.com\/v9-0\/?p=29847"},"modified":"2021-08-13T18:37:03","modified_gmt":"2021-08-13T17:37:03","slug":"simulate","status":"publish","type":"post","link":"https:\/\/multisite.korebots.com\/v9-0\/docs\/process-apps\/simulate\/","title":{"rendered":"Simulate"},"content":{"rendered":"<section class=\"l-section wpb_row height_auto\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row via_grid cols_1 laptops-cols_inherit tablets-cols_inherit mobiles-cols_1 valign_top type_default stacking_default\"><div class=\"wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>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.<\/p>\n<\/div><\/div><div class=\"w-separator size_medium with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><h4><strong>Simulate Process App<\/strong><\/h4>\n<p>To simulate your Process App, follow the below steps:<\/p>\n<ol>\n<li>On the Flow page, click <strong>Simulator<\/strong> on the top-right.<\/li>\n<li>On the Simulations window, you can find the <strong>Running<\/strong> and <strong>Completed<\/strong> tabs that display the <em>in-progress<\/em> and <em>completed<\/em> simulations.<\/li>\n<li>Click <strong>+Simulation<\/strong>.<\/li>\n<li>On the Simulations window, you can find triggers. Select a trigger to test the workflow.\n<ol>\n<li>If the trigger type is a <strong>Form<\/strong>, the system opens up the form for you to submit.<\/li>\n<li>If the trigger type is<strong> Callable<\/strong>, the system displays all the process apps that have <em>Call a Subflow<\/em> task and are associated with the current process app.\n<ul>\n<li>Parent process apps are displayed.\n<ol>\n<li>Select a parent process app to execute. On selection, the system displays the triggers applicable for the parent process app.<\/li>\n<li>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.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<li>If the trigger type is <strong>Scheduled<\/strong>, the system allows you to schedule the process app execution.\n<ol>\n<li>On the property panel, you can enter the input to trigger.<\/li>\n<li>Enter the <strong>limit<\/strong> for the process app execution and based on the input, the scheduled trigger execution occurs.<\/li>\n<\/ol>\n<\/li>\n<li>If the trigger type is <strong>Conversational<\/strong>, you can select the bot to trigger the process app.\u00a0 Then, click <strong>Trigger<\/strong> to trigger the process app.<\/li>\n<li>If the trigger type is <strong>Webhook<\/strong>, the system displays a text message against each trigger as shown below:\n<ol>\n<li><strong>Webhook Trigger <\/strong>&#8211; The system displays a text stating <em>Please do a post-call to the endpoint URL, and if posted successfully, check the execution status under simulator instances.<\/em><\/li>\n<li>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.<\/li>\n<\/ol>\n<\/li>\n<li>If the trigger type is <strong>Email<\/strong>, the system displays the below details to trigger a process app:\n<ul>\n<li><strong>From Address<\/strong> &#8211; It uses the default platform email setup to send the email to the process app email address.<\/li>\n<li><strong>To Address<\/strong> &#8211; This will default to the trigger email address of the process application<\/li>\n<li><strong>Subject\u00a0<\/strong><\/li>\n<li><strong>Compose message\u00a0<\/strong><\/li>\n<li><strong>Trigger\u00a0<\/strong><\/li>\n<li><strong>Email<\/strong> &#8211; An email is sent successfully message is displayed on success. If failed, it displays an error message.<\/li>\n<li>Process app is triggered if the email content matches the trigger definition.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/li>\n<li>Click <strong>Exit Simulator<\/strong> to exit the simulation process.<\/li>\n<\/ol>\n<\/div><\/div><div class=\"w-separator size_medium with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><h4><strong>Simulator Instances Information<\/strong><\/h4>\n<p>The system displays all the instances that are executed for the process app. It also displays the previous 3 days process apps that are simulated to go back and check details of the instance that got stimulated. You can find the following information:<\/p>\n<ol>\n<li>Instance Initiation Date &amp; Time<\/li>\n<li>Trigger Type<\/li>\n<li>Debug Logs\n<ol>\n<li>Nodes transitions are displayed against each instance\n<ol>\n<li>Execution started<\/li>\n<li>Execution successful<\/li>\n<li>Step Failed<\/li>\n<li>Date and time to be displayed as well for the node<\/li>\n<\/ol>\n<\/li>\n<li>Context data<\/li>\n<\/ol>\n<\/li>\n<li>Current Step<\/li>\n<li>Instance Execution Status\n<ol>\n<li>In Progress<\/li>\n<li>Failed<\/li>\n<li>Completed<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/div><\/div><div class=\"w-separator size_medium with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"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: On the Flow page, click...","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[141],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/posts\/29847"}],"collection":[{"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/comments?post=29847"}],"version-history":[{"count":10,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/posts\/29847\/revisions"}],"predecessor-version":[{"id":29870,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/posts\/29847\/revisions\/29870"}],"wp:attachment":[{"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/media?parent=29847"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/categories?post=29847"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/multisite.korebots.com\/v9-0\/wp-json\/wp\/v2\/tags?post=29847"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}