It would be very helpful if the Direct Email Approval option could also store a reason when there is a rejection so that if the initiator is rejected, that reason can be used as a variable in the notification email.
Discussion
Discussion
Hi Angela,
Which mode of direct email approval are you using?
This is not support with 'Click an action button in an email to complete tasks' mode yet, while with 'Reply to an email with the action button text to complete tasks', optional reason could be replied in second line with direct approval as suggested in email notification.
You can perform this task via email by replying to this message with one of the following actions as the first line of the email body: Approve, Reject, Submit. Optional comments (up to a maximum of 500 characters) can be typed in the second line.
I am using the button option. I thought about the replay but where would the second line be saved so it can be used as a variable in a later step?
@████████ is this in the Forms documentation?
@████████
The second line will be treated as user task comment when processed, and like other user task comment, it can be retrieved in later step by process variable token 'Previous submission -> Comment'
I will record support comment for 'Click an action button in an email to complete tasks' as feature request though
@████████ This is not explicitly introduced in Forms documentation, while indicated in sample in Direct Approval (laserfiche.com)
Could wording be added to explicitly talk about this ability?
Thank you for putting in the request to add this with the buttons. I don't suppose there is the ability to have some forms use the buttons and other forms use the Reply with an action? I understand the setups are very different.
Yes, currently only one mode for all user tasks in the system.
Request made to update the corresponding online help page.
I like the idea, just not sure how it could be implemented. Forms would somehow need to know what information to pull from the email to use as the reason.
I agree it would be tricky. Either a radio button or free form field would have to know to pull from the email and where. Perhaps that could also show in the email as well. Almost everything has a rejection option and without being able to provide a reason, it makes this option useless. My current work around is just use verbiage explaining to reject the form they have to open it, but the button still shows so it gets confusing if people don't read the email completely.
I second this request. Rejected forms need to include a reason that can be provided to the person who submitted the form. Without this, we aren't able to use Direct Approval for forms with a Reject option.