Request node
The request node has a single input request terminal and a single output response terminal. Similarly, to the source node, it allows data to be retrieved from a data source. The request node differs from the source node in that it accepts input data from a request. This input data can influence or determine the data that is retrieved from the data source. The ability of the request node to accept request input is one way to introduce dynamic queries into the execution of a flow.
The request node is analogous to a map node whose map uses the GET function.
GET("adapter-alias", "command-line", request-data)
Like the GET function in maps, the request node supports a variety of data source types.
As for the source and target nodes, the settings categories of the request node are Connection, Action Properties, and Schema. The Connection category allows an existing connection or a command line to be used. When a command line is used, the type of the data source of the request node must be elected. The syntax and meaning of the command line value depends on the data source type. The available options for the Action Properties category vary depending on the data source type.
The transactions are committed at the node level if the data was retrieved or modified successfully (adapter’s GET operation was successful).
Example Use cases:
- REST APIs where the PUT or POST requires a body, and a response is returned in the HTTP response
- A SAP BAPI call has input parameters and a response to the BAPI call
- A converter that converts data from one form to another (e.g. SOAP adapter)
- A cipher adapter encrypts or decrypts the requested data
Process to create a request node
Request node can be placed as a first node, last node or between any other two nodes on canvas.
Node settings are:
- Connection: choose existing connection or select Use Command Line to specify the adapter and its command line.
- Define success and failure actions.
- Optimally, choose a schema that defines the node’s data.
Logging
The node produces a log that consists of the node’s internal messages and messages that underlying adapter generates. The adapter messages are prefix with the adapter name. The level of details depends of the flow execution log level.
Example log may look like (subject to change):
0: Called adapter EXCEL.
1: The adapter command line was: -WRKSHEET invoice1
2: The adapter success_action was set to: create
3: The adapter failure_action was set to: commit
4: EXCEL: Worksheet | invoice1
5: EXCEL: Excel Format | false
6: EXCEL: Trace file | __memory__
7: EXCEL: Trace append | true
8: EXCEL: Trace error | false
9: EXCEL: Trace verbose | false
10: EXCEL: Excel document data passed as GET parameter from the map
11: EXCEL: Reading Excel document data from the worksheet...
12: EXCEL: Total Rows in the Excel document: 5
13: EXCEL: Excel document data has been successfully passed to map!
14: EXCEL adapter performed the commit operation.
15: EXCEL retrieved 193 bytes.