InfoPath Dev

Hi,

I have a fairly standard process where my form is going to be filled in by a requestor, sent to an approver and the on to an actioner (approve) or back to the requestor (reject). Simple so far.

My questions is, when the form goes to the approver is there a why of making all of the fields read only apart from the 'approval' section which obviously needs to be filled in. I know that you can select that a view be 'read only' however that will lock out the approval section as well. And yes, i know you can create another view and then manually select each field and turn it into Read Only but given the large number of fields on my form that is time consuming.

I was really wondering (for the future really as this is something going to do a lot) whether there is a quicker way (maybe turning all fields read only automatically and then manually changing the ones I need to back to edit)

Cheers.

You can set up conditional formatting on fields and controls based on the user's role. This, of course, assumes that you are using InfoPath user roles. Here is a link about InfoPath user roles (also read this); once set up, just add conditional formatting based on the user who opened the form. Good luck!

Hi Ernesto

Thanks for the reply but there are literally hundreds of potential approvers so user roles isn't appropriate.

I think I am going to have to change every field manually - which is a pain but doable.

When there is a large group of people in one group it is unrealistic to add them one by one to the form, but I imagine one option (if the "approvers" group, for example, has stable membership) is to set up an AD group and manage membership via that AD group.

Anyway, that's all I can think of, sorry I couldn't help more!