This is a known issue in RSA Identity Governance and Lifecycle 7.0.1 and 7.0.2.

The problem occurs for new or existing Workflow Activity Nodes of type Decision Node where the decision is based on Conditions using Workflow Variables.  The problem occurs when a variable name is typed manually into the Operand section of the workflow variable section.  If the variable is selected from the drop down list, the feature works as expected.  If the Workflow decision node based on a previously defined workflow variable was working correctly, making any change to the workflow (even changes not related to the Decision Node) may cause the workflow to fail in the manner described.  

The problem occurs because we incorrectly parse the Condition variables and exclude any variables that are not populated in the drop down box. 

For new workflows the following technique may be used to work around this limitation.  Ensure that you only use variables that are defined in the Workflow as local or global variables and that populate the Condition dropdown list.  If you need to access an internal variable that is not displayed in the drop down list such as a form variable, then use a SQL Select node to assign the value of that form variable to a local variable and then use the local variable as the object for the Workflow Activity Node Decision Node Condition Statement.

Use the following SQL SELECT statement to assign the value of your variable to a local variable of your choice, such as MyVariable:

SELECT ${Peop} AS MyVariable FROM DUAL

In the Activity Node Decision Node, select the new variable you have defined from the drop down list.