Using the Interaction Manager

Article Overview

The following article describes how to use the Interaction Manager.

Structure Overview

(See Figure 1)

As described in a previous article, The Interaction Manager is divided into two main sections, Process Building (1) and the work area (2). 

Figure 1: Interaction Manager Structure

Adding Building Blocks to the Work Area

(See Figure 2)

Building blocks are added to the work area by drag and drop. After a building block is placed in the work area its properties appear on the left (1) and it displays additional buttons:

• Delete(2)
• Open(3) - enables you to open a specific area in the Builder platform such as the Webflow
• Copy (4)

When a building block has an empty required property it will display a red frame (5). 

Figure 2: Process Building

Connecting Building Blocks

(See Figure 3 and Figure 4)

To map a process and create detailed visualizations to understand the relationship between building blocks better, we need to establish connections. Each building block has at least one connection point (1), for example: 

Figure 3: Building Block Connecting Points

To establish a connection between building blocks, hover over a connection point and wait for the icon to appear. Then, with the left click, pull a connecting line toward the next building block and attach it to a connection point.

Figure 4: Connected Building Blocks

Arrow Direction and Data Flow

When connecting building blocks, the direction of the arrows signifies the flow of data between them. Using the wrong direction can cause errors and prevent data from being auto-filled or processed correctly. In the following example, the data flow starts with the Create Webflow Link building block to the Webflow building block. This is the accurate way to connect the two building blocks. When clicking the Webflow building block to display its properties, the Linked to and Role properties are automatically filled.    

Figure 5: Connected Building Blocks and Data Flow 1 of 2

The wrong way to connect between the two building blocks is to connect them from the Webflow to the Create Webflow Link.
This will cause the Webflow properties to remain empty and display an error indication (red frame) around the Webflow building block.

Figure 6: Connected Building Blocks and Data Flow 2 of 2

Guidelines

Follow these guidelines when adding and connecting building blocks:

• Before using the Interaction Manager, perform a specification process as described in the Specification Process article
• Every process starts with the Start building block located under the Business Logic category
• A process can have more than one Start building block

Figure 5: Start Building Block

• Connect a Start building block to one of the other building blocks, according to the scenario of your workflow, for example:

1. The end-user accesses a portal and clicks a link
2. The end-user clicks the link in the email to access the process 

• Portal -> Webflow

Figure 6: Workflow Example 1 of 4

1. An agent accesses Salesforce
2. Inside Salesforce, the agent displays a list of EasySend processes
3. The agent generates a new process link
4. The link is sent via email
5. The end-user clicks the link in the email to access the process

• Salesforce -> Integration -> Create Webflow Link -> Email -> Webflow

Figure 7: Workflow Example 2 of 4

1. A customer receives a direct link to a process
2. The end-user clicks the link to access the process

• Direct Link -> Webflow

Figure 8: Workflow Example 3 of 4

1. An API generates a link and sends it to an end-user via integration
2. An email is sent to the end-user
3. The end-user clicks the link in the SMS to access the process

• API -> Integration -> SMS -> Webflow

Figure 8: Workflow Example 4 of 4

• Use a condition to logically split the workflow of the process into different paths, for example, a process will either end or continue if a spouse needs to be involved

Figure 9: Using a Condition

• Use an Integration to describe where to send data at each stage of the process, for example:
  • When the agent sends a link of the process through a CRM system to the end-user it is prefilled with data
  • When the end-user submits the process, new information is integrated back into the CRM
  • When the end-user submits the process, all uploaded files are sent to an FTP by using Webhooks

Figure 10: Using Intgrations