Workflow becomes invalid when passing 'false' as boolean list element value in AddOrder instruction.

Current Behavior:

• When passing false as a boolean-type list element value from the Add Order instruction to another workflow, the workflow containing the Add Order instruction enters in 'not valid' state. Despite this, it is still possible to deploy the workflow, but it transitions into a 'not valid deploye' state.

This issue occurs specifically when the boolean-type list element value is set to 'false' and passed from the Add Order instruction.

Steps to Reproduce:

• Create two workflows: W1 and W2.
• Inside W1, create a list variable test with 3 elements: t1 (string), t2 (number), and t3 (boolean).
• In W2, add an Add Order instruction where you attach the W1 workflow and assign values to all three list elements: t1 = "testing", t2 = 1, and t3 = true.
• Check the status of the workflow — it should be in a valid state.
• Now, change the value of t3 to false. The workflow will enter a not valid state.
• If you try to assign the value false to t3, the value is removed, and the following message appears on the status section:
  $.instructions[0].arguments: Key 't3' of the list[0] variable 'test' is missing but declared in the workflow

Desired Behavior:

• The workflow should accept 'false' as a valid boolean value for list elements passed via the Add Order instruction. It should remain in a valid state without treating false as a missing value.