Hi Appian community, happy summer,
I have a use case where there is an interface with buttons (Approve, Deny, and Back) on a site page.
I initially set the Approve and Deny buttons up as button widgets and had a startProcess function inside. However, this approach will not display the "wait screen" after triggering the process that is towards the end of the process to "buy time" and to allow the previous request that the user clicked Approve or Deny to disappear when the user clicks FINISH on the wait screen and returns to the site interface. Therefore, the user experience is returning to the site too early to still see the original request on the screen after the user already chose Approve/Deny.
Then, I tried using submitLink which allows startProcessLink and wrapped it in a cardLayout in lieu of button widgets. This approach allowed my chained process to display the wait screen. However, the drawback is there is no way for me to have a confirmation window pop up.
The business user's feedback is having the confirmation window pop up is more important. I want to ask the community if there is a better solution that allows me to have the best of both worlds?
TIA
Discussion posts and replies are publicly visible
To start a process my first approach is, to use record actions. Did you consider that?
Then, what is that "wait screen" and that "confirmation window pop up"? Can you help me with some details?
If you want a confirm message in your window, please go through the buttons, in your buttons there is a parameter "confirMessage", if you configure that one you can see a pop-up window in your window.
You can also configure a startProcessLink() and in the process model you can configure a interface for using like a confirmation window.
Hi,
We need more details about your use case, but based on my understanding, I'm sharing this,
You can use a combination of a buttonWidget(submit property), start process, a process report to track the process status, and conditional UI components to display the completion status.
Start Process:
Wait Screen and Refresh Mechanism:
Hi Stefan, I always like listening to your podcast!
Strongly agree with you that using record actions is the first choice but at this point in time, I don't have enough time left in the project to revamp the buttons.
I originally thought that under the Save section in a button widget could not accept startProcessLink but only startProcess, which was not triggering the wait screen that is a task assigned to the logged in user towards end end of the process model.
Wait screen is a task assigned to the logged in user to buy time for not returning to the site interface too quickly in order for the original request to disappear.
Confirmation pop up window is the confirmation message in a button widget set up
I will try using startProcessLink
Thanks for the tip. I will try it
Hi, I will try using startProcessLink in the save section of buttonWidget
I tried using startProcessLink in the button widget and got an error:An error occurred while executing a save: Expression evaluation error: You must specify a variable to save into, such as ri!name << fn!sum. Received: StartProcessLink.
I guess I just cannot have StartProcessLink in a button widget but only startProcess
You can use cardlayout() as a button and there has an option to configure the link. There you can keep a!StartProcessLink()
I tried that but the feedback from the business is they feel the confirmation box is more important