GetTransaction

This activity assists the user in extracting details from the created transactions associated with the specified ‘Batch ID and URN’ found in the queue on the ‘Interact’ page.

Properties

INPUT

AttachmentsFieldName: This parameter indicates to provide the “FieldName” of the Attachment if any created in the Interact. This field name can be extracted from “SmartInteract” in Manager. Refer the below document. You can either hardcode the values in “String” datatype or can enter the values in “String”. When left blank, it will not be considered. This parameter accepts values in “String” datatype.

DataTableFieldName: This parameter indicates to provide the “FieldName” of the “Table” or “Group” if any created in the Interact. This field name can be extracted from “SmartInteract” in Manager. Refer the below document. You can either hardcode the values in “String” datatype or can enter the values in “String”. When left blank, it will not be considered. This parameter accepts values in “String” datatype.

DownloadFilePath: Indicates to provide the “FilePath” to download the attachments against the field, if any available in the “Interact”. You can either hardcode the values in “String” datatype or can enter the values in “String”. When left blank, it will not be considered. This parameter accepts values in “String” datatype.

FileOverWrite: Indicates to overwrite the “Files” that are being downloaded from the “Interact” in the specified path. By default, the box will be “checked”.

InputParameters:* This parameter helps you to provide the “inputs” that are required to pass against the fields in the Project during the execution. This parameter accepts collection of argument types.
Refer the below documentation to pass the values.

QueueName:* Indicates to provide the “Queue” name from the “Project” against which the “transaction” needs to be added. This parameter accepts values “String” datatype.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

JsonData:* It helps to view the output of the activity as “Json String” for the extracted transactions. It returns in the values in “String” datatype.

OutputDataset:* It helps to view the output of the activity as “Dataset” if there are any tables or group available in the extracted transactions. It returns in the values in “Dataset” datatype.

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”
True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

URN:* It helps to extract the “URN” of the created transaction as output. It returns in the values in “String” datatype.

* Represents mandatory fields to execute the workflow