You are viewing limited content. For full access, please sign in.

Question

Question

Difference Between Submit & Approve Buttons?

Forms Version 9
Updated March 24, 2014
asked on February 5, 2014 • Show version history

When editing a User Task, there are three button options: Submit, Approve, and Reject. What is the difference between the Submit and Approve buttons?

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on February 5, 2014

That is correct. For example, we have some internal processes here at Laserfiche Corporate where the approver can take three actions: they can approve, they can send the form back to the submitter to make edits, or they can reject outright. So having three buttons available for configuration comes in handy. Their names as they appear in the User Task don't matter. What matters is the value you give them. The values correspond to the "Actions" in the process when you define conditions.

0 0

Replies

replied on February 5, 2014

The only real difference between them is the "action" value they hold in the internal Forms System. You can rename Submit to be Approve and Approve to be Submit and as long as you set the routing properly, then everything will work just fine in your process modeler.

0 0
View 3 previous replies
replied on February 5, 2014

So what "Action" value does the internal Forms System hold for them?

0 0
replied on February 5, 2014

The Action value is the original button name. Submit button always means the action will be "Submit" to the system, but you can decide what that button is named and does inside your process.

 

"Submit", "Approve", and "Reject" are the three button types and they have the same Action value as their names.

0 0
replied on February 5, 2014

So really the only reason the Submit and Approve buttons exist is to make it possible to have a total of 3 buttons when you add in the Reject button?

0 0
APPROVED ANSWER SELECTED ANSWER
replied on February 5, 2014

That is correct. For example, we have some internal processes here at Laserfiche Corporate where the approver can take three actions: they can approve, they can send the form back to the submitter to make edits, or they can reject outright. So having three buttons available for configuration comes in handy. Their names as they appear in the User Task don't matter. What matters is the value you give them. The values correspond to the "Actions" in the process when you define conditions.

0 0
replied on February 28, 2014

I just noticed while configuring a form process that I had a the Submit option selected for a user and the form was marked as read-only at their step. When the user viewed the form, they did not have any options to choose from. I had to uncheck the Submit option and select the Accept one instead for a button to appear for them. Is that how it is supposed to work?

0 0
replied on March 24, 2014

Is there a way we can make the the comments field with Approval and Reject option as required field. Thank you!

 

Best,

Himanshu

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...