The Run Another App module can be used to direct the caller to another application, and when that application finishes, the original application resumes. This module is particularly useful for when you want to modularize the functionality of your applications. Let's learn how to use this module by creating a new application.

For our example application, we're going to create an application that runs another application, “Get Age”.

First, we're going to start our “Run Another App” application by dragging out a First Name Input module and Last Name Input module to the workspace. Connect the node from your Start module to the receptor on the First Name Input module and connect the node from your First Name Input module to the receptor on the Last Name Input module. Next, drag a Run Another App module to the workspace and connect the node from your Last Name Input module to the receptor on the Run Another App module.

Now, save your application and exit out back to the “My Apps” page. Create another application and name it “Get Age”. Drag out a Reserve Variable module and name the variable, firstName. Drag out a second Reserve Variable module and name the variable, lastName. Next, drag out a Multipart Prompt module to your workspace and connect it to your Start module. In the textbox of the Multipart Prompt module, write the following text: “Your name is”. Click on the ”+” button to add a variable to your Multipart Prompt module and select firstName as your variable. Click on the ”+” button to add another variable to your Multipart Prompt module and select lastName as your variable.

Next, drag out a Digits Input module to your workspace and connect it to your Multipart Prompt module. In the textbox of your Digits Input module, enter the following text: “How old are you now?” Finally, drag out an Exit App module and connect it to your Digits Input module.

Now, let's go back to the “Run Another App” application and finish setting it up. Let's drag out a Reserve Variable module to our workspace and set the variable as age. In the Run Another App module, select “Get Age” from the drop-down menu for application and select ”(use the latest)” as the correct revision. For the Send variables, click on the ”+” button to add another variable and select firstName and lastName as your variables. For the Receive variables, select age as your variable.

Next, drag out a Multipart Prompt module to your workspace and connect it to your Run Another App module. Enter “You are” as the text in the textbox. Click on the ”+” button to add a variable to your module and select age as the variable. Click on the ”+” button again to add a phrase to your module as enter “years old.” as the text. Finally, drag out a Hang Up or Exit module to your workspace and connect it to the Multipart Prompt module.

From this example, the “Run Another App” application first prompts the user to input their first name and last name. Then, the Run Another App module is used to send the variables, firstName and lastName, to the “Get Age” application. In the “Get Age” application, the user is told what they had entered for their first name and last name and then prompted to enter their age. The “Get Age” application then completes and returns to the “Run Another App” application. There, the Run Another App module receives the age variable from the “Get Age” application, which gets used in the Multipart Prompt module to state what the user had inputted for their age.

The Exit to Survey module allows you to integrate a survey you've created in Plum Survey to your Plum Fuse application. The following example demonstrates how you would use the Exit to Survey module:

From this example, users are first prompted on if they would like to like to take a crayon survey. If users enter 2 for no, they would hear the prompt, “Have a nice day!” and the application hangs up. If the users enter 1 for yes, they would hear the prompt, “You will now be transferred to our survey.” From here, users would be transferred to the survey, Crayon Survey, which was created in Plum Survey.

If the survey was put back into an Editing state and the module wasn't refreshed, users would be directed to the “survey not ready” node and hear the message, “This survey has not yet been put in a Testing or Deployed state.”