Recovery in Sharepoint 2007 can be divided into two distinct areas:
Recycle bin. This has two stages – an end user recycle bin and an admin recycle bin. Items deleted from an end-user recycle bin go through to the admin recycle bin. Note that the end user recycle bin is site based (i think), with its contents being security trimmed based on the users credentials. Note that the recycle bin does not work for column deletion etc.
Vesioning persists in Sharepoint 2007, and is essentially the same as in V2 sharepoint.
A delete event has been introduced into the Sharepoint object model.
You can use sharepoint backup / restore. Note that stsadm -o [import | export] replaces smigrate.exe. Note that this is not full fidelity (e.g. workflows and recycle bin contents are not persisted). I dont think that this backs up defs.
Alternatively you can use SQL only backup and restore. Or you can use a 3rd party solution.
Workflow paradigm: event -> condition -> action
Windows Workflow Foundation is a framework that is part of WinFX, aimed at facilitating the creation of activities / processes. Workflows can be hooked into all manner of things – eg outlook, infopath forms.
Workflows can be set up in Sharepoint Designer (there is a wizard), but also you can create more complex workflows using Visual Studio. Note that out-of-the-box workflows exists, such as issue tracking (not sure if part of WinFX or with Sharepoint).
Apparently, Sharepoint Designer can be used to generate aspx forms whilst Visual studio can be used to generate aspx and infopath forms (custom handler code using the code-beside model). I believe that server side infopath is only available with MOSS, and not WSS – hence WSS will not support these.
Note that workflows can be turned on or off in sharepoint on a site-collection basis. Note that there is a claim released feature if someone else is working on a specific task. Also you can easily set up parrellel approval.
Whilst websites could be created in Sharepoint 2003, by setting up a site and allowing anonymous authentication. Whilst you still need to set up anonymous access with Sharepoint 2007, there are masses of extra native features to facilitate the creation and administration of websites.
It is a lot easier to radically rebrand you site by using a master page (to whatever degree that you require – people browsing the site need not even know that its based on sharepoint). Note that there are actually 2 master pages – 1 for content pages and 1 for admin pages. Although a similar effect could be acheived in Sharepoint 2003 by adding a new page type in the smartpgs folder, it was a lot trickier.
Note that in addition to master pages, you can set up content type pages – i.e. with specific web-part zones. Note that pages are stored in a document library.
You can set up proper content management on your site using the approval mechanism. An authoring toolbar appears if you have the correct credentials. Rich content can be input via a Rich Text Editor (with no need for an activex control). Each site has a central admin to push content onto a site.
There is also support for setting up site caching (using the ASP.NET 2.0 caching functionality).
The Business Data Catalog permits Sharepoint to consume from non-sharepoint data sources. Sharepoint will be available with server out of the box connectors including SAP, Siebel and Dynamics.
To allow Sharepoint to consume a datasource, the datasource API must be described. This is done within an xml file (see http://www.codeplex.com/Wiki/View.aspx?ProjectName=DBMetadataGenerator for a utility to create these xml files). I believe that the runtime and admin API needs to be described seperately. Note that when a new datasource has been added, you need to perform an iisreset to update the cache of BDC interfaces. Note that it is possible to permit actions (e.g. writing back to the datasource).
Sharepoint 2007 comes with a prebuild set of business data webparts, to present bdc data.
Here are some keypoints that Ive picked up that dont really fit with any of my previous blog posts…
- In sharepoint V2, eventhandlers could only be set up on doc and form libraries. In V3, all lists etc will have event handlers.
- In Sharepoint V3, you can dynamically re-arrange sites within a site collection.
- No ISAPI filter for Sharepoint V3. All requests are processed by ASP.NET
- Sharepoint V3 supports both ASP.NET 2.0 and Sharepoint V2 webparts.
- Sharepoint V3 can use a wide range of Authentication mechanisms (eg the auth mechanisms native to .NET 2.0, such as form auth).
- Sharepoint V3 content types are essentially facilitated by record chaining in the Sharepoint Database).
- Outlook 2007 can show and overlap outlook and sharepoint calendars.
- Microsoft proposed that they were intending to host sharepoint for small businesses etc – I guess that this will be part of the’re live offering.
- Sharepoint tasks can now be directly sent through to outlook tasks
Sharepoint 2006 conference slide decks: http://sharepointmvps.officeisp.net/spc2006/default.aspx
My Sharepoint links
Names to look out for
Mike Ammerlaan – Excellent session at the Sharepoint 2006 conference on Templates and Features (unfortunately he doesn’t seem to have a blog)
Arjun Ohri – Excellent session at the Sharepoint 2006 conference (unfortunately he doesn’t seem to have a blog)
Site Definition – core description of what a site is
Site Template – cab package of differences from the site definition. Stored in a content database and generated by the end user.
Features – set of extensibility point that are overridden.
Im not really going to go into these in any detail as there explained really well here. This is well worth reading.