InfoPath Dev

Hi All , Am glad to be here and posting my first question to Infopath experts out here :-). I am a complete newbie to Infopath and that being the reason i choose this Forum to post my question....Please suggest/Help me to move it to respective threads if this is not the appropriate one. I have been assigned a new Project which deals with developing On-line system to Raise New Job request within specific department. Currently the process is all done manually which takes longer process time and also prone to human error. I have basically planned to develop the application into three Modules , Namely , 1. Requester Module ----> Person who raise New Request 2. Manager's Module ----> Person who Approve/Reject new request 3. Engineer'g Module ----> Person who process/Work on this request I have managed to create Infopath Form design for the first Two Module's.But i have no idea on how to proceed further from here. I have created a SharePoint List namely Employee , Job Details . I want to store the information which user enter in the info path into these two share Point List. Infopath form consist of Two section , First being Requester detail (To be stored in Employee List) and JobDetails (To be stored in Job Details list). I have read few forums which demonstrate how to store info path form in Document library, but that is not what i am looking for.I just need to store the info entered by users into these List |(Just like we store data into SQL db from web application). Please let me know your valuable suggestions guys. I know i have a long way to go to accomplishment this project .....Learning is always fun when heading in rite direction :-) Thanks in advance.

Off the bat the easiest way to do this would be to use a hidden form status field on your form. This field has a default value and then it is set to another value on the pressing of a submit button on the form.

i.e.
1.Draft.
2.Employee Request
3.Manager Approval
4.Job Complete

Depending on how you add your manager's name or the enginee'rs name you could have a form load rule so that only X can open each view. Each stage is a view within the form.

The forms are submitted to a SharePoint form library. Publish only the columns in the library that you want to read without opening the form. In the library you can create multiple views of the information contained within the form depending on who is going to view the form.

There are many ways you could take it from here i.e. displaying and filtering information on a web part page, workflows etc.

 Hi Wilkies, Thanks a lot for the brief explanation.I have managed to created multiple views and submit the form into a Form Document library and make alteration to view only the fields which are necessary excluding the form view.Now my question is , Can i store the Infopath data directly into a SharePoint list ?Or is it only possible to load the form into sharepoint form library and make modification to view required fields as in List.I have a Form Library named "RequestInfo" --- >I have successfully published form to this library I also have a SharePoint list named "EmployeeInfo" ---- > Can i store the data related to employee iformation from the Infopath form to this list and not into form library ?I hope you can clear my doubts on these.RegardsAshesh

 

In ref to the above that I received via email.

Pretty much all controls (fields) can be published to a SharePoint library.

This is what I do.

Publish all required columns from your form that you require to the form library. They all by default get published to the All documents view. I also add any calculated columns to this view too. - This is my (admin/designer) default view.

Then I'll create several other views of the information. This is where you cherry pick the columns and present the required information. Permissions etc. are taken care of either by SharePoint groups or more often via a workflow. i.e. you can only see forms that you have permission to see when you are named as the manager.

Once all views are set up, I'll change the default view to my documents. This only shows documents that you created. It depends on the sensitive nature of the information you are publishing.

If you want to store information from the form in separate lists you can do it, but you'll need to write a SharePoint designer workflow for that. It depends for what purpose you need your EmployeeInfo list.