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
Here is the links to Quick Tasks - Common Process Model Workflows and Recipes - Appian 25.2
the MNI is right before the confirmation task in the screenprint I sent
May i know what exactly you are doing in subprocess(Which you are calling as MNI)?
Any attended activity(UIT)?
The subprocess creates # of requests , which is given by the user in the initial form in the start node to this subprocess I'm just passing the number of times it needs to execute and thats all. So if user passes 5, this subprocess would create 5 different instances. The goal is to at the end of the main process to show the user you have created these number of instances, these are the IDs.
Activity chaining will break when you call a subprocess that contains a user input task.I hope your subprocess has UIT which creates # request based on main process input.
no user input task in the subprocess. Just uses data from the main process input.
Can you share same snapshot of subprocess?
Also how you are calling subprocess sync or async?
Can you show snapshot of subprocess nodes?
This use case is incredibly common. If you have access to a customer's support portal, when you submit an Appian Support ticket, you'll encounter this exact use case. The problem is - even with extremely generous exception timeouts, the user will eventually encounter a pink box in Appian if they don't close the tab. (Error: Task has already been submitted, or something similar). This has been a 'thing' on every single Appian project I've been a part of.
There is a feature enhancement request floating around for a "process redirect to site page". The idea is that Appian developers can encode into a process model "at this point in the activity chain, the user should be redirected to XYZ site page rather than their 'last' Appian page". If you think such a feature would be useful, you'll have to find a way to submit an Appian Support case to request the enhancement as well.