-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 7.2-SNAPSHOT
-
Fix Version/s: 7.2
-
Component/s: Automation, Excel Export, Workflow
-
Epic Link:
-
Tags:
-
Impact type:API change
-
Upgrade notes:
-
Sprint:Sprint io 7.2-1
-
Story Points:1
Currently, if we call the SetWorkflowVar, Context.SetVar or Workflow.SetNodeVariable with a null value. It throws an exception.
The value is currently required.
This behaviour is especially annoying since the XML importer imports empty tag as null (instead of previous empty strings).
We want to accept null value as input.
- is duplicated by
-
NXP-14217 Automation > Fix error when setting null value for variable in SetVar operation
- Resolved