This page (revision-6) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
6 26-Nov-2021 10:22 1 KB rforbes to previous
5 26-Nov-2021 10:22 1 KB rforbes to previous | to last
4 26-Nov-2021 10:22 1 KB rforbes to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last COMPARISON_OF_NULL_VALUES ==> COMPARISON OF NULL VALUES
2 26-Nov-2021 10:22 1 KB JMyers to previous | to last
1 26-Nov-2021 10:22 1 KB JMyers to last

Page References

Incoming links Outgoing links
COMPARISON OF NULL VALUES
COMPARISON OF NULL VALUES

Version management

Difference between version and

At line 7 changed one line
In this workflow usercalc, we want to see when a value has changed in a given field. The easy solution is to test new value against old value like this:
In this workflow usercalc, we want to see when a value has changed in a given field. The easy and obvious solution is to test new value against old value like this:
At line 11 changed one line
If either the new value (NV) or old value (OV) are NULL, the condition will be false and you will always go down the else branch - even when they are both NULL. To deal with this scenario, we have to use some variables (recommended to be character type) and additional logic using the [EQNL|EQNL_OPERATOR] operator.
If either the new value (NV) or old value (OV) are NULL, the condition will be false and you will always go down the else branch - ''even when they are both NULL''.
At line 13 added 2 lines
To deal with this scenario, we have to use some variables (recommended to be character type) and additional logic using the [EQNL|EQNL_OPERATOR] operator.
This page (revision-6) was last changed on 26-Nov-2021 10:22 by rforbesTop