Announcement Announcement Module
Collapse
No announcement yet.
<input> requestParameters and subflows Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • <input> requestParameters and subflows

    I put some thought into this issue in the past and thought if my mind came across it again - I'd just ask.

    I set a required input at the top of the flow defn to capture the request parameter clientId and put it in the conversationScope - except it seems input is only for subflows, not initial request parameters? So I removed it.

    So I use 'set' to do the same in the on-start...like so

    <code>
    <on-start>
    <set name="conversationScope.clientId" value="requestParameters.clientId"/>
    </on-start>
    </code>

    But what if I want to reuse this flow? It would need the same input. If I specify 'input' at the top, won't the on-start requestParameters.clientId override it with nothing? What's the best practice for this approach - to have a webflow as a top level flow and as a subflow?

    Cheers,
    adam
Working...
X