Allow workflow global variables in SQL query to retreive external data.
I'm not sure if this is a formatting issue, a bug, or simply unavailable but when building a "where clause" in a workflow for assigning data from external data, I select a workflow global variable as the comparison but it always returns null.
Example: ENTRY_TYPE="PROJECT" and PROJECT_NAME=GV_gProject
However, if I simply replace "GV_gProject" with the actual hard coded string, the result is correct, so it the query is correct but the GV is not being placed into the query it would seem.
Because the wizard provides access to the global variables, this should function.
For the time being I have to write web services to perform the same queries and return the index data but would much rather have the entire process within the workflow design.
Thank you for your contribution. Your idea is already available.
Gilles Sauvagnat commented
Try it using single quote for the global variable
ENTRY_TYPE="PROJECT" and PROJECT_NAME='GV_gProject'