Description

This postexecuter can change the values of up to 2 variables.

If a variable in the parameter string is not defined in the profile, the profile is terminated with an error.

The profile must also have an active mapping, otherwise no value change can be made. However, this does not cause an error.

Important note: The changes made to the variable values have no influence on the mapping result and the content of the output file. But the changed values would, for example, be passed on to a subsequent profile called via Message. Additionally, variable values (through placeholders) in configuration fields of the current and subsequent Response Routes could be changed.

Important note: If the Response Route of type Message with content setting Trigger profile is used, no value change is performed. If the Response Route of type Custom Class is used and the selected class does not use any data, no value change is performed. This is the case with class WaitResponse, for example. If you develop such a class yourself, this controlled by method dataRequired.

Parameter Description

The parameter string is specified in field Config file in the following format (the separator between the first variable name-value pair and the second is a semicolon):

<VariableName1>=<NewValueVariable1>[;<VariableName2>=<NewValueVariable2>]

Important hint: <NewValueVariable1> and <NewValueVariable2> are not allowed to contain the characters = (equal sign) or ; (semicolon). The second variable name-value pair is optional.

Example

Assume the two string variables var__TEST1 and var__TEST2.

The following parameter string is used in field Config file:
var__TEST1=333;var__TEST2=444

As a result, the variable var__TEST1 now has the value 333 and variable var__TEST2 has the value 444.