Monday, May 19, 2014

Cross-site publishing in SharePoint Server 2013

In this post we will discuss about Cross-site publishing in SharePoint Server 2013. Also you can check out:

- Package and Deploy workflow in SharePoint 2013 designer

- How to Get Current Logged in User and Display Name using SharePoint 2013 REST API?

- Backup and Restore SharePoint 2013 site collection using PowerShell

Cross-Site Collection Publishing feature in SharePoint Server 2013 works like you use one or more authoring site collections to author and store content, and one or more publishing site collections to control the design of the site and to show the content. The authoring site collection contains catalogs, such as Pages libraries and lists, which contain content that is tagged with metadata. These catalogs are indexed by the search system and made available to the publishing site collection. The publishing site collection issues queries for data that has been indexed and shows it on web pages by using Web Parts that use search technology.


When you use cross-site publishing, you create and store content in a different site collection than the site collections where users view the content. The authoring site collection contains Pages libraries and lists, which have been shared as catalogs.

Below is the Steps how it works:

- You create content in libraries and lists in a site collection where cross-site publishing is enabled. You enable these libraries and lists as catalogs.

- You crawl the content in your catalog-enabled libraries and lists. This will add the catalog content to the search index.

- You add one or more Search Web Parts to the site collections where you want to display your catalog content.

- When users view a page, the Search Web Parts issue queries to the search index. Query results are returned from the search index, and shown in the Search Web Parts.

If you change the content content in an authoring site collection, the changes you make are shown across all publishing site collections that are using that same content.


Friday, May 16, 2014

Package and Deploy workflow in SharePoint 2013 designer

In this post we will discuss how to package and deploy workflow in SharePoint 2013 designer. Also you can check out:

- Create custom page layout in SharePoint 2013

- SharePoint 2013 Developer Site Template

- Timeline web part in SharePoint 2013

Now it is a bit easy to package and deploy SharePoint 2013 designer workflow. In SharePoint 2013 you can package a workflow by saving it as a template. Not all the workflows but List Workflow, Site Workflow and Reusable Workflows we can save as a template.

Package Workflow:
Open your workflow, from the Workflow Settings tab in the ribbon, click the Save as Template button in the Manage section.

This by default save the template (.wsp) to the Site Assets library.

Then we can use the template in different sires.

Deploy Workflow:
The workflow package can be deployed to a site in different farm or a site in the same farm. But we need to be sure on the two things below:

1- All workflow dependencies such as lists, libraries, columns, and content types must already exist on the new site.

2- Each dependency must have the exact name of the source dependency.

Before deploying the workflow we need to export the wsp file from the Site Assets library.

Open the SharePoint 2013 designer and then navigate to the Site Assets library where the template is located. Select the workflow template and Click the Export File button to save the template file to your local computer.

Then Open the SharePoint 2013 site which you want to deploy the workflow. Then Click Site Actions and select Site Settings. And then in the Web Design Galleries section click Solutions.

Then Click the Upload Solution button to upload the solution

One the solution uploaded successfully, Activate the solution by clicking the Activate button.

After a workflow solution has been activated for a site collection, it is available as a feature for all sub-sites. 


SharePoint 2013 designer workflow discontinued features

In this post we will see the list of discontinued features in SharePoint designer workflow. Also you can check out:

- Promoted Links App in SharePoint 2013

- Content by Search (CBS) Web Part in SharePoint 2013

- New actions in SharePoint designer 2013 workflow: Call Web Service Action and Start workflow action

Microsoft removed some of the key features of SharePoint designer workflow. But in SharePoint Designer 2013, you can still create a SharePoint 2010 Workflow and use all of the SharePoint 2010 Workflow features by choosing the SharePoint 2010 Workflow platform.

Below are some of Actions that are not there in SharePoint 2013:

- Stop Workflow
- Start Document Set Approval Process
- Set Content Approval Status
- Add List Item
- Inherit List Item Parent Permissions
- Remove List Item Permissions
- Replace List Item Permissions
- Start Approval Process
- Start Custom Task Process
- Start Feedback Process etc.

Below are the Conditions which are not there in SharePoint 2013:
If current item field equals value
Check list item permission levels
Check list item permissions

Below Steps is not there in SharePoint 2013:
Impersonation Step:

You can check out the MSDN article for a full URL.
http://msdn.microsoft.com/en-us/library/jj728659.aspx


Wednesday, May 14, 2014

Activate Group Work Site Template in SharePoint 2013

In this post we will discuss how to activate Group Work Site Template in SharePoint 2013. Also you can check out:

- What's new in Developer dashboard in SharePoint 2013?

- OAuth in SharePoint 2013

- How we will create a package to deploy the auto-hosted app to the Office Store or an App Catalog in SharePoint 2013?

This Group Work site template provides a groupware solution that teams can use to create, organize, and share information. The Group Work site template includes the Group Calendar, Circulation, Phone-Call Memo, document library, and other basic lists.

Over all this is a very useful template in SharePoint 2010.

But the bad news is Microsoft removed the Group Work Site template in SharePoint 2013.

The reason behind this is The Group Work site template was not a widely used site template. The Group Work site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection.

But it will support the migration, Existing sites that were created by using the Group Work site template will continue to operate in SharePoint 2013.

Workaround:
But If you want to include that template in SharePoint 2013, then Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\1033\XML, open WEBTEMP.XML file, find an element with 'Group Work Site' title attribute and change its Hidden attribute from FALSE to TRUE.


Tuesday, May 13, 2014

Add list item to SharePoint Online List using Client Object Model

In this post we will discuss about how to add a list item to a SharePoint Online list using SharePoint Client object model.

Also you can check out:

- How to Get Current Logged in User and Display Name using SharePoint 2013 REST API?

- Prevent new sites to be added to content databases in SharePoint 2013

- SharePoint 2013 Boundaries and Limits

Below is the JavaScript Client Object Model Code. You can put a Content Editor Web Part to add the below code to the SharePoint 2013 online public site.

var clientContext = new SP.ClientContext.get_current();

var web = clientContext.get_web();

var list = web.get_lists().getByTitle('MyTestList');

var name = document.getElementById('firstname').value;  

// Create a new list item
var itemCreateInfo = new SP.ListItemCreationInformation();

var listItem = list.addItem(itemCreateInfo);          

listItem.set_item('Title',name );

listItem.update();

This code will work for the user who has permission.


Monday, May 12, 2014

Hide page Title in SharePoint 2013

In this post we will discuss on how to hide page Title in SharePoint 2013.

Also you can check out:

- Embed word document into SharePoint 2013 site

- SharePoint 2013 App Component

- New actions in SharePoint designer 2013 workflow: Call Web Service Action and Start workflow action

1st Approach:
Open your master page using SharePoint designer 2013 and place the below code inside the head tag.

<script type="text/javascript">
    function hidePageTitle() {
        var elem = document.getElementById('pageTitle');
        elem.style.display = 'block';
    }

_spBodyOnLoadFunctionNames.push("hidePageTitle");
</script>

2nd Approach:
You can also the 2nd approach:

Click the gear in the upper-right corner

Select Site Settings

Under Look and Feel, select Title, description, and logo

Delete the text in the Title: box


Twitter Delicious Facebook Digg Favorites More