Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Subjective Question

  Asked By: Anish    Date: Dec 04    Category: Sharepoint    Views: 863

In our design of a corporate SharePoint site, I will be implementing an InfoPath 'Site Request' form. Our thinking is that we put the form into a forms library on the Sites page and have a link on the Home page, but somehow that idea seems sort of incomplete. Any comments?



5 Answers Found

Answer #1    Answered By: Tejaswani Barve     Answered On: Dec 04

heather is the master - i owe a lot of our site  provisioning process to her blog

we didnt see the point in using infopath  in the first release of our "site request". we actually just did a survey and made it available to all domain users. one day when we have the questions and the process worked out better we would switch to infopath..

Answer #2    Answered By: Harshita Padwal     Answered On: Dec 04

The purpose is to allow users to request  a site  and have it forwarded to our site admins without having to 1st go thru User Support, etc.

Answer #3    Answered By: Jennifer Jones     Answered On: Dec 04

Just remember that if a user requesting a site  does not have infopath  installed on his/her computer, they cannot open or complete an infopath form, regardless of its location.

Answer #4    Answered By: Annie Norris     Answered On: Dec 04

Assuming some kind of workflow – such as someone requests a site, someone else needs to approve it, then the site  gets created – you could design  the form  with this in mind. And when the site request  is approved, event handlers on the form library  could create the site, configure any web parts accordingly, create the appropriate security groups, and add users to those groups.

If the forms  asks the right questions, you could totally streamline any complicated procedures around site creation.

Answer #5    Answered By: Chadd Hahn     Answered On: Dec 04

Do you already use InfoPath on the site? I assume this won’t be a problem with any of your end users and that everyone has it available to them.

If not, one thing you could do is create a SharePoint list. Create columns for all the information you need, for example ours include approving manager info and billing info, site  owner name and contact, name of site, desired URL of site (/sites/yournamehere), list of needed contributors and readers to add, checkboxes to include in site search and sites  listing, etc. The list is setup to allow Readers to add items and it has alerts and all that good stuff so the support staff is notified when there is a new list item. Once a user submits a request  it goes through the processes (the list also includes a Status column) to get approved for creation, then actual site creation. It sounds like a lot, but once the list is set up, it really helps streamline the process and we have an excellent record of all of the sites that have been created and who is the content owner. Since it is a list, it can be exported to Excel, sorted, filtered, etc. Rather handy.

Didn't find what you were looking for? Find more on Subjective Question Or get search suggestion and latest updates.