...
Field Name | Description |
---|---|
Transaction | Name of the Transaction. |
Template | Name of the Template used for creating Transaction. |
Type | Type of Transaction whether App Inbound or Outbound or File Inbound or Outbound. |
Started | Date and time when the Transaction was executed. |
Reference | Displays the name of the source file. This field is applicable only for file-based applications. |
Status | Displays the status of the Transaction. The status can be Fetching, No Data, Queued, Running, Success, and Abort. Fetching: Transaction is fetching data from the specified location. No Data: Transaction couldn't find any data at the specified location so far. Queued: Transaction is in a queue and is waiting to fetch data. Running: Transaction execution is in progress. : Successful execution of the Transaction. : An error in the execution of the Transaction. |
Action | : View details of the execution. Execution status is displayed graphically. indicates all the stages of the Transaction execution have been processed successfully. In case of an error, the status is displayed with the cause and fix of an error. Click to view the error details. |
: Re-runs the aborted Transaction after rectifying an error. You can only Re-run the Transaction till the time its reprocessing file is available and not deleted by the cleanup job. You can either Re-run the Transaction from the last failure stage or upload a new file to Re-run the Transaction. | |
: Displays the detailed logs of the process flow (running in the background of Adeptia Connect, that is, in the Developer's Studio). It also displays the activities used in the process flow that is executed to process the Transaction. | |
or process flow. | : Displays the list of repository files created during execution of the Transaction|
: Displays the log details of the activities used in the process flow to execute the Transaction. | |
or process flow. | : Displays the value of the context variables used in the Transaction
Anchor | ||||
---|---|---|---|---|
|
...