Sharepoint 2007 is in Beta 2 now and is projected to be released at the beginning of the year but now is the time to start looking at the new features that SharePoint 2007 and WSS V3.0 ordain contain. Below are some of the highlights of the new features that SharePoint 2007 and WSS V3.0 ordain include. place columns give a central reusable model for column definition. When you create a site column each enumerate that uses this column has the same definition and you do not undergo to do the tedious work of reproducing the column in each list. Additionally site columns give you with the simplicity of a single maintenance inform. For instance you can act a status site column which may include multiple choices of an enterprise's specific statuses and apply the column in dozens of communicate master lists across the place collection. If you add a new status you can modify the place column instead of having to change each enumerate that contains a status column. circumscribe types are a core concept used throughout the functionality and services offered in Microsoft Windows SharePoint Services (version 3) and 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 circumscribe. Content types alter you to manage the metadata and behaviors of a document or item write in a centralized reusable way. For example consider the following two types of documents: software specifications and legal contracts. You might want to hold on documents of those two types in the same SharePoint document library. However the metadata you would want to gather and store about each of these enter types would be quite different. In addition you would likely want to assign different workflows and retention policies to the two types of documents. Content types enable you to hold on multiple types of content in the same SharePoint library or list. In the preceding example you could be two content types named Specification and Contract. Each content write would include different columns for gathering and storing item metadata and would undergo different workflows and policies. Yet items of both circumscribe types could be stored in the same SharePoint document library. Recycle bins or undelete functionality is another important improvement that has been added in Microsoft Windows SharePoint Services (version 3). This functionality is available in both lists and document libraries. Deleting an item from a list triggers a multilevel series of events. First the item is sent to a Web-level recycling bin. From here the item can be undeleted by any individual who has been given appropriate rights. When the item is deleted from this bin the item is sent to a second recycling bin controlled by the place administrator. Among the design features of this bin are timers that allow you to alter the removal of old documents. For example an administrator may decide that the vast majority of requests for item restores happen within the first 90 days. In this scenario the administrator may set the timer such that items older than 90 days are permanently deleted. RSS has become a standard way of aggregating circumscribe from the Web. For more information on RSS in Microsoft Windows label Name "Longhorn," see the technical article RSS Support in Longhorn on Microsoft Developer communicate (MSDN). By integrating RSS feeds for each SharePoint list. Microsoft Windows SharePoint Services (version 3) provides a displace mechanism for forwarding information to end users. Folders one of the popular features from enter libraries in Microsoft Windows SharePoint Services (version 2) is now also available in lists. Folders allow advance segregation of circumscribe within a single list adding another aim of versatility. One of the interesting features of folders is the ability to appoint 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 answer as a displace but fully functional item write. An example of this can be seen in Windows SharePoint Services discussion boards. Each top-level discussion is in fact a folder with metadata containing one to n child objects. By modifying the appearance of the folder an end user can visualize the folder as another list item rather than as a container. You can use this model in custom lists to act a dynamic parent/child list. Many business applications require rich container objects for which a parent disapprove has both important data concerning itself and one to n children with similar data. Normally you deal with this challenge by using lists in which a parent or master list selection drives the show of a child or detail list. Because you can now appoint metadata to folders in a SharePoint list you can achieve similar functionality with a single enumerate. believe an Orders enumerate for example. You could provision a folder as an order and then appoint metadata to it such as request number customer and shipment method. By doing so you can alter the folder mimic the know list functionality. You can then fill the folder with request items list items each with its own metadata such as item be description and price. Now you have the rich functionality of a master/detail enumerate within a hit list. enumerate Indexing. Integral to the idea of using Microsoft Windows SharePoint Services as a platform is the ability to use its storage containers specifically lists and document libraries for application storage. However a be of limitations restricted the adjust use of these containers in Microsoft Windows SharePoint Services (version 2). One of the problems was the inability to handle large lists. As lists began to change both in metadata and list items the mechanisms built into lists became clunky and inefficient. A key goal within Microsoft Windows SharePoint Services (version 3) was to fix these restrictions and create a rich storage model with performance capable of supporting applications both external and those built upon the Windows SharePoint Services platform. One of the key ways that Microsoft Windows SharePoint Services (version 3) solves this air is to consider indexing on columns. By allowing a column to be indexed and stored as a simple label/value unify in a separate database access to specific items in large lists is significantly improved. These kinds of performance improvements allow SharePoint lists to change state adjust data stores capable of supporting external applications as come up as simple aggroup sites. For example with an Orders enumerate you could furnish a folder as an order and then assign metadata to it such as order number customer and shipment method. Consider that by indexing the order be column access to specific items in the list by an external communicate becomes significantly cheaper. Another scenario is an external application with hundreds of thousands of records. Previously your Web application could not use a SharePoint enumerate as a storage device. With the inclusion of indexing on columns performance increases allow this architecture. By using Windows SharePoint Services storage the standard features of the platform such as views alerts and RSS can now be used as a data store explorer for internal use in simple team sites. Cross-List Queries - Another improvement made with the idea of using Microsoft Windows SharePoint Services storage more effectively is cross-list queries. Cross-list queries.
Forex Groups - Tips on Trading
Related article:
http://softhearted2986.blogspot.com/2007/12/sharepoint-2007-new-feature-overview.html
comments | Add comment | Report as Spam
|