Transact Function Triggers

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    Form Builder Platform Developer |  17.10 This feature was introduced in 17.10.

Journey Manager provides a number of API calls which represent the application lifecycle so you can trigger server side services (called fluent functions) after these calls. Within these services you can run any application logic you require for the customer journey. For an application to call a fluent function it must be associated with the Form Version; these are called Transact Functions.

Transact Functions provide an improved programming model for client applications to call server side business functions. Form Functions are designed for applications to make calls to other systems for doing remote data lookups or executing some secure business logic on the server. They provide the modern replacement for Form Dynamic Data Services but with an improved programming and security model.

Fluent Functions can be triggered on a variety of form function triggers. Below are all the function trigger types with example use cases.

Form Open

Called when new form transaction is created, immediately before it is rendered to the browser. This event trigger is initiated by the Manager server.

Use Case

An example use case for this trigger type is to prefill data into an application.

Form Resume

Called when a saved form transaction is resumed, immediately before it is rendered to the browser. This event trigger is initiated by the Manager server.

Use Case

An example use case for this trigger type is to prefill data specific to a returning user into an application.

Form Save Challenge

Called when a save challenge is performed.

Use Case

 

Form Update

Called when the form makes an background update operation. This event trigger is initiated by the application.

Use Case

Two example use cases for Form Update are:

• Sending and retrieving data on page / route change
• Adding / removing an attachment

Form Ineligible

Called when the application determines the user is ineligible to complete the transaction. This event trigger is initiated by the application's business rule scripts in the browser after determining the user is not eligible to complete the application.

Use Case

An example use case for this trigger type is to send an email to the customer saying they are ineligible.

Form Function

Called by the application generally to get dynamic data from the server and perform any transaction updates.

Use Case

Two example use cases for Form Update are:

• Retrieving an address list based on an input parameter
• Validating a user account

User Save

Called when the user explicitly saves and closes the application. This event trigger is initiated by the user of the application.

Use Case

Two example use cases for Form Update are:

• Sending a custom save / resume email to user
• Expiring a users session

User Submit

Called when the user explicitly submits a completed form application. This event trigger is initiated by the user of the application.

Use Case

Two example use cases for Form Update are:

• Sending a custom submission completed email to user
• Sending data to a back office data server

User Cancel

Called when the user explicitly cancels and closes a form application. This event trigger is initiated by the user of the application.

Use Case

Two example use cases for Form Update are:

• Sending a custom abandoned email to user
• ?

Next, learn how to configure triggers.