...
Parameter name | Description | Example | ||
CPI: Block in iFlow to get input payload | ID of the block in iFlow that can be used to get payload before processing from iFlow trace | CallActivity_2 | ||
|---|---|---|---|---|
CPI: Block in iFlow to get output payload | ID of the block in iFlow that can be used to get payload after processing from iFlow trace. Multiple IDs can be specified to support one to many scenario or validate multiple processing steps in iFlow | EndEvent_2 | ||
CPI: Adapter type | Sender adapter type in tested iFlow. Int4 Suite supports only HTTP, IDOC, SOAP, PROCESSDIRECT. Polling channels are not supported as well as timers. It is strongly recommended to move the sender channel logic to separate iFlow and connect it via ProcessDirect with main integration logic. | HTTP, IDOC, SOAP, PROCESSDIRECT | ||
CPI: Store ID used to persist message | The name of the store used to persistence the payload. Recommended approach is to use Block IDs instead of Store | BeforeMapping | ||
SOAP Action | The SOAP action if the tested integration flow has a SOAP sender channel | http://www.abc.org/po/NewOperation | ||
CPI: Variable name as application ID | The variable name to fetch the value for an application ID. In case not provided, the value will be generated automatically. | BUKRS | ||
CPI: HTTP Method | HTTP method if the tested integration flow has a HTTP sender channel | POST, GET | ||
CPI: HTTP Query | HTTP query if the tested integration flow has HTTP sender channel (optional) | param1={MYPARAM}¶m2={MYPARAM2} | ||
CPI: ProcessDirect endpoint | ProcessDirect sender channel endpoint | /iftt_pdirect | ||
Flat File Line Separator | The character used for end-of-line determination in Flat File messages: for example, CLRF - Unix. The parameter is used to display the comparison report better and display the reference and new message line by line. "Carriage Return and New line" character should be stored as CRLF "Line Feed" should be stored as LF (Unix based files) There is no default value, so the parameter is obligatory for CSV files | CLRF | ||
CPI: Externalized Parameter | Int4 Suite can change value of the externalized parameter before triggering a test case and revert the change back after test case execution. For example you can change your regular PROCESSSDIRECT outbound connection to dummy one and prevent sending message to the receiver. Many parameter can be provided for single automation object in form of <ParameterName>=<ParamterValue>
| Receiver1=IFTT_Default_Out | ||
CPI: Read CPI Headers | Tells the Int4 Suite to read additional technical CPI headers for the response. Default value is ' ' (false). | X | ||
Show XML in the correct original order (unsorted) | This flag determines if the lines of the file lines in the XML Comparison Report should be displayed unsorted in the original order or should be sorted alphabetically for a specific nodes. | Checked or 'X' - payload will not be sorted on the report Unchecked or '' - payload will be sorted alphabetically (default value) |
...