Use of Standard "Workflow" Field Does Not Work as Request Type Rule Dependency
I am attempting to use the out-of-the-box "Workflow" field (Token = "Workflow_ID") as a dependency in a Request Type Rule, in order to hide certain fields (via "setFieldVisible(false)") for different workflows. For some unknown reason, this rule does not recognize the "Workflow" dependency and therefore fields remain visible. I have tested the same rule with the "Workflow" dependency removed, and desired fields are then hidden.
Re: Use of Standard "Workflow" Field Does Not Work as Request Type Rule Dependency
We have the Workflow field displayed on the request and use that request field token in our rules to hide/show fields based on which workflow is set for the request. This has worked great for us. Hope this helps. 🙂