Cloud FTL Request Reply

Cloud FTL Request Reply is an asynchronous activity that is used to send a request to an FTL application and wait for a response.

General

The General tab has the following fields.

Field Literal Value/Module Property Description
Name No The name to be displayed as label of the activity in the application.
Request Format No Defines the set of fields in the message that is sent by the Cloud FTL Request Reply activity. The form of each FTL message (its field names and their value datatypes) is governed by a format. The field is pre-set to Custom and can be defined by using the Input Editor.
Request Format Name Yes

The name of the Custom format.

Reply Format Yes Defines the set of fields in the message that is sent by the FTL Request Reply activity. The form of each FTL message (its field names and their value datatypes) is governed by a format. The supported formats are:
  • Custom: can be defined by using the Input Editor. The Input Editor is enabled only for the Custom format option.
  • Keyed Opaque: is a built-in format that contains a text key field and a binary (opaque) data field.
  • Opaque: is a built-in format that contains a binary (opaque) data field.
Reply Format Name Yes The name of the Custom format.

This field is displayed when the Custom format is selected.

Description

Provide a short description of the activity here.

Advanced

The Advanced tab has the following field.

Field Literal Value/Process Property/Module Property Description
Activity Timeout (msec) Yes It is the amount of time Cloud FTL Request Reply activity waits to get the reply from the Cloud FTL Subscriber.
Note: Note: When the Cloud FTL Request Reply activity timesout, the in-line subprocess instance called by the Cloud FTL Request Reply activity can be cancelled before the subprocess instance completes. Hence, the business logic in the cancelled process instance may not be executed to its entirety.

Input Editor

The Input Editor gets enabled only when Custom format is chosen in the General tab. The schema must match the schema of the input for the activity shown on the Input tab.

Output Editor

The Output Editor tab defines the schema to use for reply messages. This tab gets enabled only when you select the Custom format.

Input

The input for the activity depends on the Format you select in the General tab. If you select Custom format, the input is a data element defined in the Input Editor tab.

Output

Shows the output reply message. The output reply message depends on the format you select in Reply Format with the message metadata and reply message.

Fault

The Fault tab lists the possible exceptions thrown by this activity.

Fault Thrown When...
FTLRequestReplyActivityFault The Cloud FTL Request Reply activity fails due to a runtime error.
FTLCreateRequestMessageFault The FTL request message could not be created.
FTLSendRequestMessageFault The FTL request message could not be published.
FTLProcessReplyMessageFault The FTL reply message could not be processed.
ActivityTimedOutException The timeout is reached.