In previous versions of SharePoint, Outlook was simply a handy tool for storing local copies of specific types of SharePoint lists, such as contacts, tasks, and calendar lists. It was great for offline access to these types of SharePoint lists, but it did not allow the user to update them locally and then replicate that modification back to the SharePoint server. But the new Outlook 2007 is very different. It is almost as if this version of Outlook is acting as a SharePoint client, besides being a mail client. It brings so many enhancements to SharePoint users, and for that reason, I recommend that even if, for some reason, you choose not to implement Office 2007, you implement Outlook 2007!
It is definitely possible to use MS Outlook 2003 with SharePoint 2007. However, it will not have all the new and exciting features that Outlook 2007 offers. Below is list of the standard features that Outlook 2003 offers:
Task lists: Outlook allows the user to download a copy of tasks lists for offline usage. These tasks are read-only and changes cannot be replicated back to the SharePoint server, not even with SharePoint 2007.
Contact lists: The same thing is true for contact lists. The user can download a read-only copy of a SharePoint contact list, but it cannot be changed in Outlook 2003.
Calendar lists: Again, same thing is true; you can only download a read-only copy of SharePoint's calendar lists.
Alerts: With Outlook 2003 you can receive and use incoming alert messages sent by SharePoint. You can also view and manage all your alerts defined in SharePoint.
So, Outlook 2003 is good if you are happy with downloading SharePoint lists as read-only copies. But if you need two-way synchronization, then this Outlook version will not do.
The best Outlook edition available for SharePoint 2007 implementation is Outlook 2007. It has a number of new and exciting features that relate to SharePoint 2007. Note that with SharePoint 2003 you will not have these extra features, even with Outlook 2007! Below is a list of the features available when you combine Outlook 2007 and SharePoint 2007:
Task lists: With Outlook 2007, you get full two-way synchronization of task lists in SharePoint. You can view, add, and modify tasks in this list, just like any Outlook task list, and all changes will be replicated back to SharePoint. These tasks will also be displayed along with other Outlook tasks in Calendar view.
Contact lists: Another list type that can be replicated from Outlook 2007 to SharePoint 2007. Its content can be updated, including adding new contacts or deleting existing contacts. Any changes will be replicated back to SharePoint. Outlook will, by default, search for users also in these replicated SharePoint contact lists, when a user searches for recipient names.
Calendar lists: Use Outlook 2007 for two-way synchronization with Calendar lists in SharePoint. Any changes to this list in Outlook 2007 will be synchronized back to SharePoint within minutes. The copy of this calendar can also be used as an overlay on top of other Outlook calendars. You can also send HTML-formatted copies of replicated SharePoint calendars with this version of Outlook. See Figure 7-3, which shows a SharePoint calendar named SIS. The calendar has been converted to an HTML-formatted e-mail.
Alerts: With Outlook 2007, you can receive and use incoming alert messages sent by SharePoint.
InfoPath forms: Send forms created by InfoPath 2007 as e-mail. The recipient will see the form directly, and can fill in the form and then return it. These forms may then be stored in a SharePoint library.
Offline content: You can download a complete library with documents, images, or forms to an Outlook folder. These downloaded files can be viewed and edited offline. If a document is changed, it will also be stored in the users folder SharePoint Drafts, located in My Documents. The next time this computer goes online, and you open the local copy, SharePoint will ask if you want to upgrade the server copy, that is, the copy stored in the document library in SharePoint.
Send to: A new feature in all SharePoint 2007 libraries is that you can use Outlook to send a link to a document, image, or form. The recipient will open the document in read-only mode and can then choose to edit the document, if necessary. This is much smarter than sending complete copies of documents, since you will retain just one single copy of the document, and you will not "litter" your mailbox with large mail attachments.
Workflow integration: e-mails with instructions sent by workflows in SharePoint, for example Approve instructions, can be managed directly in Outlook 2007.
Record Management: You can forward copies of e-mail directly to SharePoint's Record Management server, where these messages will be stored within a specific record. This requires MS Exchange 2007.
RSS reader: Outlook 2007 has built-in support for managing Really Simple Syndication (RSS) feeds. This can be used to display all new items in a SharePoint customer list or documents in a project document library. It can also be used to display information in any standard RSS source, such as news from Internet web sites, or virus warnings from antivirus vendors' web sites.
The list above is extensive, and to see how to use some of the most exciting features, you should try the step-by-step instructions in the Try It Out below. As always, it is easiest to explain how it works by using examples. The user Adam is working at the company Filobit; they recently deployed SharePoint 2007 and MS Office 2003 Professional Plus, which includes MS Outlook 2007 and MS InfoPath 2007. Adam uses the SharePoint site SIS a lot, since it contains the information he needs to do his work. Now and then, Adam is away from the office, so he will be off line, and therefore cut off from the SIS site. But by using the new offline feature in Outlook 2007, he will still be able to view both documents and images offline. The Try It Out shows how Adam does this.
Try It Out: Download SharePoint Libraries to Outlook
|
To summarize, Outlook 2007 allows the user to take information stored in SharePoint libraries offline. This information may also be edited offline and when the user goes online again, he or she will be offered the opportunity to update the server. If there is a conflict, Outlook 2007 will discover this and give the user several options on how to resolve this.
The offline functionality described above is excellent. But sometimes, you do not want to make a copy of a complete library, especially if it contains thousands of documents.. This is where RSS comes in handy, since the information listed in a RSS folder is a short description plus a link to the documents in SharePoint, not the documents themselves. To open a document, just click the link. This requires that you be online and have access to the RSS source, the SharePoint library.
The story behind RSS is this: This XML-based protocol was first released in 1999 by Dan Libby of Netscape. At that time, RSS stood for Rich Site Summary. Its purpose was to create an easy way for a program to subscribe to updates from an information source, for example news headlines published by a news site, such as the Washington Post or CNN. The term used here is RSS feed readers (or aggregator), that is, the program that receives the information feed. The RSS release used today is version 2.0, released in 2002, and its abbreviation now stands for Really Simple Syndication. There are actually several versions of RSS available, but the most commonly used is RSS 2.0
Both MS Outlook 2007 and MS Internet Explorer 7.0 have built-in support for RSS 2.0 and can be used as feed readers for any web application that supports RSS 2.0 feeds. Many of the lists and libraries, including News pages, in SharePoint 2007 support RSS feeds, that is, an Outlook 2007 client can set up a RSS feed reader to any SharePoint list. The following steps describe how the user Adam will configure Outlook as a RSS feed reader of the document library Info in the SharePoint site Sales.
Try It Out: Use RSS to Display List Content in Outlook
|
You can change an existing RSS feed configuration in Outlook 2007 by opening the Tools menu, then selecting Account Settings. Open the RSS Feeds tab. It will list all existing RSS feeds, and here you can change any of these feeds by selecting them and clicking Change. This will bring up the same configuration dialog box as depicted in Figure 7-9. You can also delete an RSS feed by selecting it and clicking Remove. To create a new feed, click Add, and enter the URL to the RSS source. If you want to change the default folder location in Outlook, click Change Folder, then select another Outlook folder for the RSS feeds. You can also create a new database file that Outlook will use for storing all RSS feeds by clicking New Outlook Data File (see Figure 7-10).
NOTE
When creating a new Outlook data file, you should choose the option Office Outlook Personal Folders File (.pst), due to its unlimited size, unless you want to use this PST file later in Outlook XP or earlier editions of Outlook.
All RSS feeds are stored in a local mail database, known as a Personal Store (PST) file. By default, Outlook will create one single PST file that will be used for all information retrieved from SharePoint, including offline synchronization of document libraries, task lists, and RSS feeds. The default size limit for this PST file is referred to as "unlimited," but in reality it is limited to 16 TB (terabytes). The option you have when creating a new PST file is to use the older file format, which is limited to 2 GB. There is no reason to use that older file format, unless you need to copy this PST file to Outlook XP or an older version.
There is a master configuration of RSS for the SharePoint farm, which controls if RSS is available or not. Open the Central Administration tool for SharePoint, switch to Application Management, and click Web application general settings in the SharePoint Web Application Management section. There, you will find RSS Settings, which by default will be enabled. If this setting is disabled, then no list or library will have an RSS configuration setting visible. Each site collection also has its RSS configuration, which controls if RSS is enabled or not in this site collection. Almost the same configuration page is also available for each individual site in that site collection, except that these configuration pages cannot control the overall RSS setting for the complete site collection. The following Try It Out contains the steps to configure RSS for a site collection.
Try It Out: Configure RSS Settings for a Site Collection
|
Finally, each list and library has its own RSS configuration, which controls if RSS is enabled or not, and what information this RSS feed will send to the feed reader. This is actually the most interesting RSS configuration page, due to all the options it contains. Follow the steps in the Try It Out below to configure the RSS settings for a SharePoint list.
Try It Out: Configure RSS Settings for a SharePoint List
|
As you have seen, there are a lot of places to configure RSS settings. But how do you force an update instead of waiting for the default schedule for a particular RSS feed? The answer is that you do it the same way that you update anything else in MS Outlook. Press the F9 key. However, this alone will not work with RSS feeds, since the Update Limit setting is set by default on the RSS Advanced configuration page, as mentioned at the beginning of this RSS discussion. You may remember that SharePoint lists are, by default, configured to send updates to the RSS feed reader once every 60 minutes. Uncheck the Update Limit for this RSS feed in Outlook, and then press F9 to force an update.
It is hardly a secret that traditional meetings often are ineffective and sometimes just plain boring. Why is that? The main reasons are that the preparations for the meeting are bad, those involved in the actual meeting process have problems keeping to the time schedule, the attendees are not prepared, and there are always some members who forgot to bring their meeting invitation. And to make things worse, after the meeting, it can sometimes be hard to find out about decisions and information given out during the meeting. So, in effect, many attendees feel that many meetings are a waste of time.
How can this be improved? One solution is to use SharePoint to keep track of everything about the meetings. But some things, such as sending meeting invitations and keeping track of people's calendars, are handled better by MS Outlook. Both the 2003 and 2007 versions of MS Outlook are fully integrated with SharePoint's meeting functionality, and they are the preferred way of creating meeting invitations and workspaces at the same time. Your users don't have to learn a completely new way of managing these meetings; everything they know about checking the Outlook calendar status for attendees and resources, managing invitations, and moving meetings, is exactly like it was before. However, there are some new features related to creating a common place to store all the meeting details. This place is known as a meeting workspace.
A meeting workspace is a common team site, built on a specific site template. It has a number of preconfigured lists for storing information such as the meeting agenda, decisions, a list of attendees, and a list of tasks. Just like any other team site, it can be modified to suit your needs for this particular meeting. You can also create a series of meeting workspaces that are connected to each other; this will make it very easy to go back to any previous meeting instance to view its details.
NOTE
You can use a meeting workspace just as a place to store everything about a meeting, but the best way to use it is to display its content in real time during the meeting, using a video projector or a large monitor. This makes sure that everyone focuses on the same thing.
Another smart move is to enter the decisions and tasks in their lists, and take notes directly in SharePoint during the meeting. This way, all attendees who are still awake will see what is documented and can comment directly if something is wrong.
The following sections list the logical steps for using SharePoint's meeting workspaces for managing meetings and using a video projector during the actual meeting. Later you will see the steps for doing this in MS Outlook and SharePoint. This is what you will need to work with meeting workspaces as described:
Windows SharePoint Services: MOSS will also do fine.
MS Outlook 2007 (or 2003): Earlier Outlook versions are not integrated with SharePoint.
MS Exchange Server 2007 (or 2003): To view calendars of the attendees and resources.
If you don't have MS Outlook and MS Exchange, it is still possible to create meeting workspaces, but it is not anywhere near as easy and effective a process as if you have these programs.
In this example, you are the meeting organizer who needs to discuss a new project that will start next week. You have five project members, and all of them must participate in this first meeting:
You create a meeting agenda, including an estimation of how much time each item will take and who will be responsible for it. The total estimated meeting time seems to be about 60 minutes.
Using MS Outlook, you look for a time when all five project members seem to be available.
Using MS Outlook, you also look for a conference room that is equipped with a video projector and a network connection and is available for this meeting.
You create, but do not yet send, the meeting invitation to all project members, plus the conference room, which happens to be a resource mailbox in this case (but a public folder mailbox will also do fine).
Still with the meeting invitation open, you create the meeting workspace in SharePoint.
You add a description of the meeting and then send the invitation to the attendees and the resource mailbox.
Using your calendar, you open the new meeting workspace and start adding the agenda items, the objective, and some documents that will be discussed during the meeting.
All attendees except Bill accept the invitation. Because Bill must be there in order to make decisions, you reschedule this meeting using Outlook. A new invitation is sent out. There is no need to change or update the meeting workspace.
Bill sends you an e-mail saying that he needs to add two items to the agenda. You tell him to use the link in his meeting invitation to open its workspace and add these items. Because Bill is an attendee, he is automatically granted the rights to write and update any list in this workspace.
Everyone (including you) seems satisfied with the meeting preparations so far. Just relax and await the actual meeting.
It is time for the meeting. You take your laptop to the conference room and connect it to the network to make sure you can open the meeting workspace. Then, you connect your computer to the video projector. Everything is now ready for your meeting:
When all attendees have arrived, you display the meeting workspace using the video projector. You give a quick overview of the meeting workspace so that everyone understands what is displayed.
You point your mouse at the list of meeting objectives described on the workspace and tell the attendees what the meeting is all about.
You point your mouse at the meeting agenda and show the attendees that each item has a title, a description, the name of the person responsible for each item, and finally how much time each item is supposed to take. Make sure that people understand that they must stick to the estimated time or the meeting will take longer than planned, which is something nobody wants.
The first item on the agenda is to greet everyone, welcome them to this meeting, and explain what the meeting is about. You have just done that so you continue with the next item on that list.
The next item is to discuss the project plan. Instead of handing out paper, you open the document that describes this plan: Everyone can see this document now, and you can all start discussing this plan.
You all agree that Bill should be the project leader. This is entered in the Decision list in the meeting workspace.
You go on with the next agenda item. Marina is given the task of ordering new software tools that will be needed during this project. This information is entered in the Task list on the workspace.
Marielle comments on the number of project members. She thinks that it will be hard to meet the deadline with just five people. This comment is entered in a list normally used for announcements.
For each item on the agenda, a number of decisions, delegated tasks, and comments are made; all of these are entered in their respective lists. When the meeting is over (on time because everyone tried to keep to the expected time slot for each agenda item), you will have full documentation of everything important that happened at the meeting.
You end this meeting, reminding all attendees that they can go back to this workspace whenever they need to and read what was said and done.
Because a meeting normally results in a number of tasks that need to be accomplished in due time, it is interesting to revisit the workspace for some time after the actual meeting. SharePoint stores this information until you actively delete this workspace; if necessary you can reuse this information in later meetings. Following are some typical activities after a meeting:
Marina wants to check some details about the task assigned to her, so she looks at her Outlook calendar to find the booking for that meeting, which contains the link to the meeting workspace.
Because Bill is the project leader, he also wants to see the complete list of tasks and their due date to check if anybody is behind schedule.
The manager for your department says he wants a copy of the meeting minutes. You open the meeting workspace and add the manager as a member of the Visitors SharePoint group, using the built-in feature of SharePoint to send an e-mail to the user who has been granted access to a site. You add some descriptive text in that e-mail and explain that you don't use meeting minutes anymore but instead use SharePoint's workspaces.
Marielle wants to find out who the project members are today. She also uses her Outlook calendar and the link in the booking for this meeting to quickly access that meeting workspace and read its list of attendees.
One important partner wants to view the details from this meeting. Because he does not have any user account on your network, you cannot ask him to open the workspace for this meeting. And because there are no meeting minutes, you have nothing to send him. Instead you start an MS Live Meeting session, sharing your web browser to display the workspace to this partner. This way, you also can be sure that this partner will not see anything other than what is required.
MS Outlook plays a very important role in managing meetings in SharePoint. It is used to send out invitations and to quickly open the meeting workspace before, during, and after the meeting. MS Outlook is also used to create the meeting workspace, although you can create this workspace from within SharePoint, just like any other team site. Remember that a workspace is just an ordinary team site but uses a special meeting site template.
NOTE
Only MS Outlook 2007 and 2003 are integrated with SharePoint. Previous versions of Outlook cannot create a meeting workspace, nor can they see its properties.
In order to create a meeting workspace, the user needs to be assigned the Create Subsites right on the web site that is the parent of the workspace. All users who have a personal web site (My Site) can create meeting workspaces as subsites in their personal web site. By default, only owners of a site have this right. In other words, team sites you have created and personal sites are locations that you can use to create meeting workspaces. Regardless of where the meeting workspace is created, all users who are invited are automatically assigned the right to join that workspace, even if it is created in a personal workspace. Typically, a project manager (who uses a team site for his project information) will create all related meeting workspaces under that project team site, and other users who just need to create an ad hoc meeting workspace will use their own personal site.
NOTE
After the workspace site is created, no more meeting workspace or other subsites can be created under that first meeting workspace site!
As you can see, Outlook has a lot of features that integrate with WSS 3.0 and MOSS 2007. As an administrator, you may want to control the behavior of this integration. All of these features are stored in the Windows registry settings. These settings can be controlled by the deployment tool that comes with the MS Office 2003 Resource Kit or by the Group Policy Objects (GPOs) in Active Directory.
NOTE
Use the GPO templates Office12.adm and Outlk12.adm to control these SharePoint-related features. See http://tinyurl.com/y3buyq for the MS Office 2003 Resource Kit and more information about using these settings.
The following table lists the key registry entries; all of them are in the HKEY_CURRENT_USER MicrosoftOffice12.0 key.
Key | Value | Type | Description |
---|---|---|---|
CommonDWS | PollingInterval | DWORD | The number of minutes before checking for updates of Document Workspace (default 10, allowed values are 1–999). |
CommonMailSettings | DisableSharingOptions | DWORD | 1 = disable; 0 = enable: Shared Attachments option in Outlook messages. |
CommonSecurity Trusted Alert Sources | All | DWORD | 0 = do not allow; 1 = allow: users to use Outlook to manage all SharePoint alerts (default = 0). |
AllIntranet | DWORD | 0 = disallow; 1 = allow: users to use Outlook to manage alerts from all SharePoint sites within Outlook (default = 0). | |
AllTrusted | DWORD | 0 = do not allow; 1 = allow: users to use Outlook to manage alerts from all intranets (default = 1). | |
MeetingsProfile | EntryUI | DWORD | 1 = disable; 0 = enable: Meeting Workspaces button on Outlook meeting requests. |
ServerUI | DWORD | 2 = disable that user can enter values to server list. If so: publish default, disallow others. | |
MRUInternal | String | Set a limit of five servers available for Meeting Workspace sites. See more about this following this table. | |
OutlookPreferences | DisallowSTS | DWORD | 1 = disable; 0 = enable: the feature of linking SharePoint contacts and events lists with Outlook. |
STSSyncInterval | DWORD | The number of minutes before the next update process for linked SharePoint contacts and events lists in Outlook (default is 20 minutes). Set any value between 1 and 1430. | |
SharePointTrackingName# | Name | String | (# = 1-4) The display name of SharePoint site that will be listed in the "Select A Location list." |
URL | String | The URL of SharePoint site to be listed in the Select a Location list. |
The settings for the key SharePointTrackingName# and the values ServerUI and MRUInternal for the MeetingsProfile key control what options the user sees listed in the Select a location menu when creating the meeting workspace. The default is to show these sites:
My Site.
Sites listed in the MRUInternal value.
Up to five of the most recently used sites listed in the SharePointTrackingName key.
Up to five of the most recently used sites. This list is built from cookies stored when users visit a site, where they have the Create Subsite right.
"Other," which allows the user to enter any SharePoint URL.
NOTE
You can create up to five SharePointTrackingName# (#=0-4) entries to have these sites listed for the user when creating the meeting workspace.
The five default meeting workspace templates are listed in the following table.
TemplateName | TemplateID |
---|---|
Basic Meeting Workspace | Mps#0 |
Blank Meeting Workspace | Mps#1 |
Decision Meeting Workspace | Mps#2 |
Social Meeting Workspace | Mps#3 |
Multipage Meeting Workspace | Mps#4 |
Just like any other WSS site, meeting workspaces are built on a site template. By default, there are five different meeting workspace templates:
Basic Meeting Workspace: Contains four lists: Agenda, Attendees, Objectives, and Document Library.
Blank Meeting Workspace: Contains no lists or Web Parts.
Decision Meeting Workspace: Contains these lists: Agenda, Objectives, Attendees, Document libraries, Tasks, and Decisions.
Social Meeting Workspace: Contains three tabs, or pages: Home, Discussions, and Photos. These three pages contain these lists: Attendees, Directions, Things to Bring, Discussions, and Picture Library. You can add new lists to any of these pages. You can also create new pages using the Modify This Workspace link.
Multipage Meeting Workspace: Contains three pages: Home, Page 1, and Page 2. The Home page contains the following lists on the Home page: Objectives, Attendees, and Agenda. The other pages are empty until you add one or more lists to them. You can also create new pages, using the Modify This Workspace link.
As with team sites' workspaces, you can save any customized meeting workspace as a site template. This makes it available when creating new meeting workspaces in the same site collection. You may recall from previous discussions that a site collection is all the team sites created under a specific top-level team site, including the top-level site itself.
Creating a meeting workspace is very easy. This process is fully integrated with the Outlook process to send invitations to users. For example, say that you want to create a meeting workspace for yourself, Anna, and Axel. This workspace should use the basic workspace template and have the name Project ALPHA. Because you are the administrator for the IT team site, you will create it under that site. Use the steps in the Try It Out below to do this.
Try It Out: Create a Basic Meeting Workspace under IT
|
When you open the new workspace, it displays the four lists: Objectives, Attendees, Agenda, and Document Library. The next logical thing to do is to add information to this workspace, such as the objective and the agenda. Note that you do not need to add attendees, because this list is automatically populated based on the invited users for this meeting. The list also displays each user's status regarding this invitation, for example Accepted, Declined, or No response so far.
Try It Out: Modifying a Meeting Workspace
After doing this for a while, you might want a faster way of adding agenda items. The simplest way is to use the Datasheet view, which will display this list in a table view. To do that, follow these steps:
That was an easier method, right? But there are still some things you can do to improve the management of the agenda. For example, you can summarize the total time for this meeting, and you can add a new column that you can use to indicate that an item is completed. Use the following steps to fix these features:
This enhanced list is now ready to be used. Note that the Done column is the first column on this list. Also note that the total sum for the Time column is displayed on top of the Time column (see Figure 7-17). Figure 7-17. Figure 7-17The Done column is not that easy to use in the default view. It is much easier to switch to Datasheet view (Actions Edit in Datasheet), because you can simply check each item as it is completed. Compare Figure 7-18 to Figure 7-17. Figure 7-18. Figure 7-18Because the Datasheet view is so much easier to see and modify items in, it is the recommended view to use when holding this meeting with the attendees. The smartest thing to do is to create a new view, based on the Datasheet view, and use that view on the start page for this meeting workspace. Use the steps in the following Try It Out to do that. |
Try It Out: Create a Datasheet View for the Agenda List
|
The meeting workspace is starting to look good, but some things are still missing. There is no place to add notes or comments from the meeting, and there is no way to store decisions and tasks created during this meeting. You fix this easily by following the steps in the Try It Out below.
What do you say? Isn't this a very easy, but at the same time powerful, way of organizing all types of information related to meetings, such as meeting comments, agenda, attendees, decisions, and tasks? By adding the lists you need and modifying their columns, you can control what and how information is entered in this workspace, thus making sure nobody forgets about adding important information. It sure beats the traditional meeting minutes!
Did you notice that all lists you add to the workspace are immediately displayed on the web page? Compare that to ordinary team sites, where you can choose to add these lists and libraries as links on the Quick Launch bar or not, then later add them as Web Parts to the web page. This choice is not available for workspaces, because they do not have the Quick Launch bar. So for more complex meetings, you may need more than one page for all your lists. This is a very easy task to accomplish with workspaces, but team sites do not have the same functionality. Another difference between workspaces and team sites is that you will automatically create a new list or library when adding list Web Parts in workspaces, whereas in team sites the same operation will create a copy of that list or library. This is demonstrated in the following example.
For example, say that you have a workspace for a project meeting with several lists on the Home page, and you also have a large document library. You discover that this library will make the Home page very long and hard to use, so you decide to create a second page on this workspace and move these documents there, using the steps in the following Try It Out.
Try It Out: Add a New Page to a Workspace
NOTE
You can also make a template of the original document library and include all documents, up to 500 MB in total. You can move, rename, or delete a page, except for the Home page. To move a page, choose Site Actions Manage Pages. Note that you cannot move the Home page, nor can you move a page to the left of the Home page. To change the name of an existing page, choose Site Actions Manage Page; SharePoint will now display the Order action. Click the black menu arrow to display a list with different options, as shown in Figure 7-20. Click Settings and enter the new name for the page. Figure 7-20. Figure 7-20Deleting the page also removes all its content. Because there is no way to undo this operation, make sure that you copy the page's lists before you delete it! Use Manage Page and its menu as depicted in Figure 7-20. Then select Delete. This displays a list of all pages except Home. Select the page to be removed, and click the Delete button at the bottom to remove the page from the workspace. Click OK on the warning page. |
It is very common to have a series of meetings. For each of these meetings, it is important to have easy access to the information from previous meetings. Using SharePoint's meeting workspaces, this is a breeze. One of my customers complained that their project meetings were almost too complicated to perform, partly due to their constant need to go back to previous meetings to see things like who was responsible for a specific task or when a certain decision was made. After they started to use SharePoint's meeting workspaces, they told me that all this was now much easier; in fact, their meetings were now both fewer and shorter.
The support for a series of meetings in SharePoint is a very strong feature! This can save you a lot of time and energy, compared to using traditional meeting minutes on paper. It makes it possible to go back and forth between the meeting dates and see everything that happened in them. You can even search all the meeting instances for a given text string. This is default with MOSS, but for WSS the SQL Server has to have the Full-Text Indexing feature activated.
After the first meeting workspace has been created as described previously, you can join, or link, new meeting instances to that first workspace. This creates a new page that looks like an individual workspace, but in fact it is a part of the first workspace, cleverly disguised behind smoke and mirrors. "Behind smoke and mirrors" might not be completely true; you will soon see that the workspace gets one enumerated folder for each meeting instance in this series to store the information from that meeting.
For example, say that the first project meeting you created in the previous example will be followed by a number of other meetings related to that project. Now you need to create the second meeting, and you must make sure to link it to the first meeting workspace instead of creating a completely new one. Follow the steps in the Try It Out below to do this.
The ability to link a series of meetings to the same workspace is a real time-saver. You can easily find any information about an earlier meeting just by clicking a meeting's date. However, sometimes it would be great if the content from one list could be available in any meeting instance. For example, say that you have a list named "Tasks;" it contains a list of actions to be performed, each action's due date, and the name of the person responsible for each action. Assume you have this list on a project meeting workspace; when performing each meeting, you want to see all actions remaining from earlier meetings. To do this, you need to change the list into a "series object," as the next Try It Out describes.
Try It Out: Change a List into a Series Object
In other words, by making a list into "series items," you make it one single list that is shared among all meetings in this series. This works fine as it is, but sometimes you want to filter the list to prevent it from showing all items. For example, the Tasks list displays all actions, including the ones that have been completed. It would probably be more interesting to see only items that are not completed. This is easily solved by using a view that filters the Status column that the Tasks list contains in this example. The good news is that there already exists such a view for this list, named Active Tasks. You just have to use it as the default view for the Tasks Web Part:
|
Now you have a general idea of how to use lists and views for series of meetings. You have the tools for creating a very powerful and time-saving workspace for meetings.
Adding new meetings to an existing series is easy, but sometimes there is a need to change or manage these meetings. In the following table you get some tips about these situations.
Situation | Comment | Solution |
---|---|---|
You, the meeting organizer, delete an existing meeting request in Outlook that has an associated workspace. | This will make the specific meeting instance in the workspace an orphan. Its data remains in SharePoint, but there is no connection to Outlook. Note that Outlook 2007 (but not 2003) will open the meeting invitation, and mark it as "Canceled." It will also offer the user to send out an e-mail about this meeting being canceled. | Open the workspace. There is a red exclamation mark next to the orphaned meeting date. Click this exclamation mark, and it displays a menu (see Figure 7-21). You can select the option to Move the workspace's data to another existing meeting instance (overwriting any of its content, so make an empty workspace first; see Figures 7-22 and 7-23); to Keep (data remains in the workspace, but no Outlook appointment is associated); or to Delete (this instance of the workspace and all its data is removed). |
You want to remove one meeting instance from a series of meetings. | For example, say that you planned one meeting, but it was canceled, and you don't want to move it. | Use the previous technique: Delete the meeting request in Outlook. Open the workspace and its date will have the red exclamation mark. Use its menu to delete the workspace. Instead of deleting the meeting appointment in Outlook, you can also open its properties and click the Remove button in the Meeting Workspace pane. |
You want to connect one meeting instance to a new date. | Say that you have an existing meeting instance with lots of data and that you want to associate it with a new meeting request and a new date. |
|
The procedures described in the preceding sections work very well for internal users who have access to your SharePoint environment and have been invited using Outlook's meeting requests. But sometimes you need to allow other users to view the meeting workspace. This section describes the options you have to handle these situations.
Sometimes there will be people in your organization who aren't invited to your meetings but who need to access the meeting workspace. The typical example is a manager who wants to know what you do in these meetings. Before you started using meeting workspaces in SharePoint, he got a copy of the meeting minutes. But now, because you don't have these anymore (and frankly, you don't miss them), you must provide him with this information in another way. The easiest way is to add this manager to the list of users with access to this workspace site; making the manager a member of the Visitors SharePoint group is sufficient to enable him to view and copy all the content of this workspace.
NOTE
When you have a series of meetings all invited users have Members access (Contributor permissions) to all meeting instances, regardless of when they were invited! There is no way to limit access to just one meeting because the series is sharing the same workspace and, therefore, the same list of users. The same is true when you add additional users; they also have access to all meeting instances. But you can set a unique right for any user to a specific list, or library, using its security settings in Settings Document Library Settings Permissions for this document library. You can also set a specific security setting for an individual list item or document, by using its quick menu option: Manage Permissions.
To add an extra user to an existing meeting workspace without making him or her a meeting attendee, follow the steps in the Try It Out below.
Try It Out: Grant Extra Users Access to the Workspace
Another solution would be to manually create meeting minutes from the data in the workspace. One way of making this task easier would be to export the Agenda and Decisions lists to Excel and copy that information into the meeting minutes. NOTE
I have not seen any tool that does this automatically, although it may be possible using MS SQL 2005 Reporting Services. |
Another common request is to allow people outside your organization access to the information stored in the meeting workspace. The problem here is that these users do not have access to anything inside your network, because they don't have a network user account. Following are some options to handle this situation:
Create a user account: If you make this external person a member of your network, you could grant him or her access the same way as any internal user, as in the previous example about the manager. This solution will be of interest if this a recurring request.
Create meeting minutes manually: Again, as the previous section discussed, you can manually create a document with the meeting minutes. This is acceptable for a one-time request with a limited amount of data in the workspace.
Use MS Office Live Meeting: This program is designed to allow anyone with an Internet connection to see and participate in any meeting, not only SharePoint's meeting workspaces. One way of using this program is to invite the external user ahead of time to join the Live Meeting. You can also allow a user who has not previously been invited to the Live Meeting session to simply join it at the time it starts by displaying the workspace on the MS Live Meeting panel and sending the user this URL link in an e-mail. Either way, you can give this user real-time access to the meeting and allow him or her to participate and discuss matters like any attendee of this meeting.
The last option may also be of interest for internal users, when they need to attend meetings while working from home or from an Internet café when on vacation.
NOTE
For more information about MS Office Live Meeting, visit http://office.microsoft.com/en-us/FX010909711033.aspx.
13.59.237.58