Skip to main content
K
kellyq2641
July 25, 2025
Solved

Confirmation Page

  • July 25, 2025
  • 20 replies
  • 0 views

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

Best answer by stefanhelzle0001

I covered this in an older blog post:

https://appian.rocks/2022/06/23/task-exceptions-quick-tasks/

20 replies

stefanhelzle0001
stefanhelzle0001Answer
July 25, 2025

I covered this in an older blog post:

https://appian.rocks/2022/06/23/task-exceptions-quick-tasks/

    K
    kellyq2641Author
    July 25, 2025

    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?

    shubhama926776
    shubhama926776
    July 25, 2025

    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.

    K
    kellyq2641Author
    July 25, 2025

    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.

    shubhama926776
    shubhama926776
    July 25, 2025

    Yes, it works - activity chaining will still take the user from the form to the confirmation page on the site.

    J
    jessek855119
    July 30, 2025

    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.

    Terms & ConditionsAccessibility statement