Hi All,
What would you all recommend for implementing a confirmation page after a form is submitted ? another user form ? The only concern I have is that once my user submits the form is a subprocess creating multiple instances (as we need). So basically for the confirmation page we need something along the lines this # of items were created in the system, even better if we can give the ids of the created items.
Any suggestions for a good design implementation?
Thanks in advance
Discussion posts and replies are publicly visible
I covered this in an older blog post:
https://appian.rocks/2022/06/23/task-exceptions-quick-tasks/
Use a User Input Task after all item-creation subprocesses complete, passing the number and IDs of created items to process variables. Display these on a confirmation page with activity chaining from the form submission to the confirmation screen for seamless user flow.
When I try to access the link you have attached for the appian documentation it says it no longer exists, is this option is still possible in newer versions of appian?
would this still work even if we are launching the initial form from a site page? they click on the menu name and the form launches.
Yes, it works - activity chaining will still take the user from the form to the confirmation page on the site.
This is how I have my sub process set up.., the initial form is being launched from a site page.
when I try this after it says action is completed it just takes me back to the intial form page. This is the setup for my subprocess
Add a User Input Task right after the MNI node and make sure activity chaining is enabled from the form through the MNI to this confirmation task, so that the user is taken directly to the confirmation page after all items are created.
thats what I currently have, but is still not working.
MNI often breaks activity chaining in because it creates parallel tasks. To fix this, ensure MNI is used only on background nodes, then chain directly to a single User Input Task assigned to the submitting user for confirmation. Avoid gateways or async nodes between MNI and confirmation to maintain the chain.