Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A new object called getvariable has been implemented to support dynamic expression calculation for variables.

Dynamic expression calculation means the presence of two execution steps, as opposed to the traditional single execution step seen with a variable, where expression can be only static.

For example:

[
"getvariable",
"extUSER_CHAR",
"iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')"
],

In this case there will be two executions (calculations):

  1. The first Execution will calculate expression (iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')). In our example the result of this expression is |57|;

  2. The second Execution will use the result of the 1st execution, it works as expression for the second execution. In this scenario, the value will be taken from column 57 of the incoming CSV file.

This variable then can be used in the mapping as typical variable:

[
":extUSER_CHAR:",
"",
false,
null,
"",
"accountingTrade/userChar5"
],

In the resulting file, we should expect to find the value from column 57 in the element accountingTrade/userChar5.

It works the same way if the variable is defined with static expression:

[
"variable",
"extUSER_CHAR",
"|57|"
],

However, in the scenario, it's expected that the definition will be dynamically defined and the column number will be modified.

SDP-82063 Added new flag ValuationSource for PRICINGREPORTEXTRACT

...