Spec> If a navigation case is matched that causes the new viewId to be
Spec> different from the current viewId, the runtime must force a
Spec> redirect to that matched navigation case with different viewId,
Spec> regardless of whether or not the matched navigation case with
Spec> different viewId called for a redirect.
When using <f:viewAction> to enter a flow, this is functionally
equivalent to using GET based navigation to enter the flow, however,
this code path misses out on attaching the necessary parameters required
by FlowHandler.clientWindowTransition() to successfully enter the flow
in the GET based navigation case. Specifically, the
FlowHandler.TO_FLOW_DOCUMENT_ID_REQUEST_PARAM_NAME and the
FlowHandler.FLOW_ID_REQUEST_PARAM_NAME must be added to the query string
when entering the flow in this way.
The trick here will be to find the right place to specify that these
must be tacked on.