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

Question

Read-Only dropdown field does populate the field in the LF client once the form is submitted.

Ideas

Updated September 28, 2017

asked on September 28, 2017

I'm working with our vendor and we're trying different things that might work, but wanted to see if anyone here has had to deal with the same scenario. We have a dropdown field that needs has a requirement that the selected option cannot be edited, however, if we set the field to read only, we're able to make a selection, but when the form is submitted, the LF client doesn't populate the field with the selected value. Adding js to make the field RO doesn't bring up the dropdown list to pick from.

Anyone else had to deal with this issue?

0 0

Replies

replied on September 28, 2017

Hi Willie, what you need to do is to create a duplicate of the Form in forms (ie: external and internal). Assign the external form to the Start event and the internal form to the task. Set the drop down field on the internal form to read only (just use the Read Only check box feature on the field, no JS). What will happen is that the user can use the drop down but the internal users will see it but not be able to change it. It should save into the LF Client Metadata fields fine unless you have a rights restriction on the field

0 0

replied on September 28, 2017

Interesting. I will give that a try and see how it behaves. Thanks and I'll let you know how it goes.

Question

Question

Read-Only dropdown field does populate the field in the LF client once the form is submitted.

Replies

Sign in to reply to this post.