Go To App

Function

This module enables users to call and execute other Fuse applications from within an application.

Select the application to jump to from the drop-down menu, as well as the preferred revision, if there is one.

Please note that any application(s) that users would like to call out to in their Fuse application(s) must be owned or shared by that user.

The values in the ‘Variable’ and ‘Value’ fields contain the data that this module passes to the sub application. Once the sub-application is finished and exited, the call flow will continue with the node () at the bottom of the module.

Upon exit of a sub application all of the variables declared in that sub application become available as properties of the Goto App module variable.

For example, if the Go to App () module is titled “Payment” and it has a variable defined as transactionID, that variable becomes available in the main application as Payment.transactionID.

The format for this is modulevariable.subvariable.

It is important that the sub-application (Sample Payment App) has a proper Exit () module to mark the end of the sub-application so that the call flow can continue.

A common use for the Go to App module is to ensure PCI compliance. This module also allows separation of applications for user control.

Assume that a Fuse application processes payments, but the marketing team also wants access to the application in order to update messaging and offers.

In this situation, it makes sense to isolate the actual payment process in a separate application to ensure data integrity. The remainder of the call-flow exists in a separate application that is accessible by the marketing team. A Go to App () module that points to the payments application would then be inserted into the main application in the appropriate space.

Note: If the main application is shared with another user and is to be deployed separately in that new user's account, then any sub application referenced in the Goto App modules should be shared with that user as well

Module Settings

Private

This setting controls the logging function of a module. Enabling the 'Private' setting instructs the module to not record, report, or retain the information input to that module for reporting or any other purposes. When enabled any information entered into a module during a call will be lost immediately when the call terminates. The 'Private' setting is critical for businesses that need to maintain PCI-DSS or HIPAA compliance. The module icon, in the upper left-hand corner, becomes grayed-out when this setting is enabled. See more details here.

Note: The private setting here will prevent logging only for variables and values defined in this module. Modules in the sub application will follow its own private logging settings.