SharePoint4us

• No Internet Explorer 7 support.
• With the purchase of Yammer, there is more emphasis on social media.
• Licensing: Internet sites no longer require an expensive licence, the cheaper standard server licence means that customers can host their internet and intranet on the same platform, reducing costs and providing more flexibility.
• Records and document management: no real change.
• Greater adoption of internet and open standards, enabling broader device support and integration with other services.
• Users can have SharePoint on premise, in the cloud, or a hybrid of both.
• The core ‘Search’ capability, based on FAST technology, is much richer.

• End users can “share” files with others more simply
• Better developer support
• New database storage reduces the overhead of versioned documents
• With Office Web Apps one can now edit documents on iOS devices
• Much more flexibility around images
• Video support improvements.

• Most customers will want to virtualise the SharePoint servers but they are resource intensive so should not be run on over committed hosts
• Beware of remote access requirements, which can cause slow access
• There’s no need to keep scanned and read-only files in SharePoint – it’s an expensive form of storage – it’s better to have a link to these resources in SharePoint
• Don’t underestimate the technical skills that SharePoint needs.
• Some of the SharePoint features require that other infrastructure and client components are all on the 2013 version. Fortunately SharePoint 2013 still allows to run 2010 sites, which means that one can leverage some new features like search, while continuing to use 2010 document libraries for Office 2010 users. This ability to run both in parallel is a key feature introduced in 2013 to help reduce the upgrade pain.

•   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