General

Re: Visibility of buttons, depending on the user function

Hilary Stoupa — Wed, 30 Oct 2013 15:21:51 GMT

I'd use user roles, since this sounds like it is not a browser form. More info here: http://office.microsoft.com/en-us/infopath-help/introduction-to-user-roles-HP010165118.aspx

Re: Visibility of buttons, depending on the user function

Tesoro — Wed, 30 Oct 2013 14:39:59 GMT

no one? Please. Is there any way to resolve my problem?

Re: Visibility of buttons, depending on the user function

Tesoro — Mon, 28 Oct 2013 09:08:59 GMT

Any advice? Please, please, please... :)

Re: Visibility of buttons, depending on the user function

Tesoro — Thu, 24 Oct 2013 11:50:41 GMT

The process workflow looks as follow: 1. Initiator fill in the form press the "SEND FOR APPROVAL" button. Form is send to Manager via email. 2. Manager verify the form (can make changes) and press the "SEND FOR PROCESSING" button to Operation department. Form is send via email to Operation Department. 3. Operation department press the button submit and form is saved on a SharePoint. Now, when initiator fill in the form he has visible all 3 buttons. As I wrote before, I would like to do something to visible: 1. Button 1 only for those who initiating the form but not visible for Manager and Operations 2. Button 2 only for Manager who approves the form but not visible for Initiators and Operations 3. Button 3 only for Operations who submit the form but not visible for Initiators and Manager I forgot mention that I use infopath 2010 to design form but it will be used also in infopath 2003 and infopath 2007 Could you tell me step by step how to to this? or make an example for me on the attached one? Thank you in advance

Re: Visibility of buttons, depending on the user function

wilkies0106aw — Thu, 24 Oct 2013 08:02:05 GMT

Many ways to skin this cat.

1.If you're form has different views, only put the applicable button on its correct view. Use a workflow to strip permissions where appropriate. Thus an Initiator could go into a form when it's at the Manager stage.

2. You could put each button into its own section and using rules hide the button depending on who is looking at the form (for this you can compare username against a manager field or connect it's viewing rights to a list.

It really depends on how the form is going to be used, I've found which way I go about this. i.e. if the manager spots an error or something, who updates the form, the initiator or the manager?

Visibility of buttons, depending on the user function

Tesoro — Tue, 22 Oct 2013 14:21:30 GMT

HI everyone, I am not sure where I should put my topic so I place it here. I am designing an InfoPath form for my office. I have a form which has 3 submit buttons: 1. Send for approval (this button sends the form to Manager via email) 2. Send for processing (this button sends the form to Operations via email) 3. Submit (this button save the form on the SharePoint) I would like to do something to visible: 1. Button 1 only for those who initiating the form but not visible for Manager and Operations 2. Button 2 only for Manager who approves the form but not visible for Initiators and Operations 3. Button 3 only for Operations who submit the form but not visible for Initiators and Manager Should I use rules or something like that? Please tell me what and how should I do it. Ps. I attached an example form Please redirect me if I should put the topic in a different place