|
WSS3 vs. MOSS
2007 Feature Comparison |
|
Feature Included |
o |
þ |
|
|
Description |
Windows
SharePoint Services 3.0 |
Office
SharePoint Server 2007 Standard CAL |
Office
SharePoint Server 2007 Enterprise CAL |
|
Alert Filtering |
þ |
þ |
þ |
|
Filters are supported
to highlight the more relevant alerts. |
|
Richer Alert
Information |
n |
n |
n |
|
More information about
the item that has changed is included in the alert. |
|
Alert Customization |
þ |
þ |
þ |
|
Additional platform
features are provided for custom formatting, events, and
alerts. |
|
Task Notifications |
n |
n |
n |
|
Task notifications are
now sent automatically when a user is assigned a task.
There is no need for the user to subscribe to the
notification in advance. |
|
Notification Service |
|
n |
n |
|
Extensible platform
sends customizable e-mail alerts to users. Users
participating in a workflow automatically receive e-mail
alerts without subscribing in advance. Improved
filtering conditions now trigger more relevant alerts to
all users. |
|
RSS Feeds |
þ |
þ |
þ |
|
By integrating RSS
feeds for each SharePoint list, Microsoft Windows
SharePoint Services V3 provides an efficient mechanism
for end users to retrieve the information using RSS-enabled
programs such as Internet Explorer 7 and Outlook 2007. |
|
Consistent User
Experience |
þ |
þ |
þ |
|
Windows SharePoint
Services V3 implements many new and enhanced features
that make the Windows SharePoint Services user interface
more uniform – providing a consistent user experience.
These features are described below. |
|
Rights Trimmed User
Interface |
þ |
þ |
þ |
|
Users are only allowed
to see the features that they have the rights to use.
Previously, Windows SharePoint Services Version 2
Service Pack 2 (V2 SP2) did not inform a user they were
not allowed to perform a function until they clicked its
link. |
|
Automatic Breadcrumb
Bar |
þ |
þ |
þ |
|
Provides immediate
navigational context for the user – creating a greater
sense of “place” within a SharePoint site. |
|
Quick Launch Bar |
n |
n |
n |
|
Available on all view
pages and is more easily customizable. |
|
Top Navigation Bar |
n |
n |
n |
|
Available on all view
pages and is more easily customizable. |
|
View Improvements |
n |
n |
n |
|
Ability to page
forward and backward in addition to improved user
interface for sorting and filtering. |
|
Descriptive Menu
Actions |
n |
n |
n |
|
The Actions drop-down
menu provides task-based descriptions of the actions
that can be performed on a particular SharePoint list or
document library. |
|
Simplified Web Part
User Interface |
n |
n |
n |
|
Simplified user
interface for browsing, selecting and adding Web Parts
to a Web Part page. The Web Part catalog is presented as
a scrollable list; no more paging forward and backward
through the Web Part catalog. |
|
Accessibility |
n |
n |
n |
|
Windows SharePoint
Services V3 is Section 508 and W3C compliant. |
|
Recycle Bin |
þ |
þ |
þ |
|
Enables a user to
easily restore an item that was deleted accidentally.
Administration tools are also available to manage the
lifecycle of deleted items in the recycle bin. |
|
Backup/Restore Support
for VSS (Volume Shadow Copy Service) |
þ |
þ |
þ |
|
Windows SharePoint
Services backup and restore functionality is enhanced
with the support for VSS (Volume Shadow Copy Service), a
feature of Windows Server 2003. |
|
Document Libraries |
n |
n |
n |
Improvement to
SharePoint document libraries include:
• Checking out documents locally
• Offline document library support in Outlook 2007
• Major and minor version numbering and tracking
• Support for multiple content type
• Policy, auditing, and workflow
• Tree view support
|
|
Large-List and
Cross-List Indexing |
þ |
þ |
þ |
|
The performance of
large lists and cross-lists can be improved through the
use of indexes on specific list column properties. This
significantly increases the capacity and performance of
a Windows SharePoint Services V3 list compared to
version 2.0. |
|
Metadata |
n |
n |
n |
Users can extend
document libraries and lists with custom column
properties.
The practical number of column properties that a list or
document library may have has been significantly
increased due to performance and scalability
improvements in WSS V3 Lists.
|
|
Content Types |
þ |
þ |
þ |
Content types are
reusable definitions of document types across your
organization. A single document library can store
content with multiple document types.
A content type is used to define a group of documents
that share a common set of attributes; including:
• Document templates
• What’s on the “New” button
• Metadata specific to the content type
• Shared column property templates
• Custom InfoPath forms in 2007 Office system
applications
• Enterprise defined policies
• Common workflows
Content types are different from traditional file types
(which map to physical file formats like Word documents
or Excel spreadsheets). Content types are used to define
and implement business documents such as functional
specifications, budget planning spreadsheets or new
product concept presentation.
|
|
Application Templates |
n |
n |
n |
While standard
workspaces in Windows SharePoint Services are easy to
implement, organizations seeking a more customized
deployment can get started quickly with application
templates for addressing specific business processes or
sets of tasks.
A new set of Application Templates will be available for
Windows SharePoint Services V3. They will highlight
aspects of task coordination and will offer some
pre-configured workflows. The application templates
provide customers with a baseline for deploying Windows
SharePoint Services in context of business processes and
set of tasks. A rich ecosystem of solution providers use
the application templates as the basis for deeper
horizontal and vertical solutions.
|
|
Workflow |
þ |
þ |
þ |
Windows SharePoint
Services V3 hosts Windows Workflow Foundation (WF) to
enable customized creation of workflow solutions and use
of structured workflows on document library and list
items. Office SharePoint Designer 2007 can be used to
design and configure custom workflow solutions with the
support for Windows Workflow Foundation in Windows
SharePoint Services V3.
Ready-to-use workflow templates are available with
Office SharePoint Server 2007 as well as a new set of
application solutions for Windows SharePoint Services
downloadable from the Microsoft TechNet Web site.
|
|
Tree View |
þ |
þ |
þ |
|
Tree view controls are
now supported for navigating document libraries in a
manner similar to the file system. |
|
Append-only and
Multi-Value Lookup Fields |
þ |
þ |
þ |
Append-only fields
enable a user to append text to a field without being
able to modify the existing content of the field. This
is useful for logging and tracking applications.
Multi-valued lookup fields enable multiple values to be
selected from another list field.
|
|
Extensible Site and
List Templates |
n |
n |
n |
|
In Windows SharePoint
Services V3, site and list templates can be edited in
Office SharePoint Designer 2007. |
|
Subsite Promotion |
þ |
þ |
þ |
|
An existing subsite
can be promoted (repositioned) within the logical
hierarchy of SharePoint sites (SharePoint site
collection) to which it belongs. |
|
Support for ASP.NET
2.0 |
þ |
þ |
þ |
Windows SharePoint
Services V3 leverages the reliability, scalability, and
functionality of ASP.NET version 2.0. This includes
support for the ASP.NET version 2.0 Web Part Model (with
added backward compatibility support for Windows
SharePoint Services V2 SP2 Web Parts). Building on
ASP.NET not only provides a deep technical foundation
for WSS, but also allows WSS to leverage the Visual
Studio development environment for application
development.
|
|
ASP.NET Master Pages |
þ |
þ |
þ |
Each Web page in a
SharePoint site references an ASP.NET version 2.0 master
page. Master pages provide centralized control of the
layout and style of all the pages in a SharePoint site.
Each site has a master page gallery that the site owner
can use to customize the look of all of the pages on the
site.
|
|
Performance Caching |
n |
n |
n |
|
|
|
Object Model |
n |
n |
n |
All object model
changes in Microsoft Windows SharePoint Services V3 are
highly backward- compatible with Microsoft Windows
SharePoint Services V2 SP2. However, you should be aware
that your old code, although it will compile, may not
behave as expected in the new object-model hierarchy.
The Administration object model (Microsoft.SharePoint.Administration)
has been completely re-factored to allow for greater
extensibility. There is now a hierarchical object store.
|
|
Field Types |
þ |
þ |
þ |
|
Extensible field types
allow you to use enterprise data structures within
Microsoft Windows SharePoint Services V3 by creating
your own controls, which are exposed as simple fields
within a list or document library by Microsoft Windows
SharePoint Services V3. |
|
Site Columns |
þ |
þ |
þ |
|
Site columns provide a
central, reusable model for column definition. When you
create a site column, each list that uses this column
has the same definition, and you do not have to do the
tedious work of reproducing the column in each list. |
|
Content Type Settings |
þ |
þ |
þ |
|
Content types are a
core concept used throughout Microsoft Windows
SharePoint Services V3. Content types are designed to
help users organize their SharePoint content in a more
meaningful way. A content type is a reusable collection
of settings you want to apply to a certain category of
content. Content types enable you to centrally manage
and reuse the metadata and behaviors of a document or
item type. |
|
Folders in Lists |
þ |
þ |
þ |
|
Folders, a popular
feature in Windows SharePoint Services V2 SP2 document
libraries, are now also available in lists. Folders
allow further segregation of content within a single
list, adding another level of versatility. |
|
Folder Metadata |
þ |
þ |
þ |
|
Users and developers
can now assign metadata to a folder. This creates a rich
content holder that contains child content, while
appearing as more than a container. Essentially, this
allows the folder to function as a separate, but fully
functional, item type. |
|
List Indexing |
þ |
þ |
þ |
|
By allowing a column
to be indexed, and stored as a simple name/value pair in
a separate database, access to specific items in large
lists is significantly improved. These kinds of
performance improvements allow SharePoint lists to
become true data stores, capable of supporting external
applications as well as simple team sites. |
|
|
Overview
What's
New?
Hosting Plans / Pricing
SharePoint Templates
