InfoPath Dev

Hello, We have a form that once submitted we do not want them to be able to open the form again unless the status has changed to rejected. How are people doing this currently? Maybe the best method might be that once submitted, there is an email sent to a supervisor and/or head for approval(done currently). If I could check to see that the status is this and the person opening the form is contained in one of the 2 dropdowns let them in. Is that possible do you think? Thanks for the help.

A simple way could be to check the status on the form if that is available for you and if the status is not equal to rejected then display a read-only view of the form instead of an editable view.  This could be easily set up within InfoPath instead of having to work through permissions to block opening the form itself.

wow that was a quick response and I like your suggestion. I should note I am pretty new to this too so forgive me in advance. So if i create a read only view, is it possible to hide the editable view from the submitter? I will have to keep track of that somehow i suppose which I am not certain how to do yet? Also, i will need to know who should go to what view. The assigned supervisor should go to the editable view and all others to the read only. So when a form is first created, the status is blank. At this point i need to determine who opened the form and save there email address behind the scenes. When it is opened next by the supervisor, if the persons email address who is opening the form equals that of the dropdowns selected value (email) then open in an edit mode otherwise read only for all. This is how I am thinking it should work? Thanks again.

There are form load rules in the Data tab which you can use to switch views when the form is opened.  Just create a rule to check if status = rejected then switch to your read-only view.  This will prevent users from seeing the editable section.  Don't forget to disable the views dropdown in the ribbon as well (File -> Form Options -> Web Browser Category -> Uncheck Views).

If you know who the supervisor is, you can use the userName() function to determine the current user and perform different logic based on who is viewing the form and perhaps what state the form is as well.

Sounds like a pretty complicated form for your first InfoPath experience :)

Thanks again and ya this has been a good starter one for sure. Might as well make my brain work right away! I like it. Some neat stuff. I played with username function and that returns the username which will be good to know for future I think and I haven't figured out yet how it will help here just yet. And here is what I thinking. This form if rejected will allow the original request to again modify it. However outside of initially submitting it and rejected it will be read only. This should be solved with the view you suggested. The next thing is, there has to be potentially 2 groups of folks (there names and email addresses are stored in 2 dropdowns or 2 lists in the form). I would like it that I could get the user who is accessing the form's email address and if it exists in one of those 2 forms shoot them over to the form for modification. I think my biggest thing here is how to get the user email address?