UpdateTransaction

This activity helps the user to update the existing transactions to update the fields. It can also be used to move the transactions from one to another queue.  It accepts the input values of the “Json” format extracted as output in the “Get Transaction” activity as it requires the “Batch ID, URN and Queue” of the existing transaction to be updated.

Pre-Requisites

1. The Input “Json” provided here should contain the “BatchID, URN” of the existing transaction.
2. It accepts only the output extracted from the “Get Transaction” activity as input in the “JsonData” field here.
3. You can update the existing field values by either hardcoding the values or providing the variables. (Refer below in the document to get a detailed understanding.)

Properties

INPUT

AttachmentFieldName: 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.

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

Json:*  To update transactions, you should provide the “Json” string to the Project. The sample “JsonString” can be extracted from “SmartInteract” in Manager. It will incorporate with the values passed in the “InputParameters” field and creates a transaction.
This parameter accepts values in “String” datatype. You can either hardcode the values in “String” datatype or can enter the values in “String”. The “InputString” must be in “Json” format. (Refer the tips below).

JsonData:*  This parameter indicates to provide the “JsonData” resulted as output in “GetTransaction” activity as input here. It accepts values in only “String” datatype, or you can input the “String” variable that contains the “Json” values. The “InputString” must contain the “Json” format. (Refer the tips below).

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

ResponseBatchID:* It helps to extract the “BatchId” of the updated transaction as output. It returns in the values in “String” datatype.

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

ResponseValue: It helps to view the response as  “status” from the service for updated transaction. It returns in the values in “String” 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.

* Represents mandatory fields to execute the workflow