Page Comparison

Parameter name

Description

Example

Test Case Creation

CPI: Block in iFlow to get input payload

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: Attachment Name to get input payload

Attachment Name from which input payload can be fetched

Source_Attachment

CPI: Attachment Name to get output payload

Attachment Name from which output payload can be fetched

Target_Attachment

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

Output Automation Object

Automation Object(s) used to read the output payloads. This parameter allows for testing scenarios where message is injected into one iFlow and results are compared on a different one.
Automation Objects(s) of type 12 ( SAP CPI E2E Inbound ) and 13(SAP CPI E2E Outbound) are allowed to be used.

Child Test Case Automation Object

Automation Object(s) used to link and create child test cases. This parameter allows for automatic creation of linked outbound test cases during save.

Following Automation Object types can be used as child:

5 PI E2E Outbound
7 IDoc Outbound
13 SAP CPI E2E Outbound

CPI: Read CPI Headers

Tells the Int4 Suite to read additional technical CPI headers for the response.

Default value is ' ' (false).

X

Test Case Execution

CPI: Adapter type

Sender adapter type in tested iFlow. Int4 Suite supports only HTTP, IDOC, SOAP, PROCESSDIRECT, SFTP.

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, SFTP

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

HTTP Header

Add custom HTTP header sending to CPI.

There are two methods to use this parameter:

1. Directly filling the header name and header value in format "HeaderName=HeaderValue".

2. Indirectly by filling the header value using a value from Variable d

   1. defined for this purpose (e.g., named Variable1) in the format 

    "HeaderName={Variable1}":

   1. please remember to use curly braces ( {} ) while using this method

   2. we recommend using this method for header values containing such characters as: {, =, }.

Header1=123 (Method 1)

or

Header2={Variable2}  (Method 2)

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

General: 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)

Separator can be also specified using hexadecimal representation of Numeric Character Reference (NCR).

There is no default value, so the parameter is obligatory for CSV files

CLRF

Flat Files Compare with payload validations applied

If this checkbox is checked, Payload Validation rules are applied before files

Use || to enter multiple alternative separators e.g. CLRF||'

CLRF

NCR Example:
&#x1C;

Line Separator Escape Character

Escape character for line separator. Used to avoid line breaks in case separator is used in the file content.
Value of this parameter should be aligned with specific format used by tested interface.
Example: If line separator is set to ' and escape character is ? following split is applied:

Source:
NAD+SU+8720121000874::3++Test?'file'NAD+SU+8236459000874

Split:
NAD+SU+8720121000874::3++Test?'file'
NAD+SU+8236459000874

Flat Files Compare with payload validations applied

If this checkbox is checked, Payload Validation rules are applied before files comparison and the match content is replaced by the placeholders. This can in some cases result in better flat file comparison results, especially in case of many missing lines. cases result in better flat file comparison results, especially in case of many missing lines.

File Type - Input

Determines processing of input files ( variable extraction & replacement).

Possible values:

• Auto-detect (default)

• XML

• Flat file

• JSON

File Type - Output

Determines processing of output files ( variable extraction & payload comparison).

Possible values:

• Auto-detect (default)

• XML

• Flat file

• JSON

Show XML in the original order (unsorted)

This flag determines if the lines of the file in the XML Comparison Report should be displayed 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)

Do not fail TC if DB reference not found

If this checkbox is set TC won’t fail if no reference document is found in by DB Validation rules

SOAP Adapter

SOAP Action

The SOAP action if the tested integration flow has a SOAP sender channel

http://www.abc.org/po/NewOperation

HTTP Adapter

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}&param2={MYPARAM2}

CPI: Fetch CSRF Token

If this checkbox is set Int4 Dispatcher will try to call CSRF Token URL to get CSRF token

CPI: CSRF Token Fetch HTTP Method

Methods used by Int4 Dispatcher when calling CSRF Token URL endpoint

HEAD, GET

CPI: CSRF Token URL

URL endpoint used to get CSRF Token

ProcessDirect Adapter

CPI: ProcessDirect endpoint

ProcessDirect sender channel endpoint

/iftt_pdirect

SFTP Adapter

CPI: SFTP Directory

SFTP Directory (folder) where the file should be placed

Tests/Files/Test1

CPI: SFTP File Name

SFTP File Name that should be used, variable usage is possible like with other parameters

test{MY_VAR}

CPI: SFTP Address

URL of the SFTP server

CPI: SFTP Credential Name

Alias to the CPI credentials from Security Material

CPI: SFTP Private Key Alias

Alias to the private key from Keystore

CPI: SFTP Proxy Type

Proxy Type - default value is “internet”

internetonPremise

onPremise

CPI: SFTP Location ID

Location ID defined in destination configuration for Cloud Connector. Relevant only for Proxy Type onPremise.

DP1_ERP

AMPQ Adapter

CPI: SAP Event Mesh Host

SAP Event Mesh host as in the channel under test

test-example.example.eu10.hana.ondemand.com

CPI: SAP Event Mesh Queue

Queue name from SAP Event Mesh

test/demo/em/int4suitedemo

CPI: SAP Event Mesh OAuth2 Credential Name

OAuth2 Credential Name used in the channel under test. Those should be credentials deployed on Cloud Integration tenant Security Material

EMOAuth2cred

CPI: SAP Event Mesh Content-Type

SAP Event Mesh Content-Type. By default it can be application/xml.

application/xml

application/json

text/plain

JMS Adapter

CPI: JMS Queue

JMS Queue name, as in iFlow under test

JMS_QUEUE

CPI: JMS Content-Type

MIME Content-Type

application/xml

application/json

text/plain

Parameter name

Description

Example

Database validation ruleset

GENERIC_SO

Persist reference DB Data

When switched on, DB reference data will be fetched from backend system during test case creation. Otherwise, it will be fetched during test case execution.

https://int4support.atlassian.net/wiki/spaces/IUM/pages/2062843993/Automation+Objects#Database-Validations