Missing or misspelled variables do not fail in Preconditions and Postconditions

Document ID : KB000085085
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

A variable that is referenced in a Workflow's precondition or postcondition rule becomes missing or misspelled.

Investigation

IF {THIS.VARIABLE.DOES.NOT.EXIST} = YES 
False 
FINALLY skip task with message 'DontRun'

Results
Actual:  It does not fail when the variable object fails to resolve.  Instead, the literal string including the curly brackets, { }, is used as text.
Expected:  It fails.

Cause:
Cause type:
By design
Root Cause: Curly brackets, { }, is not used as a reference for a variable.
Resolution:
The behavior is by design because a curly bracket, { }, can be used as a character or value for a condition.  Thus, the value is not changed or the condition aborted.

Fix Status: No Fix

Additional Information:
Workaround :
N/A