We often use Global Macros to define useful constants, for example gettablenum( SETTINGS_TABLE, SETTING_RUNTIME_ROW, SETTING_VALUE_COL)
is more readable and maintainable than gettablenum("Settings", 3, 2)
.
However, it seems that the query strings in for example Process Flow's Pull from list or Acquire Resource activities do not parse them correctly. Please see the attached model for a demo, it has a global macro #define FIVE 5
. I try to pull resources off the list with the following queries:
WHERE Rank > FIVE
- This does not match any items on the listWHERE Rank > 5
- Replacing the macro by its definition works as expectedWHERE FIVE = 5
- Does not pull any items either. Interestingly enough, neither doesWHERE FIVE = 0
so I don't know what FIVE evaluates to. Finally I observed thatWHERE FIVE != 0
does pull an item.