Alumio's evaluation

Hi there!
My question is towards Alumio’s evaluation:
Are the conditional transformer’s conditions (or basically any conditions inside Alumio) evaluated lazy, or eager?

Example: I might have a ‘method’ variable set in the data. If that method set, and if it is “POST”, then I want to do something. If it doesn’t exists, or if it isn’t “POST”, then I don’t.

On a situation of it not being set: can I place the ‘key exists’ and ‘value condition’ inside one conditional transformer as “All conditions have to be true” setting, and will the evaluation stop at the ‘key exists’ condition, or will it throw an exception on a non-existent ‘method’ variable because of the latter condition?

Thank you for your answer in advance!

Hi @gerg.borsodi

The “Value Condition” + the “Equals” comparator will first check whether the key exists. If the key doesn’t exist, the “else” part of the conditional transformer will be executed. Therefore, you don’t need to add the “Key condition” and “All conditions” to the conditions.

In addition, the “Key condition”, “Value condition”, or the other available conditions will not throw any exceptions. If the conditions are not met, Alumio will execute the “else” part of the conditional transformer.

Please let us know if it doesn’t answer your questions.

Thank you for your answer!

1 Like