Question

Can the image of a button remain on a form once a form is re-assigned to the next task?

Forms Version 10

Updated January 28, 2021

asked on January 27, 2021

Hi.

Is there a way to configure a forms process so that the image of a button a user has clicked on can remain on the form once the form is re-assigned to the next task?

For example, the user (approver) may have a choice to click on either an Approved button or a Denied button. If the user clicks Approved, can an image of the Approved button be kept on the form once the form gets re-assigned? The next user (approver) would like to see this show up on the form before making their decision and submitting the form. Since the second approver needs to see what decision the first approver selected, using Workflow after it is submitted to the repository will not work.

This wouldn't necessarily have to be an image of the button, itself. If it can be configured to stamp "Approved" or "Denied" (based on the button clicked on by the user) into an HTML field on the form or something like that, that would work.

Thank you!

Rob

0 0

Replies

replied on January 28, 2021

One solution could be a step passed Jason's idea.

Have a field at the bottom of the form for approved or denied instead of using the buttons. (Or create your own buttons using JS and tie that to a field + submit)
Create two large custom HTML fields at the top with clear messages and colors
- One big green one saying "This form was approved"
- One big red one saying "This form was denied"
Use a field rule to tie the drop down choice to show the correct custom HTML field at the top of the form.

When users would see this form later, the correct custom HTML would show the big message at the top of the form.

2 0

replied on January 27, 2021

What I usually do when a process needs to keep track of the "status" like that is I'll use a field like a dropdown or radio button instead and just have a single submit button.

Either that, or I'll add a hidden field on the first form, attach a click event handler to the action button that populates the field, then display that field on the subsequent form as read only.

1 0

replied on January 27, 2021 • Show version history

The user should be able to see the Action History in the Details pane showing previous approves selection as well as any comments entered in the comments field. This is built in functionality.

1 0

replied on January 28, 2021

Hi, Steve and Jason

Thank you for your replies! My apologies - I forgot to include an important detail in my original post. The goal is to provide the users with a very obvious, very noticeable visual cue on the form to help them quickly identify the decision from the previous step in the process. They do already use Action History and would prefer to avoid adding more text-fields to the form.

Thank you!

Rob

0 0

replied on January 28, 2021

If you want something on the form to change dynamically based on whether the previous task was approved or rejected, and not just the action history, then you have no choice but to add a field to the form to track the value, even if the field is hidden.

That doesn't mean you need to display that field because you could just use it in field rules or JavaScript to make handle what's displayed, but one way or another you need it to be tracked into a variable that can be accessed by the form.

0 0

You are not allowed to follow up in this post.

Question

Question

Can the image of a button remain on a form once a form is re-assigned to the next task?

Replies

Sign in to reply to this post.