CROSS CHECKING

Cross Checking mode – node is used to implement rules that validate the data of the current transaction and historical transactions​. The rule that has been verified positively generates an "alert". The node contains 3 sections:

  • Collection - the name of the auxiliary structure to write historical data​

  • Validator - validation rule​

    • Search time - search time window

    • Keys - search keys​

    • Validators - a set of conditions checking rules​

      • Example databaseVariable!=scenarioVariable​

//An alternative comparison method using Levenshtain distance
import static org.apache.commons.lang3.StringUtils.getLevenshteinDistance
a = getLevenshteinDistance(databaseVariable, scenarioVariable )
return a>2

  • Variables -

Cross Checking node

Additional data and result

Defining an object with variables that we want to save and further cross-check (the "event" object in this example)

If the key field in the "event" of the current request ("pesel" in this example) has the same value as in any previous request, all defined validators are checked.

If the conditions for a given validator are met, this will be visible in the result ("validationResultsCC" in this example).

We have access to all values that are saved in the "event" object in the found requests. Option "Saving object for cross-checking" allows to use many nodes of cross-checking in one scenario (only the last node in a sequence should have this option set to 'true')

In each node we can add many validators

PreviousDATABASENextCACHE

Last updated