Flow requestParameters input mapping

[jonnio]

Folks,
I should be able to do this at the top of my flow definition (SWF 2.0.8.RELEASE) to capture a request parameter into a flowScope variable, right?

<input name="command" value="flowScope.commandId" type="int"/>

It doesn't work so I have to do this in a transition to capture the value:

        
<transition to="detail" on="detail">
    <set name="requestScope.commandId" value="requestParameters.command" type="int" />
    <evaluate expression="myExpressionHere.get(commandId)" result="flowScope.xyz"/>
</transition>

Is this a bug or am I mis-reading the documentation?

Jon

[Marten Deinum]

If you would implement it correctly it works... Currently you are assigning the value of flowScope.commandId to a attribute named command.

[jonnio]

But if I change the request to

<input name="command" value="requestParemeters.commandId" type="int"/>

I get some gnarly exception about the request parameters not being found. Thoughts?

[Marten Deinum]

input mapping only works at the start of a flow, not from a transition, instead of specifing requestParameters simply put 'commandId' webflow will try to detect it from somewhere.

Next to that 'requestParemeters' isn't a valid name 'requestParameters' is.