...
...
...
Steps to create a Context Variable
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
title | Settings to View Logs for Standalone/REST(API) triggered Process Flow in Adeptia Connect Dashboard |
---|
To View the logs in Connect Dashboard of Process Flow either triggered by REST (API) or executed standalone:
...
Context Variable Name | Available Key on Parent Context | Possible Value |
---|---|---|
transactionType | transactionType | 500 (App) 501 (File) 502 (EDI) 504 (Custom) |
templateName | templateName | |
templateId | templateId | |
spokeCompanyName / partnerName | spokeCompanyName / partnerName | |
spokeCompanyId | spokeCompanyId | |
PF_ReferenceID | PF_ReferenceID | |
transactionExecutionLoggerId | parentTxnExecutionLoggerId | |
hubCompanyName | hubCompanyName | |
hubCompanyId | hubCompanyId | |
direction | direction | 3200 (Inbound) 3201 (Outbound) 3202 (VAN) |
Info | ||
---|---|---|
| ||
In case any of the above parameters is not defined in Process Flow Context, and only 'View Logs on Connect Dashboard' property is enabled, the entry in the Connect Database will be blank. |
...
title | Settings to to run transaction using REST Webhook in a synchronous mode |
---|
To run the transaction using REST Webhook in a synchronous mode:
First, set the following predefined context parameters into the process flow.
Variable Name Description Default Value response The response text to be sent as successful response fault The response text to be sent as invalid response statusCode The HTTP status code 202 for successful response 500 for invalid response contentType The content type of response TEXT PLAIN Send the queryParameter async into the request. The possible values for this parameter is true or false.
When parameter value is async=false then the REST listener call will be synchronous with process flow execution, else if the parameter is not specified or is async=true, the call will be asynchronous.
...
title | Note |
---|
...