Right now, single-select and multi-select attributes are not workflow “aware”. Meaning, you can’t use Lava to define their options if that Lava is based on the value of another workflow attribute.

For instance you can’t have a person workflow attribute (set by one User Entry Form), and then offer a single-select in a later User Entry Form listing the family members of that person. The closest we’ve found is to take the person attribute and put a representative value in the PageParameters when displaying the second form. Then the single- or multi-select value template can look for that page parameter and offer the correct options without relying on a Workflow | Attribute lookup. However, when using this method the Workflow List grid does not display the correct values for the select attributes because it’s still looking for the page parameter rather than the workflow attribute value.

Maybe a “delayed evaluation” checkbox on these attribute types could be added, to indicate to Rock that the value template shouldn’t be evaluated while the workflow is being edited, but only within the context of a specific workflow instance. For instance, on the workflow list grid when the value of such a single- or multi-select attribute is shown, it would be in the context of the specific workflow rather than in the context of the workflow type as it is right now, so that Workflow | Attribute type lookups would function properly.