...
Parameter name | Description | Example |
|---|---|---|
Rule Type | Rule type. Available options:
| |
Scrambling rule | Specify scrambling rule name for identification. | BEFORE |
Method | Choose a scrambling method from a list. Available methods:
| CONSTANT - Replace value with constant |
expression type | Expression type. Available options:
This field is optional for all interfaces where there is single type of output. However for interfaces that output might be both XML and flat file then it is mandatory to specify the expression type. | X |
XPath Expression 1 | Path pointing to the field/node where the exception should be applied. This might be both XPath syntax for working with XML files or int4 Flat File Syntax for flat formats like for example EDIFACT or other flat formats. | //ORDER/DATE/text() (XPATH expression) or START_TAG(BGM+220+)&&END_TAG(+)&& (Flat file expression) |
Processing Parameter | Specify Processing Parameter suitable for a chosen scrambling method. | X (for Mask method) |
...
Open /n/int4/iftt_conf_mass and select required automation object
Navigate to data scrambling section
You can set two types of Scrambling Rules:
- I Input - Test Case Payload for scrambling the data in the message before the mapping,
- O Output - Test Case Result for scrambling the message after the mapping.
Specify Creation - in case you want to scramble data during creation of a test case
- Runtime - in case you want to scramble data during runtime - when interface is executed and additional data is loaded to test case data.
Specify scrambling rule name and select a method from the list. You can replace value with constant, generate GUID number, random / hash value or replace each character with constant (mask option). You can also create a custom method (using interface /INT4/IFTT_IF_DATA_SCRMBL_METH).
Select expression type: Flat (for flat file) of XPath (for XML messages) expression and fill XPath expression. You should also fill column Processing Parameter Name. In our example, outcome setting will look like this:
Now, when user creates a new test case using this automation object and selects Content button to view message Payload we can see that product name data is scrambled (with predefined constant value):
Furthermore, after executing the test case and viewing its results we can see that payload data was anonymized in reference and outcome messages, as required:
...