InfoPath Dev

In a test enviroment we have developed a Cheque request InfoPath form which uses authorisations contained within the form itself (uses different views at different stages of the form's journey through the approval process), the question I have is regarding how to maintain confidentiality of the cheque request form when it is has been posted to the SharePoint library, this is because some cheque requests will contain confidential information.

Our in-house SharePoint administrators are saying that in order for the person raising the cheque request in InfoPath when they submit to SharePoint they will need access rights which could allow them to see other cheque requests?

New Cheque requests will be created by using a content form type so the user will not be navigating to the document library but if a user wanted to see the contents of the library my understanding is that they could. I have come across some custom code that can be added to SharePoint but we are trying to avoid using custom code in our SharePoint2010 solution.

Any ideas would very welcome as this is the last item to resolve before I can go live and start to publish InfoPath forms via SharePoint2010

Thanks
Kirk

I'm afraid that if the user has permissions to write to a library, they have access to see the other items in it. In lists, we can set security to only allow users to see their own items - this doesn't exist for libraries.

Is workflow an option? Perhaps when XML are added, you could use a workflow to move them out to a secure location?

Hi Hilary,

Thank-you for your reply and possible options for solving this problem.

The work-flow would normally be an option for us to use but a problem with this approach I believe for us is that the authorisation for the Cheque requistion form is contained entirely within Infopath so the the authorising Manager recevies an e-mail with a link to the form in the SharePoint library, they open the form from the e-mail authorise the form which triggers a second e-mail sent to the finance/accounts department advising them their is a new approved form for processing. As the form moves through the various stages I am not sure how easy it would be to move the form on to another library and still maintain the authorisations within the InfoPath form.

This approach of containing the authorisations within InfoPath (as opposed to using workflows/task in SharePoint) was something I picked up from the book - Step by Step - Using Microsoft InfoPath 2010 with SharePoint

Regards

Kirk