We have a complicated application process for missionaries to sign up to give their pitches for donations to their projects. I am trying to create a wizard in a portal for this application that is composed of 8 screens or sections.
My initial foray into this problem was to create one interface with adaptive sections that would hide or show depending upon where the applicant was in the process. That got very complicated fast!!
My next try was to break it up into multiple interfaces and using a process flow to step the applicant along. This didn't work as the process would stop at the next User Input Task and not show the applicant on the portal the screen. The portal seems to stay on the initial interface. I tried Activity Chaining and could not check the "This node will run as an automated activity...." radio button in the User Input Task.
Any suggestions on how to attack this problem?
Discussion posts and replies are publicly visible
Your second option would not work as an user input task which is part of process cannot be used in portals.You have to go with the first approach. Thats how most of the portal wizards are built