SharePoint4us

Hi friends, Thanks for visiting my blog . In this post i would like to post about Office 365 and its importance.so lets get started...

What is Office 365  and Getting started with it ?

SharePoint Online is a cloud-based service that helps organizations share and collaborate with colleagues, partners, and customers. With SharePoint Online, you can access internal sites, documents, and other information from anywhere—at the office, at home, or from a mobile device.

Hi friends,

Thanks for visiting my blog.


In this Post i would like to describe about "SharePoint Workflows".

•   Introduction to workflows.
• .Why we need Workflow?
•  Common Workflow Scenario.
•  Reusable and Non-Reusable Workflows.
•  Typical Workflow Usage in SharePoint
• Designer, Visio and Visual Studio
• Declarative & Compiled Workflows
•  Out of the Box Workflows

 Introduction to workflows.

            Workflows help people to collaborate on documents and to manage project tasks by implementing business processes on documents and items in a Microsoft Office SharePoint Server 2007 site. Workflows help organizations to adhere to consistent business processes, and they also improve organizational efficiency and productivity by managing the tasks and steps involved in business processes. This enables the people who perform these tasks to concentrate on performing the work rather than managing the workflow.

                                        

Why we need Workflow?

Workflow provides a convenient way to automate manual business processes.

The activities in the Workflow can be represented in a graphical manner and adds great flexibility to a developer and non-developer. Using Workflow we can easily achieve the branching, cases and executions in an easier manner

Common Workflow Scenario

We can apply Workflow for the following scenarios.

Scenario 1: A task list allows creation of task for users. Whenever a new task is created in the list, we need to notify the user associated with it. We can use Workflow to accomplish this easily.

Scenario 2: A company consists of developers with various skill sets. There is a set of Training Items. Each developer can apply for the training. The application will be notified to the Training Manager. He can check the skill set and approve or reject the applicant. If selected, the applicant can attend the training. On completion of training there is a verification exam to be undergone by the attendee. If he passes then Certificate is issued else the notification through email is done. We can use Workflow to accomplish this easily.

Scenario 3: People upload their expense reports into a Document Library. The library captures the expense as a separate field. Every week manager has to change status to Approved for the expenses with less than $ 500. The list contains hundreds of entries. The status updation can be done using Workflow in just 1 minute.

Scenario 4: Client can create a bug and it should be notified to Developer through email. Developer on completion of the bug fix changes the status and the Client gets notified. This whole process can be done through Workflow in an easier manner.

Reusable and Non-Reusable Workflows

In the case of SharePoint 2007 the workflow created for one list cannot be used for another list. But in SharePoint 2010.2013  the same workflow can be applied for multiple lists and thus making it Reusable. We can create reusable workflows using SharePoint Designer 2010,2013

Typical Workflow Usage in SharePoint

• Developer creates the Workflow.
• Administrator deploys the Workflow
• Site Users use the Workflow.

Designer, Visio and Visual Studio

The SharePoint Designer provides an easier way for Administrators and Developers to create Workflows. Along with Microsoft Visio, Designer provides much more flexibility and features in Workflow creation.

Using Visual Studio developers can write more complex programming tasks with Workflow. Using the SharePoint extensions for Visual Studio, the inbuilt templates provide easier Workflow creation and deployment.

Declarative & Compiled Workflows

The workflows created using SharePoint Designer are known as Declarative workflows.

The workflows containing code and contained inside DLL files are known as Compiled workflows. They are usually created using Visual Studio 2010. 

Workflow Creators

·         A workflow can be created by:

·         Administrator

·         Developer

·         Power User

·          

Workflow Association

·         A workflow can be associated with the following:

·         Content Type

·         List / Library

·         Site

This makes easier to understand that a Workflow can be started manually or automatically.

Workflow Forms

Following are the types of forms associated with workflow:

1. Initiation Forms are shown to user when they start a workflow. The initiation form is used to capture parameters associated with a workflow.

Examples of parameters include Receiver Email list, Maximum Amount etc.

2. Association Forms are used to associate a workflow with a particular list or content type. The association form is by the Administrator.

In reality the Initiation form can be the same as Association form. The user can override the Association form settings using the Initiation form.

We can provide custom Initiation & Association forms using InfoPath as well.

                          Out of the Box Workflows

Following are the Out of the Box Workflows in SharePoint 2010:

·         Three-state

·         Disposition Approval

·         Collect Signatures

·         Collect Feedback

·         Approval

Hi friends,

Thanks for visiting my blog .

In this post, i would like to describe about "Getting multiple users from SharePoint list Programatically".

Scenario : 
I came across a situation where i want to fetch the usernames and email IDs   from list (Column is people Picker and Check the "allow multiple users" option).

Solution : 

Please find the the below code snippet
*********************************

 SPFieldUser UsersColumn = (SPFieldUser)lstNewPrsReq.Fields.GetField("ColumnName");
 SPFieldUserValueCollection Users = (SPFieldUserValueCollection)UsersColumn.GetFieldValue(lstitemCollection[0]["ColumnName"].ToString());   
   if (Users != null)
     {                                 
  foreach (SPFieldUserValue user in Users)
               {
                        SPUser spUser = user.User;                    
                        if (spUser != null)                                               
                        strCCEmail = strCCEmail + ";" + spUser.Email;
                }                                                                           
          strCCEmail = strCCEmail.TrimStart(';');                             
     }      


strCCEmail : This string contains all the mail ids of the users for that particular list item.

hope this blog helps you........

Hello,

In this post i am going to give you an overview on client side rendering using JSLink in SharePoint 2013.

Client side rendering is nothing but transformation of data at client side. Using this we can do branding on SharePoint List Views, Fields, Search Results etc. This is pretty easy to implement like  changing the look and feel of default web parts like list view web parts.

Lets start with implementation. I have used below script to render an Announcements list view fields. Copy the below script in to your js file.

Java Script:

(function () {
    /*
     * Initialize the variable that store the overrides objects.
     */
var overrideCtx = {};
overrideCtx.Templates = {};

   // Assign functions or plain html strings to the templateset objects:
   // header, footer and item.

overrideCtx.Templates.Header =
    "<div class='WebpartBGColor'><div class='AnnouncementWebpart Webpart'><div class='WebpartHeader'><a href='<#=ctx.listUrlDir#>'><h3 class='Blue'><#=ctx.ListTitle#></h3></a>" +
    "<a href='<#=ctx.newFormUrl#>' id='AnnouncementWebpart' class='Links' ><span>"+ "CONTRIBUTE"  +"</span></a></div>" +
    "<div class='WebpartBody'><div class='ContentArea'><div class='SlideContent' id='Announcement'><ul class='ItemContent'>";

overrideCtx.Templates.Footer = "</ul></div></div><div class='row-fluid AnnouncementWebpartFooter'><div class='ArrowBlock' ><a class='Prev'></a><a class='Next'></a></div></div></div></div>";

 // This template is assigned to the CustomItem function.
overrideCtx.Templates.Item = CustomItem;
overrideCtx.BaseViewID = 1;
overrideCtx.ListTemplateType = 104; //Announcements list template id

 //  Register the template overrides.

SPClientTemplates.TemplateManager.RegisterTemplateOverrides(overrideCtx);

})();

/*
 * This function builds the output for the item template.
 * Uses the Context object to access announcement data.
 */
function CustomItem(ctx) {

    if(!ctx.BasePermissions.ManageLists)
    {
      $(document).ready(function(){

      $('#AnnouncementWebpart').addClass('Hide');
     });
    }
 
    var cUrl = window.location.href;
    // Build a listitem entry for every announcement in the list.
    var ret = "<li><div class='row-fluid'><div class='span4'><a href=" + ctx.listUrlDir + "/DispForm.aspx?ID=" + ctx.CurrentItem.ID +
              "&Source=" + cUrl + ">" ;
           
              if(ctx.CurrentItem.AnnouncementImage.indexOf("img") > 0)
              {
             
                ret = ret +"<div class='Image'>" + ctx.CurrentItem.AnnouncementImage+ "</div></div></a>";
              }
              else
              {
           
                ret = ret + "<div class='Image'>" + "<img src='/Style Library/images/DefaultImage.png' />" + "</div></div></a>";
              }
              ret = ret + "<div class='span8'><div class='Title'>" + ctx.CurrentItem.Title+ "</div>" +
           
              "<div class='ReadmoreLink'><a href=" + ctx.listUrlDir + "/DispForm.aspx?ID=" + ctx.CurrentItem.ID +
              "&Source=" + cUrl  + ">" + "Read More..." + "</a></div></div></div></li>";
           
return ret;
}



You need to have below css classes which are used in the above script. Copy below css  to your css file.

CSS:

.AnnouncementWebpart{
position:relative;
padding:12px 15px;
height:135px;
overflow:hidden;
}
.AnnouncementWebpart .WebpartHeader{
width:100%;
float:left;
margin:0px;
padding:0px;
}

.AnnouncementWebpart .SlideContent{
width:100%;
float:left;
height:100px;
overflow:hidden;
margin:0px;
padding:0px;
}


.AnnouncementWebpart li{
height: 100px;
display:none;
}

.AnnouncementWebpart .Image{
width:30%;
height:110px;
float:left;
}

.AnnouncementWebpart .Image img{
width:100px;
height:100px;
border:1px #ccc solid;
}

.AnnouncementWebpart .Title{
color:#333 !important;
width:70%;
height:60px;
overflow:hidden;
float:left;
overflow:hidden;
}

.AnnouncementWebpart .ReadmoreLink{
width:70%;
float:left;
}

.AnnouncementWebpart .ReadmoreLink a,
.AnnouncementWebpart .ReadmoreLink a:link,
.AnnouncementWebpart .ReadmoreLink a:active,
.AnnouncementWebpart .ReadmoreLink a:visited,
.AnnouncementWebpart .ReadmoreLink a:focus,
.AnnouncementWebpart .ReadmoreLink a:hover{
color:#0088cc !important;
}

.AnnouncementWebpart .WebpartFooter {
position:relative;
width:55px;
height:25px;
right:9px;
margin-top:-20px;
float:right;
text-align:right;
z-index:9999;
}

.AnnouncementWebpart .WebpartFooter a.ButtonLeft{
display:block;
float:left;
height:25px;
width:25px;
cursor:pointer;
background-image:url('../../../../../Style%20Library/images/LeftIcon.gif');
}
.AnnouncementWebpart .WebpartFooter a.ButtonRight{
display:block;
float:left;
height:25px;
width:25px;
cursor:pointer;
background-image:url('../../../../../Style%20Library/images/RightIcon.gif');
}
.AnnouncementWebpart .WebpartFooter a{
border:0px;
}


To use this script you have to create an announcements list. In that create a publishing image column named 'AnnouncementImage'. Using the above script i have branded announcements list view to a customized view with scrolling of all announcements having right and left arrows and having 'CONTRIBUTE' link to add the announcements, which can be visible if user having sufficient permissions to add announcement.

Add items and images in to announcements list and perform following activities to achieve the above context.

Add announcements list view web part on to a page

Upload the js file having above script in to style library

Add the js file path to JS link reference of the list view web part

Associate the css file having above classes to the page

Now we are done! You can see a different look of Announcements list view web part on the page.

Thanks!!!

A list definition includes a Feature.xml file, an element manifest file (see List Template Files), and a Schema.xml file within a Feature folder (%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\FEATURES).
 
In Visual Studio 2012 select File | New Project
Select Templates | Visual C# | Office/SharePoint | SharePoint 2013 – Empty Project

If you don’t see this type of project available then you may need to download and install the Microsoft Office Developer Tools for Visual Studio 2012
Provide a name and location for the project/solution and OK
In the SharePoint Customization Wizard Prompt, configure the server to use for developing/debugging. If possible you will want to try and achieve a Sandboxed solution over a Farm Solution due to it’s ability to be able to be reused in more scenarios requiring less permission is the SharePoint environment.

Once the new solution has been created, we can use the new Visual Designer to create the List Definition. Right click the project in the solution explorer and select Add | New Item


Select Visual C# Items | Office/SharePoint | List, provide a name and click OK


Provide a display name for the list. We just want to create a list definition, not an instance of the list; This isn’t an option so what we do instead is go with the “Create a customizable list template and a list instance of it” and we will make some mods to the generated project files to remove the list instance so we are just left with the definition.


You should now see the list instance and definition files in solution explorer.

If you select the SettingsProfile in the solution explorer you will get the new List Visual Designer. Notice the “List” tab, this represents the instance of the list.


Since we only want the list definition, we are going to delete the list instance files from solution explorer. Select SettingProfileInstance, right-click and Delete.


You should now be left with just the list definition, the “List” tab will now be greyed out.

 You Can able  to see the list names in quick launch

Managed Metadata is a hierarchical collection of terms that can be associated with items in SharePoint 2010. We can use Central Administration website to manage these terms.

 Managed Metadata Service.
 The managed metadata service application makes it possible to use managed metadata and share content types across site collections and web applications.
A managed metadata service publishes a term store and, optionally, content types; a managed metadata connection consumes these. This article describes the managed metadata service and connections, and provides an example scenario for using them.

Metadata  
 Metadata is information about information. For example, the title and author is metadata about the book. Metadata can be many kinds of information -- a location, a date, or a catalog item number. When you use SharePoint products, you can manage the metadata centrally. You can organize the metadata in a way that makes sense in your business and use the metadata to make it easier to find what you want. 

 This is a new feature introduced  in SharePoint 2010.

Example: You have a document library to upload chapters. For each item you can specify a column metadata of category like CSharp, ASP.NET etc.
Create a List Column