You can easily create a train task flow and add pages as Train stops and add in page train navigation and train buttons (Next/Previous) and create a wizard like navigation.
Yet many times you need to validate the input of a train stop before you go to the next one. When this validation is more complex than a required field you probably need to do it when the user tries to navigate to the next train stop.
I found a solution close to what I needed in Duncan Mills post: Executing Activities between Train Stops
http://groundside.com/blog/DuncanMills.php?blog=6&cat=18&page=1&disp=posts&paged=2
The strange thing is that you need to define an outcome on the target Train Stop activity.
Then you add a wildcard to go to a router to check your condition in order to decide to go to the target Train Stop or the source.
In my example the condition is if the Department has employees or not. If it has it go to employees page, if not it returns to department task flow.
The remaining issue is to show the appropriate message. In the example I have added it as a simple text that is visible when Department does not have Employees
Test Case:
http://adfbugs.googlecode.com/files/TestTrainValidation.zip
No comments:
Post a Comment