Important Notes from this video:
Tuesday, May 29, 2012
Workflows using InfoPath, Visio (Premium) & SPDesigner 2010
Important Notes from this video:
Event Receiver : Access Site content using Privileged user account and user token
The below code is from Event receiver. The important parts are
1. Properties.ListTitle
2. Properties.AfterProperties("Title").ToString()
3. objSPUser.UserAccount
4. New SPSite(properties.Web.Url, privilegedToken)
5. Properties.Status = SPEventReceiverStatus.CancelWithError
6. Properties.ErrorMessage
7. Properties.Cancel
Note : SPEventReceiverStatus is an ENUMerator with the following options "Continue, CancelNoError, CancelWithError, CancelWithRedirectUrl"
Sample for CancelWithRedirectUrl
string errorMessage = string.Format ("ZIP Code '{0}' is Invalid!", zipCode);
properties.Cancel = true;
properties.Status = SPEventReceiverStatus.CancelWithRedirectUrl;
properties.RedirectUrl = "/_layouts/EventReceiverProject1/CustomErrorPage.aspx?Error=" + errorMessage;
Sharepoint 2010 provides support for many new events, in both synchronous and asynchronous. The new events are
1. onCreate events for lists and Web sites
2. add and delete events on list
3. add events on websites
4. after events can now be synchronous or asynchronous
To trigger a Event only for a instance of a list, we have to replace the ListTemplateId to ListUrl in the Elements.XML.
- This refers the Announcement List definition.
- This refers the instance of the Announce list instance. TestAnnouncement is the list created using Announcement list definition
Impersonation for Event receivers Sharepoint 2010
SharePoint runs your events in the context of the user who triggered the event. Generally, this is okay, but there may be certain times when you want to let a user perform actions on lists, libraries, or the system that the current user does not have permissions to do. In most cases, you would use SPSecurity’s RunwithElevatedPrivileges method. However, you may want to revert to the originating user on some operations. With SharePoint 2010 you get a property bag that contains the OriginatingUserToken,UserDisplayName, and UserLoginName which you can use to revert to the original user.
Sample for CancelWithRedirectUrl
Sharepoint 2010 provides support for many new events, in both synchronous and asynchronous. The new events are
1. onCreate events for lists and Web sites
2. add and delete events on list
3. add events on websites
4. after events can now be synchronous or asynchronous
To trigger a Event only for a instance of a list, we have to replace the ListTemplateId to ListUrl in the Elements.XML.
Impersonation for Event receivers Sharepoint 2010
SharePoint runs your events in the context of the user who triggered the event. Generally, this is okay, but there may be certain times when you want to let a user perform actions on lists, libraries, or the system that the current user does not have permissions to do. In most cases, you would use SPSecurity’s RunwithElevatedPrivileges method. However, you may want to revert to the originating user on some operations. With SharePoint 2010 you get a property bag that contains the OriginatingUserToken,UserDisplayName, and UserLoginName which you can use to revert to the original user.
Types of Event receivers
1. Site Events
2. Web Events
3. List Events
4. List Field Events
5. Item Events
Monday, May 28, 2012
State Machine Workflow
About Video Visual Studio 2010 provides a template for a State Machine workflow that enables developers the opportunity to build workflow solutions for SharePoint using a graphical design surface. State Machine workflows transition from state to state rather than the transition from activity to activity that is found in a sequential workflow. Learn how to create a SharePoint 2010 State Machine Workflow in Visual Studio 2010.
Source : MSDN http://msdn.microsoft.com/en-us/vstudio/ff623023.aspx
Saturday, May 26, 2012
Custom Search Filter - Search Refinement Panel WebPart
We can easily add the custom result extension type filtering, the filtering is provided by the Search Refinement Panel WebPart available on the results.aspx page.
Source : MSDN Forum
Source : MSDN Forum
Friday, May 25, 2012
Sharepoint 2010 - SPD Workflow - Introduction
Pros
More-flexible workflow definitions
• Reusable workflows are associated with a content type instead of a specific list.
• Site workflows are associated with a site and not a specific list or item in a list.
• SharePoint’s out-of-the-box workflows can now be customized by using SharePoint Designer.
• Association columns can be defined in a workflow and are automatically added to a list that uses the workflow.
• Solution files (WSP) can be generated by exporting a workflow through SharePoint Designer. These can then be imported into another farm.
• InfoPath forms are generated by SharePoint Designer for association,initiation, and task forms. These forms can be customized by using InfoPath Designer.
• Microsoft Visio 2010 can now be used to create the overall structure of a workflow. That structure can then be imported into SharePoint Designer for implementation.
• The Workflow Status page can contain a visual representation of the current state of a running workflow in a Visio diagram embedded in the page.
• Impersonation step - One of the most important workflow improvements in SharePoint 2010 was created specifically to deal with this type of situation. A new type of workflow step, called an impersonation step, can be added to a workflow just like any other step. The difference is that the security context for the impersonation step is not that of the initiating user but of the workflow’s author. The workflow’s author is generally the user who last updated the workflow’s definition. That user can be given the necessary permissions to perform the needed actions that the initiator may lack.
Cons
• SharePoint Designer places certain restrictions on the types of workflows that can be created. For example, SharePoint Designer does not support custom .NET code, looping constructs, or state machine workflows.
• When a user starts a workflow instance, either intentionally or as a side effect to some other action, that instance will execute using that user’s credentials. Even if the workflow continues to run long after the user has left the site, the workflow engine will still use those credentials. Any permissions ( such as file or list item access rights) associated with the initiating user will be applied to the instance when it is running. This security context has often proven too restrictive for some proposed workflow designs. For example, say a user creates a vacation request and saves it in a document library. As a result, an approval workflow is started. Once the request is approved, you want to move it into a protected archive for approved requests. Because the user who initiated the workflow doesn’t have access to the protected archive, the workflow can’t move the request into it. Impersonation step is the solution for this issue.
SPD - Types of Workflow
1. List Workflow - List
2. Reusable Workflow - Content type. Reusable workflows can be configured as part of content type definition. This helps for standardization. Reusable workflows can also be configured as part of the content type’s definition. Whenever the content type is used in a SharePoint list, the workflow is automatically configured. This is a powerful means of standardizing processes across your SharePoint farm, because content types can also be shared between site collections in SharePoint Server 2010.
3. Site workflow - no current item associated with it.
Workflow Data Context
Parameters
Workflow parameters are data elements that are declared in the workflow definition and are passed into the workflow at startup. Parameters can be defined to receive their value at association or initiation.
1. Association parameter- It refers to the point in time when the workflow definition is associated with a Sharepoint List.
2. Initiation parameter – Values are assigned using Initiation form during the initiation of the workflow instance.
3. Association only - (not for item and used for site workflow instance)
This contains all the fields of the list item (for the list workflow) or contains the fields of the content type (for the reusable workflow).
Association column
It is part of the current item, and it is declared in the workflow definition just like a parameter.
Variables
Declared to store data throughout the lifetime of the workflow.
Workflow Forms
Association Form - This form collects the Association parameter.
Initiation From - This form collects the initiation parameter (only for Manual initiation).
Task Forms - The form designed to collect the data during the process of workflow task. The data collected is writter to the Current item, History list or to the Workflow variable.
Note : In Sharepoint 2010 designer workflow, the Infopath forms are created automatically for the forms and can be customized as needed.
Misc
Important : Becoming familiar with the parameters and options associated with each available action is the key to creating powerful workflows in SharePoint Designer.
Important : Note that new actions (a.k.a. custom activities) can be created using Visual Studio and used from within SharePoint Designer workflows.Current Item
Monday, May 21, 2012
Metadata - Terms, Term Set, Term Store Management Tool
Metadata refers to a structured way of presenting information about entities like, documents, people. In lay man terms, it is generally called ‘data about data‘. The main purpose of capturing metadata is to easily identify or locate the content that we are looking for.
The techniques used for optimally managing these metadata values is called ‘Metadata Management'. An easy-to-use framework has been provided by SharePoint 2010 which deals with usage of a set of centrally managed words which can be used across multiple sites as tags or attributes.
There are a number of new features that have been introduced in SharePoint 2010.
When it comes to Metadata, these are some of the basic things that we must know
1. ‘Terms‘: It refers to a word or phase that can be associated with every item.
2. ‘Term Set‘: It refers to a collection of Terms. Termsets can either be created locally or globally.
Termsets created within the scope of a site collection are referred to as Local Termsets and the ones created outside the context of a Site collection are referred to as Global Termsets.
Termset Groups are generally created by a ‘Term Store Administrator'. He designates a ‘Group Manager‘ who creates the Termsets that have to be used in lists/libraries.
"Terms' can further be classified into two categories:
1. ‘Managed Terms‘ – These are the predefined set of terms (words/ phrases) that are created by authorized users.
2. ‘Enterprise Keywords‘ – A number of tags (Keywords) are generated by the users. These are stored in an non-hierarchial list called ‘Keywords Set‘.
Inorder to pre-define the Termsets and Keywords to be used in sites, Microsoft SharePoint Team has provided a tool called ‘Term Store Management Tool‘. Some of the operations that we might want to perform using the tool are :
1. Create, modify or delete term sets and terms
2. Organize terms into a hierarchy
3. Import new terms from a .csv file
4. Promote keywords to terms.
Some of the advantages of using Managed Metadata are:
1. Consistent usage of terms and keywords across content.
2. Better search results.
Conclusion:
A number of new features have been introduced in SP 2010, which enable better centralized management of metadata which plays a key role in organizing content in every organization. Each of these features play a critical role in making SharePoint Platform a good ECM System.
Source : Internet
The techniques used for optimally managing these metadata values is called ‘Metadata Management'. An easy-to-use framework has been provided by SharePoint 2010 which deals with usage of a set of centrally managed words which can be used across multiple sites as tags or attributes.
There are a number of new features that have been introduced in SharePoint 2010.
When it comes to Metadata, these are some of the basic things that we must know
1. ‘Terms‘: It refers to a word or phase that can be associated with every item.
2. ‘Term Set‘: It refers to a collection of Terms. Termsets can either be created locally or globally.
Termsets created within the scope of a site collection are referred to as Local Termsets and the ones created outside the context of a Site collection are referred to as Global Termsets.
Termset Groups are generally created by a ‘Term Store Administrator'. He designates a ‘Group Manager‘ who creates the Termsets that have to be used in lists/libraries.
"Terms' can further be classified into two categories:
1. ‘Managed Terms‘ – These are the predefined set of terms (words/ phrases) that are created by authorized users.
2. ‘Enterprise Keywords‘ – A number of tags (Keywords) are generated by the users. These are stored in an non-hierarchial list called ‘Keywords Set‘.
Inorder to pre-define the Termsets and Keywords to be used in sites, Microsoft SharePoint Team has provided a tool called ‘Term Store Management Tool‘. Some of the operations that we might want to perform using the tool are :
1. Create, modify or delete term sets and terms
2. Organize terms into a hierarchy
3. Import new terms from a .csv file
4. Promote keywords to terms.
Some of the advantages of using Managed Metadata are:
1. Consistent usage of terms and keywords across content.
2. Better search results.
Conclusion:
A number of new features have been introduced in SP 2010, which enable better centralized management of metadata which plays a key role in organizing content in every organization. Each of these features play a critical role in making SharePoint Platform a good ECM System.
Source : Internet
Sunday, May 20, 2012
Sharepoint 2010 - Document - Co-Authoring
Document - Co Authering - Work concurrently in a same document
SharePoint 2010 - Search New features
1. Refined results - We can filter the search result using the filters in the left hand side.
2. Shared folders and public folders - We can search the files in the network shared drives, folders etc
3. Icon to search windows search - Integrated with Windows search and search local files also.
4. View in browser - Link to view some files in browser rather than in client application (eg. docx files.)
5. Wild card and boolean seach keywords.
Eg : "Bala* NOT Krishnan"
Eg : "PeopleSearchResult.aspx?k=firstname:balakrishnan%20lastname:ganesan"
6. New Custom Ranking Models allow you to change the weights that are used by SharePoint Search to rank
results. Custom Ranking Models are used in conjunction with the Core Results web part.
7. SharePoint 2010 has capability to integrate FAST Search Server 2010 seamlessly.
8. SharePoint 2010 supports wildcard search.
9. Suggestions while typing search queries.
10. Improved "did you mean" suggestions togethor with suggestions for related searches.
11. Scale out the number of crawl/indexer components by adding additional servers to the farm and configuring them as crawlers which enables to increase crawl frequency, volume, and performance by distributing the crawl load among several servers, along with providing indexer redundancy if a server fails
12. Phonetic name matching and nickname matching - Users can search for a person by name without knowing the exact spelling of the name. For example, the search query "John Steal" could yield "John Steele" in the search results; results for the search query "Jeff" include names that contain "Geoff." In addition, nickname matching makes it possible for a search query for "Bill" to yield results that include "William."
Other Sharepoint 2010 new features please check the below links.
http://www.etechplanet.com/blog/sharepoint-2010-explore-new-features-and-enhancements-part1.aspx
http://www.etechplanet.com/blog/sharepoint-2010-explore-new-features-and-enhancements-part2.aspx
http://www.etechplanet.com/blog/new-features-and-enhancements-in-sharepoint-2010-part3.aspx
Saturday, May 19, 2012
Saturday, May 12, 2012
Search - Ranking Model
Other Built-in Search Models are
1. Expertise Social Distance
2. High proximity
3. Expertise
4. Name Social Distance
5. Name
6. Main People Model
7. No Proximity Model
Custom Model can be made.
Wednesday, May 9, 2012
Tuesday, May 8, 2012
Sunday, May 6, 2012
Tuesday, May 1, 2012
Subscribe to:
Posts (Atom)