The title refers to ExecuteAction, but this is also relevant for ExecuteWorkflow and any command created from the page designer that maps parameters.

We have a projection action that takes a boolean flag argument, and in this case we want to invoke it from a page with a constant value for this flag, but every attempt at doing so is interpreted as a string and yields an ODP_DESERIALIZATION_ERROR, stating a mismatch between the expected boolean and the received string. I have tried sending expressions (a feature already known to work for toggling page booleans such as element visibility) but these, too, are interpreted as string literals.

Is there a way to pass non-string literals (or cast from number to string or vice-versa; we had to do this for some navigation items, and were able to cast numbers to strings with ‘${NumericVariable}’, single quotes included, but don’t know the other way around) in parameters mappings for commands, or are we simply out of luck here?