Wednesday 10 August 2011

ADF Task Flows and the wildcard (*)-"To Activity ID"

Be careful when you use the wildcard (*) (or nothing for the from outcome or from action properties, for that matter) as ID for the "To Activity ID" to direct the flow back to a Router ADF Task Flow component. Due to the wildcard all activities/actions will be consumed by the Router component and hence only direct the flow as it is configured in the Router component's cases.

I had a case where an action, which originated from outside the page flow scope, did not actually get performed/handled by loading another task flow or page and I eventually figured that the router component consumes the action and makes it ineffective.

No comments:

Post a Comment