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

Question

Question

Forms 10.2 Read-Only Form Approval

Forms
Updated October 17, 2019
asked on January 19, 2017

It doesn't seem that you can approve or reject a form in 10.2 if the user task has the option "Make form read-only for users the task is assigned to" checked.  As far as I know this has always worked and is our preferred way of having forms submitted so that the approver can't change data.

Is this change by design? If so, what are my options?  I don't really like the idea of having to go through each form and make individual fields read-only on the approver form.

0 0

Answer

SELECTED ANSWER
replied on January 19, 2017

I see. Thanks for the extra detail; I can now reproduce this as well, and consistently. I've filed SCR 153757 to look into and address this. If you'd like you could still proceed with having a case created so we can notify when the ticket is resolved, but there won't be much to be done in the case itself.

Thank you for bringing this to our attention.

0 0

Replies

replied on January 19, 2017

Is the form being assigned to more than one person? Often overlooked is the need to click the "Assign this task to me" button in the top right, before any action can be taken on the task itself.

0 0
replied on January 19, 2017 • Show version history

No, just a single user.

 

If I set the form to not be read-only, the approval buttons work fine.  If it's set to read-only, nothing happens when the buttons are clicked.

0 0
replied on January 19, 2017

From a cursory attempt at reproduction, I cannot. I set up a user task with options "Approve" and "Reject", and specified that the form should be read-only to the assigned user. The form itself had a single single-line field and no theme, rules, or custom code of any sort. After typing into the field and submitting, for the user task the form was read-only but I could still add comments and choose either Approve or Reject.

The form and process were originally created in Forms 10.1 (can't remember which update) though I did only add the read-only setting after updating to Forms 10.2.

In your form, do the approve buttons seem disabled, or does it just seem that nothing happens when clicking them? If they seem disabled, are you able to enter text into the Comments field? If they do not seem disabled but nothing happens when you click them, check the browser console (F12 > Console tab) for errors when clicking the buttons.

0 0
View 4 previous replies
replied on January 19, 2017

I don't have any custom CSS/JavaScript on the form I'm testing with.  The buttons don't appear disabled, they just do nothing when clicked.

I made a copy of the user task and also recreated one from scratch within an existing form and it doesn't solve the problem.

However, if I create a new process I can Approve/Reject when it's set to read-only.

All of my processes were created with Forms 9.2, with the exception of one that was created with 10.0, I believe.

0 0
replied on January 19, 2017

I'm still looking in to this, but I think it might have to do with hidden and required fields in Field Rules.

0 0
replied on January 19, 2017 • Show version history

Could you reach out to your reseller to open a Support Case and provide us with the XML export of a sample process that has this behavior? Have them reference this thread.

0 0
replied on January 19, 2017 • Show version history

I'll do that, but what I've noticed in testing is that the problem occurs when there's a hidden radio button field that's set to required.  I can approve a read-only form when all hidden radio fields are not required.  All other required, hidden field types don't present any problems.

The second I set a hidden radio field to required, I can't approve the form if it's set to read-only.

I verified this with a brand new process that contained nothing but a hidden radio button field, I couldn't approve that one either.  I had to turn off validation in order to submit it, however.

0 0
SELECTED ANSWER
replied on January 19, 2017

I see. Thanks for the extra detail; I can now reproduce this as well, and consistently. I've filed SCR 153757 to look into and address this. If you'd like you could still proceed with having a case created so we can notify when the ticket is resolved, but there won't be much to be done in the case itself.

Thank you for bringing this to our attention.

0 0
replied on January 19, 2017

No problem. In the meantime, I just put some JavaScript in place to remove the required attribute from all radio fields when it detects it's in an approval window. 

1 0
replied on October 17, 2019

I am running into this same issue on Forms 10.2. Not a problem in 10.4. Is there a fix for this in 10.2 or will the client have to upgrade?

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

Sign in to reply to this post.

Details
Related Posts
Loading ...