| Online request form that captures all business user requests for Sharepoint sites |
Currently Available |
| Method for end-user classification of sites that support their creation up to 32 levels (aka provisioning nodes) deep within a given taxonomy |
Currently Available |
| In multi-SharePoint farm environments, supports the provisioning of a site into a node within any specified Sharepoint farm within the customer environment. |
Currently Available |
| In multi-SharePoint web application environments, supports the provisioning of a site into a node within any specified Sharepoint web application within the customer environment. |
Currently Available |
| Enforcement of basic naming convention validation rules (e.g. site names must be a minimum of X characters long) |
Currently Available |
| Smart naming convention rules for sites that are provisioned |
Future |
| Tree navigation control providing alternate method for classification of SharePoint sites (aka alternate method for selecting the appropriate provisioning node). |
Currently Available |
| Dynamic site template filtering based upon the classification of the requested site. |
Currently Available |
| Available filters for the selection of site templates include “All Global Templates”, “All Site Collection Templates”, “All Web Templates” |
Currently Available |
| Support the filtering of available site templates based on those that begin with a specified text string. |
Currently Available |
| Enforcement of business-unit specific metadata at the time of provisioning |
Currently Available |
| Business-unit specific metadata can be either choice dropdowns, multi-value list boxes, or text fields. |
Currently Available |
| Dropdown/list box metadata properties can be created to provide a listing a available pick list values from a centralized choice group. |
Currently Available |
| Business-unit specific metadata can be configured to be either required or optional |
Currently Available |
| Business-unit specific metadata can specified as being a ‘global facet’ which will place that property as a top level navigation facet of the site directory web part. |
Currently Available |
| Ability to specify whether the requested site should be visible to users within the global site directory |
Currently Available |
| Ability to specify owners, members and visitors at the time the site is requested |
Currently Available |
| Ability to specify at the time of request whether the newly created site should also allow the creation of sub-sites via the online wizard under that node |
Currently Available |
| Confirmation screen that provides users with a listing of the metadata specified for their requested site. |
Currently Available |
| Ability for the system to automatically email the specified owners and members of the site at the time in which it is created. |
Currently Available |
| Enforcement of user acknowledgment that they have read and understood the service policies prior to submission of the request for a new site. |
Currently Available |
| Optional approval workflow that can be enforced at the time of the request, configurable by site classification / provisioning node. |
Currently Available |
| Per each provisioning node, support the automatic email notification to a specified list of emails at the time any site is created under that node. |
Currently Available |
| Allow for the optional enforcement of inheritance of provisioning workflow settings to all sub nodes within a classification tree |
Currently Available |
| Default values for any node-specific metadata field can be specified. |
Currently Available |
| The configuration of a site as a provisioning node can be achieved via site settings of that site. |
Currently Available |
| Centralized configuration of provisioning nodes can be performed from central administration |
Future |
| Changes to configuration rules within remote farms shall be automatically reflected in the central provisioning wizard. |
Currently Available |