Hi,
I’m trying to use the forms activity to let users be able to continue or quit the workflow. How do I know which button the user clicked on?
I tried googling it, but it seems I dont have that many options in the properties panel:
Hi @MDS
While creating the form, you will be able to spot a property called ‘selectedButton’ in which you can store the data of the Ui element that user clicked.
On configuring the same, you can get the data of the button clicked.
Hope this helps,
Best Regards.
I guess in the latest one you dont have that option…
You can use event triggers and associate trigger with each button and in the process depending on trigger decide the button clicked
Cheers
This is not an option in the latest form designer 
Mind giving me a quick rundown on how this would be done? 
Can be retrieved from returned forms output and its Action Property Value
How exactly? I couldnt find any output.
Have you found a solution for this?
+1, looking for an answer to this.
I tried adding an argument with the button field key value into the Show Form activity, but once I save it just goes back to the original keys it imported from the form.
Working with Create Form Activity:
2 Buttons are configured with submit Action
Output Settings
Result
Selected Button, or respective Button component ID = true
Working with Action Forms:
retrieval from returned TaskObject
For any new questions we would recommend to open a new topic with details, due there were some evolutions and we would prefer to address the details from the case
I think I have found my answer - just to clarify, I am looking at the new forms, in version 2023.4+
And the answer is that UiPath have completely re-done the concept of forms in the Triggered attended automation framework.
There is a course on the Academy that’s called Attended Automation Framework Triggers and Forms in Studio (v2023.4) and it tells you all about how the new forms are used.
Here is also a link to a youtube video that explains the scenario
In short, you don’t need to retrieve an argument that tells you which button was clicked, you need to build a separate sequence with a trigger which will monitor the button clicking and execute a sequence once the button is clicked. You will need UiPath.Form.Activities for this.
In my example, I had a Submit and Reject button. I created a new trigger sequence and placed the trigger as the first activity in the sequence and got it to monitor the event “Submit clicked”. I created another trigger sequence for the “Reject clicked” event. Once you’ve got all of your triggers set up, you place a “Run Local Triggers” activity in the Main.xaml and when it’s executed, it will look for when a trigger is executed to continue with the relevant sequence.
I hope this helps.
Hi, thanks a lot for sharing, I am sure your info will help someone. I actually watched this course several times already and worked with forms quite a lot. The reason I was asking is that sometimes you simply want your automation not to be trigger-based, because it makes adjustments to your logic at all, so I thought maybe there is still a way to just get the button clicked without creating any triggers.
They are not talking about the “Create Form Task” activity.
They are talking about the regular forms activities. You choose the “Show Form” one, then you have a drop down, select the existing one to display from the list or you create a new one from there.
We have to thank UiPath team again for the confusion (“Long Running” → form related task set, and “Forms” → form related task set), and also Peter answer is misleading, not counting that it took 7 months for him to reply to the request to clarify what he was talking about…
Official UiPath docs about this are rather clumsy to me. Trying to get some support via opening tickets about this is painfully slow, too.