InfoPath Dev

I know MS has screwed us on this one, but I was wondering what is the best agreed upon solution to allow users to not only submit an InfoPath form to a form library in SP, but also then to restrict them to only be able to view and edit their own forms, rather than everybody's forms as the 'Contribute' permissions allow?

Currently, we are manually editing the permissions for each item/form before approving the form, so that only Site Owners and the user who created the form have access to the form, and manually removing the Site Members (Contribute) permissions. We have set the permissions so that while the form is still in 'Pending'  or 'draft' status, only Site Owners and form creators have access to the form, but of course this option is not available once the form is approved.

This is an extranet site and we have already had one malicious attack, and we already have over 400 forms in the library, so I definately need the best 'coded' solution to ensure maximum security...

Which coded solution do you like the best? Has anybody done this before in Visual Studio with a custom workflow using C#?

Thanks in Advance,

David

Hi David,

You can create customized views and define filters. In that case you can filter the field "Created by" with [Me]. That means that the view will filter the information to the current user with only forms that it has created.

For more information about it: Custom Views in Windows SharePoint Services (Figure 4)

I don't believe customized views are secure enough...if a malicious user knows enough about hacking sharepoint they can just type in the path to the forms library All Doucments view: http://myserver/mysite/myFormsLibrary/Forms/AllItems.aspx and view confidential information, right? Like I said, we have already had one malicious attack.

I am looking for the best solution to programattically remove the Site Members SP Group 'Contribute' permissions for the form once it has been submitted, and add the form creator individually with 'Contribute' permissions... or a similar more effective solution.

Anybody done this before in Visual Studio with a custom workflow using C#?