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
HI Chris.Gillespie ,
We have similar requirement where Vendor Onboarding Form has Many sections almost 9 where Vendor Fills in the portal. We went with one interface having all sections and depending on the flow and selected wizard we show section( as you mentioned you tried). Would like to know what difficulty you are facing?
AFAIK, we cannot use multiple interfaces to display seamlessly in portal. Because only way to start a process from Portal is by using a!StartProcess or calling integration.
HiChris. Gillespie (chrisg0006) creating one interface with adaptive sections would be the possible approach in this scenario, may I know what is the issue you are facing in this approach could you post more context on the issue, please
Hi Chris,
Your first approach would be far more suited for portal approach. If I remember correctly same type of problem was raised by some one few weeks back and one of the Appian employee suggested to go with same approach.
Your first approach is the way to go.
I simple main interface could look like this:
a!localVariables( local!step: 1, choose( local!step, rule!interfaceStep1( step: local!step, record: ri!record ), rule!interfaceStep2( step: local!step, record: ri!record ), . . . ) )
Then you can fully control all aspects from the child interfaces.
https://appian.rocks/2022/07/05/data-in-interfaces/
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
Make 8 Interfaces: Create 8 screens for each step.
Set Up a Process Model: Use a process model with user tasks for each screen.
Add Navigation Buttons: Include Next and Previous buttons on each screen.
Track Progress: Use a variable to remember the current step.
Redirect Users: After each submission, move users to the next screen.
Test It: Make sure everything works smoothly.
This will help you create a straightforward wizard in Appian!
This does not work in portals.