Testing a running event-driven flow

After you start an event-driven flow in your App Connect Designer instance, you can verify its behavior by performing the event activity that triggers the flow and then checking for the expected results in the UI of the target applications.

Tip: While developing a flow, you can also test (or try out) the flow or individual actions before you start the flow. For more information, see Testing a non-running flow with sample data.

Before you begin

You must have created a flow by using one of the methods for creating flows, and then started the flow.

Procedure

To test a running flow in your App Connect Designer instance, complete the following steps:

  1. In the source application, perform the event activity that triggers the flow.

    For example, to trigger the following flow you'd create a contact in the Salesforce instance that is linked to Account 1.

    Sample flow for testing
    Tip:
    • To test a flow without using production accounts for applications, you can temporarily select preconfigured test accounts on the event and actions in the flow.
    • To test the sequence of actions in a flow without performing the event activity on the target applications (or waiting a long time for a Scheduler event to occur), you can temporarily replace the event in the flow with a Scheduler event that is configured to trigger the flow when it is first started (by selecting the Also run the flow when it's first switched on check box).
  2. Check the target applications to verify that you can see the expected results. For example, you can check your Asana instance to verify that a task was created for processing actions related to the new Salesforce contact.

    If the flow is triggered by streamed events, actions on applications should be completed soon after the flow is triggered. If the flow is triggered by polled events or the Scheduler, actions on applications should be completed according to the configured schedule.