CXone Studio ASSIGN/IF scope leak in nested blocks

NICE CXone API & Integrations
1

How do I correctly to isolate variable scope when chaining ASSIGN and IF actions in CXone Studio? I am generating a script where an IF block updates a variable, but subsequent logic reads the stale value outside the block. The ASSIGN action seems to persist the old value if the IF condition evaluates to false, causing branching logic errors. Is there a specific syntax or action sequence required to ensure the variable state is correctly committed or reset within nested conditional structures?

2

The problem here is scope isolation. CXone Studio ASSIGN actions are global by default. You must reset the variable before the IF block.

  1. Add an ASSIGN action setting the variable to null or a default value.
  2. Place this before the IF condition.
  3. Only assign the new value inside the true branch.
{
 "type": "ASSIGN",
 "variable": "status",
 "value": "default"
}

This ensures stale data does not leak if the condition fails.