Best practices before deleting a Symphony variable

Deleting a Symphony variable permanently removes it from the Symphony, including its name, data type, default value, and all references. After deletion, the variable is no longer available anywhere in the Symphony.

Removing a Symphony variable can have significant consequences, for example:

  • Activity failures: Activities that use the variable for input or output lose required values, resulting in validation errors or execution failures.
  • Broken state logic: State transitions that evaluate conditions based on the variable can no longer be resolved, causing incorrect routing or halted execution.
  • Invalid flows and workflows: Data flows and workflows that depend on the variable may receive empty or invalid values, leading to incorrect results or complete failure.
  • Overall Symphony instability: A single deleted variable can affect multiple activities and states, causing missing bindings, runtime errors, and unpredictable behavior.
Note: You cannot approve a symphony version that references deleted symphony variables.

If a referenced variable is deleted, Enterprise Orchestrator clears the variable reference, and you must manually provide a value in the corresponding input fields.

Best practices

Before deleting a Symphony variable, verify these elements:

❑Which activities reference the variable

❑ Whether state conditions depend on the variable

❑ If flows or workflows use the variable as input or output

❑ Whether the variable controls looping, branching, or routing

If the variable is still in use, deleting it causes errors.