What is Yammer and Its Relation to SharePoint 2013?

According wiki’s definition Yammer is a freemium enterprise social network service that was launched in 2008 and sold to Microsoft at 1.2 billion in 2012. Yammer is a remote communication mode in between the organization. With a Yammer, you’re always connected to your coworkers, and can take part in the information flow and conversations. Get into your network to find what exactly you need and determine or find out that you didn’t know to make decisions quickly, and later get the work done and keep moving.

Today social media networking is not just making an impact on our day to day life but even organizations are taking big decisions over these enterprise social networking. According to Gartner, over 75% of Fortune 1000 companies will undertake some kind of online social-networking initiative for marketing or customer relations purposes by 2014. In today’s article we will discuss why Microsoft bought Yammer and what is the relation between Yammer and SharePoint 2013.

 When we talk about SharePoint 2010 its features and social networking were pretty elementary. At this point of time many organizations felt embarrassed and had turn to other third party vendors like Yammer and NewsGator for the social networking within the organization. But here buying Yammer gave Microsoft that insight of being a cut-throat competitor in the enterprise of social space and was an indication to the market that they are willing to take any bold steps when it comes to business. Yammer has been adopted by many organizations and brought fortune of experience around this social enterprise. Before that social functionality was almost in a nonexistent state when organizations were using SharePoint 2010 and here Microsoft buying Yammer into the industry showcased an impact and presence where they were desperately needed to make big moves.

But when SharePoint introduced 2013 they actually learnt from their previous mistakes and they came with a portal integrated with fully advance features and social networking. Personally speaking, you won’t find any major difference if you compare Yammer and SharePoint 2013. However, SharePoint 2013 has extended all the social media features which allows you to create community sites, post micro-blogs, use hash tags with #, and mention colleague’s name with @ and communities etc.; but if we compare it with Yammer or NewsGator its still require more of improvements and advancements.

The biggest advantage of Yammer over SharePoint is cost effectiveness. Yammer gives free networking, collaboration. You can access Yammer from anywhere. But with the fall of 2013 it got integrated with SP 2013 to provide more connections and features. Although, there isn’t a much clear story about this integration of Yammer and SharePoint 2013 experience. If I like to contribute in this personally, I can see Yammer, Office 365, and SharePoint Online integrating really well and have lots of potential in becoming a dynamic, collaborative social online environment.

However if we look further deep into this, for the clients who are using on-premise installations of SharePoint, they will either end up with some unrealistic Yammer integration paired with overpowering SharePoint social features, or may be SharePoint social features on their own. For organizations that have yet to dip into any significant enterprise social technologies, SharePoint 2013 will likely be sufficient as they wade into the social enterprise space. Nevertheless, it’s always sensible to go for any technology first looking at your work culture and notion. If it’s fit into the ideology and seems cost effective and have the capabilities to make your system seamless then one should go for such technology without thinking twice. At the end I am just leaving an open ended question for you all; so which will you use? Yammer, or SharePoint 2013 Social?

co-produced with the help of a web app development company that expertise in enterprise application development using SharePoint 2013.

What is Yammer and Its Relation to SharePoint 2013?

Posted by Sophina Dillard No comments

According wiki’s definition Yammer is a freemium enterprise social network service that was launched in 2008 and sold to Microsoft at 1.2 billion in 2012. Yammer is a remote communication mode in between the organization. With a Yammer, you’re always connected to your coworkers, and can take part in the information flow and conversations. Get into your network to find what exactly you need and determine or find out that you didn’t know to make decisions quickly, and later get the work done and keep moving.

Today social media networking is not just making an impact on our day to day life but even organizations are taking big decisions over these enterprise social networking. According to Gartner, over 75% of Fortune 1000 companies will undertake some kind of online social-networking initiative for marketing or customer relations purposes by 2014. In today’s article we will discuss why Microsoft bought Yammer and what is the relation between Yammer and SharePoint 2013.

 When we talk about SharePoint 2010 its features and social networking were pretty elementary. At this point of time many organizations felt embarrassed and had turn to other third party vendors like Yammer and NewsGator for the social networking within the organization. But here buying Yammer gave Microsoft that insight of being a cut-throat competitor in the enterprise of social space and was an indication to the market that they are willing to take any bold steps when it comes to business. Yammer has been adopted by many organizations and brought fortune of experience around this social enterprise. Before that social functionality was almost in a nonexistent state when organizations were using SharePoint 2010 and here Microsoft buying Yammer into the industry showcased an impact and presence where they were desperately needed to make big moves.

But when SharePoint introduced 2013 they actually learnt from their previous mistakes and they came with a portal integrated with fully advance features and social networking. Personally speaking, you won’t find any major difference if you compare Yammer and SharePoint 2013. However, SharePoint 2013 has extended all the social media features which allows you to create community sites, post micro-blogs, use hash tags with #, and mention colleague’s name with @ and communities etc.; but if we compare it with Yammer or NewsGator its still require more of improvements and advancements.

The biggest advantage of Yammer over SharePoint is cost effectiveness. Yammer gives free networking, collaboration. You can access Yammer from anywhere. But with the fall of 2013 it got integrated with SP 2013 to provide more connections and features. Although, there isn’t a much clear story about this integration of Yammer and SharePoint 2013 experience. If I like to contribute in this personally, I can see Yammer, Office 365, and SharePoint Online integrating really well and have lots of potential in becoming a dynamic, collaborative social online environment.

However if we look further deep into this, for the clients who are using on-premise installations of SharePoint, they will either end up with some unrealistic Yammer integration paired with overpowering SharePoint social features, or may be SharePoint social features on their own. For organizations that have yet to dip into any significant enterprise social technologies, SharePoint 2013 will likely be sufficient as they wade into the social enterprise space. Nevertheless, it’s always sensible to go for any technology first looking at your work culture and notion. If it’s fit into the ideology and seems cost effective and have the capabilities to make your system seamless then one should go for such technology without thinking twice. At the end I am just leaving an open ended question for you all; so which will you use? Yammer, or SharePoint 2013 Social?

co-produced with the help of a web app development company that expertise in enterprise application development using SharePoint 2013.

What is SharePoint Newsfeed App in SharePoint 2013 and What Can You Do with It?

When SharePoint 2013 was launched it came with many interesting features and mobile capabilities which helped people to work in team more productively. In this, one of the feature is SharePoint Newsfeed. It is nothing but a form of social media for the enterprise people which helps users to stay in touch with their enterprise social network on SharePoint itself through tablets and mobile phones etc., by straining posts and comments on a site feed and providing the ability to take part in all the conversations which are required.

It was initially available in some precise SharePoint configurations including SharePoint Server 2013 and Office 365 SharePoint Online, Newsfeed is a new tool that lets you see what’s going on in your organization throughout the day, as well as share your own ideas, updates and observations. After this, it was introduced for iOS platforms and other mobile platforms and later they also introduced it for Windows 8.

What is SharePoint Newsfeed App in SharePoint 2013 and What Can You Do with It?

Posted by Sophina Dillard No comments

When SharePoint 2013 was launched it came with many interesting features and mobile capabilities which helped people to work in team more productively. In this, one of the feature is SharePoint Newsfeed. It is nothing but a form of social media for the enterprise people which helps users to stay in touch with their enterprise social network on SharePoint itself through tablets and mobile phones etc., by straining posts and comments on a site feed and providing the ability to take part in all the conversations which are required.

It was initially available in some precise SharePoint configurations including SharePoint Server 2013 and Office 365 SharePoint Online, Newsfeed is a new tool that lets you see what’s going on in your organization throughout the day, as well as share your own ideas, updates and observations. After this, it was introduced for iOS platforms and other mobile platforms and later they also introduced it for Windows 8.

Amazing 11 New Features of SharePoint 2013 Content Management

Microsoft SharePoint 2013 is a new and better version of SharePoint 2010. SharePoint 2013 has better features and provide improved user experience. Today we will be discussing top 11 features of SharePoint 2013 which are improving the quality of content management.

Those features are-

#1 Drag and drop

Document library comes with drag and drop features now. Drag and drop the document on the page and it will upload with the quick progress bar.

#2 Call-up menu

In this new version, ECB menu is replaced with ‘call-up-menu’. It’s a call-out popup which displays preview of an item and actions which a user can take.

#3 Download a copy

With this feature, end users can download the copy of the document to their local. It’s a very direct and easy way to perform this task.

#4 Print to PDF

With this feature, you can convert your word doc into PDF and also directly send it for printing. This saves a lot of time of the user and simplifies the action.

#5 Follow and share feature

Now users can share their documents with other users, groups etc. with just one click. This feature is a social feature which has been introduced under SharePoint 2013. Owner can also follow the document himself in order to see its progress.

#6 Find a file

Find a file has been added to each document library which helps the user to find files within the library while working on a project. It’s a real-time search function.

#7 Assets library

The new and improved asserts library give the access to the user to upload digital asset with the out-of-box views like thumbnails and video page etc. in a very interactive way.

#8 Video page and Thumbnail

Every time a user upload a new video in asserts library, an evasion videoplayerpage.aspx gets formed in which you can view video and the metadata. This page will also create a thumbnail with which you can later upload the metadata for the video.

#9 Introduction of people

Another feature has been added to this version of SharePoint “People in videos”. Now the user can specify the people in the video as part of their company in the metadata. One can use this feature in the properties of the video.

#10 Cut and paste from word

The user can now directly copy & paste directly from the word document into any other text field as per his requirement. This feature saves lot of time of the user.

#11 Image renditions

This is one of the amazing features of SharePoint 2013, this feature helps in visualizing different sized versions of images on different pages. You can specify the width and height for all the images as per your requirement.

All the above mentioned features are just some of the prominent features of SharePoint 2013. There are so many more features which will lead the user by surprise. After understanding the whole SharePoint, we can certainly say that it’s a product made for the future.

Amazing 11 New Features of SharePoint 2013 Content Management

Posted by Sophina Dillard No comments

Microsoft SharePoint 2013 is a new and better version of SharePoint 2010. SharePoint 2013 has better features and provide improved user experience. Today we will be discussing top 11 features of SharePoint 2013 which are improving the quality of content management.

Those features are-

#1 Drag and drop

Document library comes with drag and drop features now. Drag and drop the document on the page and it will upload with the quick progress bar.

#2 Call-up menu

In this new version, ECB menu is replaced with ‘call-up-menu’. It’s a call-out popup which displays preview of an item and actions which a user can take.

#3 Download a copy

With this feature, end users can download the copy of the document to their local. It’s a very direct and easy way to perform this task.

#4 Print to PDF

With this feature, you can convert your word doc into PDF and also directly send it for printing. This saves a lot of time of the user and simplifies the action.

#5 Follow and share feature

Now users can share their documents with other users, groups etc. with just one click. This feature is a social feature which has been introduced under SharePoint 2013. Owner can also follow the document himself in order to see its progress.

#6 Find a file

Find a file has been added to each document library which helps the user to find files within the library while working on a project. It’s a real-time search function.

#7 Assets library

The new and improved asserts library give the access to the user to upload digital asset with the out-of-box views like thumbnails and video page etc. in a very interactive way.

#8 Video page and Thumbnail

Every time a user upload a new video in asserts library, an evasion videoplayerpage.aspx gets formed in which you can view video and the metadata. This page will also create a thumbnail with which you can later upload the metadata for the video.

#9 Introduction of people

Another feature has been added to this version of SharePoint “People in videos”. Now the user can specify the people in the video as part of their company in the metadata. One can use this feature in the properties of the video.

#10 Cut and paste from word

The user can now directly copy & paste directly from the word document into any other text field as per his requirement. This feature saves lot of time of the user.

#11 Image renditions

This is one of the amazing features of SharePoint 2013, this feature helps in visualizing different sized versions of images on different pages. You can specify the width and height for all the images as per your requirement.

All the above mentioned features are just some of the prominent features of SharePoint 2013. There are so many more features which will lead the user by surprise. After understanding the whole SharePoint, we can certainly say that it’s a product made for the future.

List Event Handlers In SP 2013 To Perform Duplicate Check

While implementing practical solutions as a SharePoint consultant, the need to perform duplicate checks of different lists is a very common scenario.

Here is a real world example you may come across. Your client needs two lists, one to store regional information and one to store country specific information. The regional list, along with different information pertaining to a region, will also store an acronym for that region (e.g. EMEA, APAC, etc.). Similarly, the country list also will store the country acronym (FR, RU, IN, etc.) among other relevant country information. And this acronym data will be used in many places to accomplish many business requirements.

In most cases, we can easily utilize the OOB concept to validate the uniqueness of the columns. But to validate across different lists we need to provide some customization. We can achieve this in various ways.

In this article we will handle this validation through the event handler. We are assuming that a project from a SharePoint template is already created.

As shown in the image below, firstly we’re going to add an event receiver, select the list to which the event handler needs to work , check the item added and item being updated (as we need to validate during edits as well).

Please repeat this for the regional list as well.

Now we will write our validation code in the event receiver. Let us write for the “Adding” scenario first. In this code we will check if the acronym exists in the other list, if yes, we will cancel the addition. The code will be as shown below. Please update the column names as appropriate.

public override void ItemAdding(SPItemEventProperties properties)
        {
            base.ItemAdding(properties);
           
           
            properties.AfterProperties["Country_Acronym"] = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();
            string newAcronym = ((string)(properties.AfterProperties["Country_Acronym "])).Trim();

            if (!CheckDuplicateAcronym(properties.List, properties.ListItemUniqueId, newAcronym, "Ctry_Acronym", "Text"))
            {
                //check in Country Profiles list
                SPList LegalEntityProfilesList = properties.Web.Lists.TryGetList("Country Profiles");
                if (CheckDuplicateAcronym(LegalEntityProfilesList, new Guid(), newAcronym, "country", "Text"))
                {
                    //cancel the event with error
                    properties.ErrorMessage = "Acronym already exist";
                    properties.Status = SPEventReceiverStatus.CancelWithError;
                    return;
                }
            }
        }

The generic duplicate checking function
public static bool CheckDuplicateAcronym(SPList List, Guid ItemId, string NewAcronym, string AcronymFieldName, string AcronymFieldType)
        {
            bool bAcronymExists = false;
            try
            {
                SPQuery query = new SPQuery();
                query.Query = @"<Where>" +
                    "<Eq>" +
                    "<FieldRef Name='" + AcronymFieldName + "' />" +
                    "<Value Type='" + AcronymFieldType + "'>" + NewAcronym + "</Value>" +
                    "</Eq>" +
                    "</Where>";

                SPListItemCollection items = List.GetItems(query);
                if (items != null)
                {
                    if (items.Count > 1)
                    {
                        bAcronymExists = true;
                    }
                    else if (items.Count == 1)
                    {
                        bAcronymExists = !(items[0].UniqueId == ItemId);
                    }
                    else
                    {
                        bAcronymExists = false;
                    }
                }
            }
            catch { }
            return bAcronymExists;

        }

The code is written in such a way that you can reuse this function for any list or for any field type by passing the relevant parameters. Even this function will take care of the updating scenario duplicate validation.
Next we’ll write the updating part of the code, as shown below. In the updating scenario we will pass the unique ID of the item rather than new GUID which we passed in the above adding scenario.
public override void ItemUpdating(SPItemEventProperties properties)
        {
            base.ItemUpdating(properties);
            properties.AfterProperties["Country_Acronym"] = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();

            string newAcronym = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();
            if (0 != string.Compare(newAcronym, properties.ListItem["Country_Acronym"].ToString(), true))
            {

                if (!CheckDuplicateAcronym(properties.List, properties.ListItemUniqueId, newAcronym, "Ctry_Acronym", "Text"))
                {
                   
                    SPList LegalEntityProfilesList = properties.Web.Lists.TryGetList("Country Profiles");
                    if (CheckDuplicateAcronym(LegalEntityProfilesList, new Guid(), newAcronym, "country", "Text"))
                    {
                        //cancel the event with error
                        properties.ErrorMessage = "the Acronym value already exist";
                        properties.Status = SPEventReceiverStatus.CancelWithError;
                        return;

                    }
                }
                else
                {
                    //cancel the event with error
                    properties.ErrorMessage = "the Acronym value already exist";
                    properties.Status = SPEventReceiverStatus.CancelWithError;

                }
            }

        }

That’s it! This event receiver can now be reused for duplicate validation of any number of lists.

Authored by:

Alvin Ubiera is a Microsoft SharePoint Technologist at the Houston-based business software provider, Rand Group and is a regular contributor to Dynamics 101. He hails from the sunny Dominican Republic and has varied experience in architecture, web development, and SharePoint.

List Event Handlers In SP 2013 To Perform Duplicate Check

Posted by Sophina Dillard No comments

While implementing practical solutions as a SharePoint consultant, the need to perform duplicate checks of different lists is a very common scenario.

Here is a real world example you may come across. Your client needs two lists, one to store regional information and one to store country specific information. The regional list, along with different information pertaining to a region, will also store an acronym for that region (e.g. EMEA, APAC, etc.). Similarly, the country list also will store the country acronym (FR, RU, IN, etc.) among other relevant country information. And this acronym data will be used in many places to accomplish many business requirements.

In most cases, we can easily utilize the OOB concept to validate the uniqueness of the columns. But to validate across different lists we need to provide some customization. We can achieve this in various ways.

In this article we will handle this validation through the event handler. We are assuming that a project from a SharePoint template is already created.

As shown in the image below, firstly we’re going to add an event receiver, select the list to which the event handler needs to work , check the item added and item being updated (as we need to validate during edits as well).

Please repeat this for the regional list as well.

Now we will write our validation code in the event receiver. Let us write for the “Adding” scenario first. In this code we will check if the acronym exists in the other list, if yes, we will cancel the addition. The code will be as shown below. Please update the column names as appropriate.

public override void ItemAdding(SPItemEventProperties properties)
        {
            base.ItemAdding(properties);
           
           
            properties.AfterProperties["Country_Acronym"] = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();
            string newAcronym = ((string)(properties.AfterProperties["Country_Acronym "])).Trim();

            if (!CheckDuplicateAcronym(properties.List, properties.ListItemUniqueId, newAcronym, "Ctry_Acronym", "Text"))
            {
                //check in Country Profiles list
                SPList LegalEntityProfilesList = properties.Web.Lists.TryGetList("Country Profiles");
                if (CheckDuplicateAcronym(LegalEntityProfilesList, new Guid(), newAcronym, "country", "Text"))
                {
                    //cancel the event with error
                    properties.ErrorMessage = "Acronym already exist";
                    properties.Status = SPEventReceiverStatus.CancelWithError;
                    return;
                }
            }
        }

The generic duplicate checking function
public static bool CheckDuplicateAcronym(SPList List, Guid ItemId, string NewAcronym, string AcronymFieldName, string AcronymFieldType)
        {
            bool bAcronymExists = false;
            try
            {
                SPQuery query = new SPQuery();
                query.Query = @"<Where>" +
                    "<Eq>" +
                    "<FieldRef Name='" + AcronymFieldName + "' />" +
                    "<Value Type='" + AcronymFieldType + "'>" + NewAcronym + "</Value>" +
                    "</Eq>" +
                    "</Where>";

                SPListItemCollection items = List.GetItems(query);
                if (items != null)
                {
                    if (items.Count > 1)
                    {
                        bAcronymExists = true;
                    }
                    else if (items.Count == 1)
                    {
                        bAcronymExists = !(items[0].UniqueId == ItemId);
                    }
                    else
                    {
                        bAcronymExists = false;
                    }
                }
            }
            catch { }
            return bAcronymExists;

        }

The code is written in such a way that you can reuse this function for any list or for any field type by passing the relevant parameters. Even this function will take care of the updating scenario duplicate validation.
Next we’ll write the updating part of the code, as shown below. In the updating scenario we will pass the unique ID of the item rather than new GUID which we passed in the above adding scenario.
public override void ItemUpdating(SPItemEventProperties properties)
        {
            base.ItemUpdating(properties);
            properties.AfterProperties["Country_Acronym"] = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();

            string newAcronym = ((string)(properties.AfterProperties["Country_Acronym"])).Trim();
            if (0 != string.Compare(newAcronym, properties.ListItem["Country_Acronym"].ToString(), true))
            {

                if (!CheckDuplicateAcronym(properties.List, properties.ListItemUniqueId, newAcronym, "Ctry_Acronym", "Text"))
                {
                   
                    SPList LegalEntityProfilesList = properties.Web.Lists.TryGetList("Country Profiles");
                    if (CheckDuplicateAcronym(LegalEntityProfilesList, new Guid(), newAcronym, "country", "Text"))
                    {
                        //cancel the event with error
                        properties.ErrorMessage = "the Acronym value already exist";
                        properties.Status = SPEventReceiverStatus.CancelWithError;
                        return;

                    }
                }
                else
                {
                    //cancel the event with error
                    properties.ErrorMessage = "the Acronym value already exist";
                    properties.Status = SPEventReceiverStatus.CancelWithError;

                }
            }

        }

That’s it! This event receiver can now be reused for duplicate validation of any number of lists.

Authored by:

Alvin Ubiera is a Microsoft SharePoint Technologist at the Houston-based business software provider, Rand Group and is a regular contributor to Dynamics 101. He hails from the sunny Dominican Republic and has varied experience in architecture, web development, and SharePoint.

Significance of Using SharePoint for Public Facing Websites

Public facing websites are not password-protected or in other words are not blocked from the general Internet. It is freely accessible by all internet users. It has all the information about the company's business, their products and services, contact information, company history and even may have links to other related web sites of their company. It is an information source about a company for its customers and its partners.

Microsoft is still claiming SharePoint Server as the fastest growing product in company history; they have claimed there are so many fortune 500 companies that have built their public facing websites on SharePoint. SharePoint usage is widely spread due to its complex collaboration structure and its flexibility. From enterprise search, enterprise content management (ECM), Business Process Management, business intelligence, records management, archiving, Intranet/Extranet, file sharing to public-facing websites etc. list of few companies using SharePoint for public facing websites are – ConocoPhillips, Procter & Gamble, Kroger, Valero Energy, Dell, Kraft Foods, Viacom, and more.

Significance of Using SharePoint for Public Facing Websites

Posted by Sophina Dillard No comments

Public facing websites are not password-protected or in other words are not blocked from the general Internet. It is freely accessible by all internet users. It has all the information about the company's business, their products and services, contact information, company history and even may have links to other related web sites of their company. It is an information source about a company for its customers and its partners.

Microsoft is still claiming SharePoint Server as the fastest growing product in company history; they have claimed there are so many fortune 500 companies that have built their public facing websites on SharePoint. SharePoint usage is widely spread due to its complex collaboration structure and its flexibility. From enterprise search, enterprise content management (ECM), Business Process Management, business intelligence, records management, archiving, Intranet/Extranet, file sharing to public-facing websites etc. list of few companies using SharePoint for public facing websites are – ConocoPhillips, Procter & Gamble, Kroger, Valero Energy, Dell, Kraft Foods, Viacom, and more.

SharePoint 2013 Community Site Creation Best Practices

We all agree that Microsoft SharePoint 2013 is awesome and it is offering all these new features to developers and enterprises. A particular feature which everybody is really excited about is “Community Sites”.

What is Community site?

With this feature the user can create communities to discuss anything related to SharePoint 2013 or otherwise. The user can also invite other people to be a part of this community. There is a point as well as badges system for the users who reply and post on the threads. The user can configure this feature only on the live site.

Some of the best practices which the user must adopt while creating a community sites are-

SharePoint 2013 Community Site Creation Best Practices

Posted by Sophina Dillard No comments

We all agree that Microsoft SharePoint 2013 is awesome and it is offering all these new features to developers and enterprises. A particular feature which everybody is really excited about is “Community Sites”.

What is Community site?

With this feature the user can create communities to discuss anything related to SharePoint 2013 or otherwise. The user can also invite other people to be a part of this community. There is a point as well as badges system for the users who reply and post on the threads. The user can configure this feature only on the live site.

Some of the best practices which the user must adopt while creating a community sites are-

App Development Models of SharePoint 2013

Microsoft has big plans to move towards SaaS (software-as-a-service) model. The latest version of Microsoft SharePoint 2013 has seen many improvement in comparison to 2010 version of SharePoint. Microsoft is in the progression of emerging a model which allows users to have an

instant access of SharePoint.

Over a period of time, Microsoft is able to understand what their customers expect from them. Keeping the need of the market in mind, they have launched SharePoint 2013. This version allows user to create, translate and manage domain-specific content from various online sources from intranet and internet.

App Development Models of SharePoint 2013

Posted by Sophina Dillard No comments

Microsoft has big plans to move towards SaaS (software-as-a-service) model. The latest version of Microsoft SharePoint 2013 has seen many improvement in comparison to 2010 version of SharePoint. Microsoft is in the progression of emerging a model which allows users to have an

instant access of SharePoint.

Over a period of time, Microsoft is able to understand what their customers expect from them. Keeping the need of the market in mind, they have launched SharePoint 2013. This version allows user to create, translate and manage domain-specific content from various online sources from intranet and internet.