——————————————————————————–
http://office.microsoft.com/en-us/windows-sharepoint-services-help/introduction-to-content-types-HA010121570.aspx

What is a content type?
In the course of a single project, a business might produce several different kinds of content, for example, proposals, legal contracts, statements of work, and product design specifications. Although these documents might be stored together because they are related to a single project, they can be created, used, shared, and retained in different ways. A business might want to collect and maintain different kinds of metadata about each kind of content.

Windows SharePoint Services 3.0 enables organizations to define these different sets of documents as content types. A content type is a group of reusable settings that describe the shared behaviors for a specific type of content. Content types can be defined for any item type in Windows SharePoint Services 3.0, including documents, list items, or folders. Each content type can specify:

The columns (metadata) that you want to assign to items of this type.
The document template on which to base new items of this type (document content types only).
The custom New, Edit, and Display forms to use with this content type.
The workflows that are available for items of this content type.
The custom solutions or features that are associated with items of this content type.
Content types provide organizations with a way to manage and organize content consistently across different lists and libraries in a site collection (site collection: A set of Web sites on a virtual server that have the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more subsites.), and they also make it possible for a single list or library to contain multiple item types or document types.

————-

A content type is a reusable collection of metadata (columns), workflow, behavior, and other settings for a category of items or documents in a Microsoft SharePoint Foundation 2010 list or document library. Content types enable you to manage the settings for a category of information in a centralized, reusable way.

For example, imagine a business situation in which you have three different types of documents: expense reports, purchase orders, and invoices. All three types of documents have some characteristics in common; for one thing, they are all financial documents and contain data with values in currency. Yet each type of document has its own data requirements, its own document template, and its own workflow. One solution to this business problem is to create four content types. The first content type, Financial Document, could encapsulate data requirements that are common to all financial documents in the organization. The remaining three, Expense Report, Purchase Order, and Invoice, could inherit common elements from Financial Document. In addition, they could define characteristics that are unique to each type, such as a particular set of metadata, a document template to be used in creating a new item, and a specific workflow for processing an item.

Content Type Scope

The Microsoft SharePoint Foundation site in which you create a content type determines its scope—that is, the extent of its availability. A site content type becomes available to lists and document libraries within the site on which the content type is created, and also to lists and document libraries in any child site.

Content Type Features
——————————————————————————–

Content types are a site-scoped Feature. Features are a way of encapsulating SharePoint Foundation functionality for ease of distribution and deployment. Features provide a mechanism by which you can package the files that a solution needs, such as content types, Web Parts, lists, and site definitions. You can package the necessary files into a .wsp file, which is basically a .cab file that contains a manifest that lists its contents.

Inside the Feature, the feature.xml file contains references to all the element manifests within that Feature. Content type definitions are element manifests. You must create a content type definition for each content type that is included in your Feature.

Plugin Developer

writing Workflows

Form Builder

Different Views:

Form View

Advanced Find

Lookup Views

Quick View

Associated View

–

On Demand Workflow

Manual workflow

On REcord is Created/deleted

Record status change

Record is assigned

Record field is changed

Status and Status Reason Values for Select Entities

Entity Status values Status Reason values

Account    Active Inactive                         Active Inactive

Case           Active Resolved  Canceled          In Progress On Hold  Waiting for Details Researching Problem Solved Canceled

Lead        Open  Qualified Disqualified         New Contacted Qualified  Lost  Cannot Contact  No Longer Interested Canceled

—

System Jobs to monitor

Workflow step editor  : define steps in workflow

Code :

using System;
using System.IO;
using System.Net;
using System.ComponentModel;
using System.ComponentModel.Design;
using System.Collections;
using System.Workflow.ComponentModel.Compiler;
using System.Workflow.ComponentModel.Serialization;
using System.Workflow.ComponentModel;
using System.Workflow.ComponentModel.Design;
using System.Workflow.Runtime;
using System.Workflow.Activities;
using System.Workflow.Activities.Rules;
using Microsoft.Crm.Sdk;
using Microsoft.Crm.SdkTypeProxy;

using Microsoft.Crm.Workflow;
using Microsoft.Crm.Workflow.Activities;
using Microsoft.Crm.Sdk.Query;

namespace Updatingincident
{
[CrmWorkflowActivity("updating incident", "cal")]

public partial class calculate : SequenceActivity
{
protected override ActivityExecutionStatus Execute(ActivityExecutionContext executionContext)
{

IContextService contextService = (IContextService)executionContext.GetService(typeof(IContextService));
IWorkflowContext context = contextService.Context;

ICrmService crmService = context.CreateCrmService();

WhoAmIRequest systemUserRequest = new WhoAmIRequest();
WhoAmIResponse systemUser = (WhoAmIResponse)crmService.Execute(systemUserRequest);

// using the GUID of current case

ColumnSet cols = new ColumnSet();
Guid guidID = new Guid(this.objectID.Value.ToString());

incident ret = (incident)crmService.Retrieve(EntityName.incident.ToString(), guidID, new AllColumns());

DateTime a = DateTime.Parse(this.startdate.date);

DateTime b = DateTime.Parse(this.enddate.date);

TimeSpan tid = b – a;

CrmNumber tes = new CrmNumber();
tes.Value = tid.Days;
// i will use existing field on CRM incident to hold the integer value.

ret.actualserviceunits = tes;

// updating the case entity
crmService.Update(reto);

return ActivityExecutionStatus.Closed;
}

// getting the id of case

public static DependencyProperty objectIDProperty = DependencyProperty.Register(“objectID”, typeof(Lookup), typeof(calculate));

[CrmInput(" objectID")]
[CrmReferenceTarget("incident")]
public Lookup objectID
{
get
{
return (Lookup)base.GetValue(objectIDProperty);
}
set
{
base.SetValue(objectIDProperty, value);
}

}

// start date as input parameter

public static DependencyProperty startdateProperty = DependencyProperty.Register(“startdate”, typeof(CrmDateTime), typeof(calculate));

[CrmInput(" startdate")]

public CrmDateTime startdate
{
get
{
return (CrmDateTime)base.GetValue(startdateProperty);
}
set
{
base.SetValue(startdateProperty, value);
}
}

// End date as input parameter

public static DependencyProperty enddateProperty = DependencyProperty.Register(“enddate”, typeof(CrmDateTime), typeof(calculate));

[CrmInput(" enddate")]

public CrmDateTime enddate
{
get
{
return (CrmDateTime)base.GetValue(enddateProperty);
}
set
{
base.SetValue(enddateProperty, value);
}
}

}
}

Register the assembly

Now we need to register the Custom assembly as pulgin . I would be using plugin developer to register this assembly.

In MS CRM for a task go to workflows -> Add Step Conditio-> WorkflowUtilities

 ————

Add Step choices available  to you with the workflow editor:

Check conditions

 Wait conditions

 Workflow actions

 Stages

CRM 4.0 Concepts: What are Leads, Contacts and Opportunities?

http://www.sharepointmonitor.com/register/?redirect_to=http://www.sharepointmonitor.com/2010/02/custom-workflows-sharepoint-designer-2010/2/

types of workflows:

1.List

2.Content Type (Reusable )

3. Sites

Out of box workflows:

1.Approval

2.Collect feedback

3.Collect signature

4. Three state

5. Disposition

6,Translation Mngt

Defining sharepoint custom sequential workflow thru code:

http://msdn.microsoft.com/en-us/library/gg265727.aspx

When to go for Visual Studio workflows in place of sharepoint designers:

When should I use Visual Studio for Workflow?

As I mentioned earlier SharePoint Designer (SPD) is a great platform for developing basic workflows, however it has several limitations and in some cases these can mean that you have to look at Visual Studio as the solution for your workflow design.

In my experience the limitations of SPD are as follows:

1. Workflows are bound to a specific list/site
    In SPD any workflow you create can only exist on the list (and in the site) that you created the workflow on.  You cannot design a workflow and then move it to another site.
2. No code support
   You cannot write custom code within the SPD workflow tools.  You can write custom activities to include in SPD, but you would need to do that in Visual Studio anyway.
3. No WSS Solution Package (WSP) support
   Your workflow will be deployed to the site via SPD and there is no support for packaging these as WSP files, which provide a more maintainable and upgradeable method of deploying customisations to SharePoint.
4. No support for State Machine workflows
   You can only build Sequential workflows with SPD, there is no support for State Machine Workflows.

Microsoft SharePoint Server 2010 includes several approval workflows that you can begin using right away to manage human workflows in your organization. Each workflow can be added to a list, library, or content type and then used by your business users to manage the items or documents in the associated lists or libraries.

You can use the workflows to run document approvals, collect feedback, collect signatures, manage publishing of assets, manage dispositions, and create three-state approvals. When you associate and initiate the workflow, you can change the basic behaviors of the workflow, like who approves it, how the tasks are assigned, duration, due dates, workflow messages, and so on. For most of the workflows, you can also customize them in SharePoint Designer 2010.

Each workflow is described below, including the main differences between the workflows, and whether they’re supported for customization in SharePoint Designer 2010.

If you use Sharepoint Designer to build workflows, sometimes you will feel the need of some extra actions in the designer (see below).Well Microsoft has provided with a class to do that, this class is call it DependencyProperty. MSDN defines the DependencyProperty like this: Represents a property that can be set through methods such as, styling, data binding, animation, and inheritance.

How does Sharepoint works?

The browser sends a DAV packet to IIS asking to perform a document check in. PKMDASL.DLL, an ISAPI DLL, parses the packet and sees that it has the proprietary INVOKE command. Because of the existence of this command, the packet is passed off to msdmserv.exe, who in turn processes the packet and uses EXOLEDB to access the WSS, perform the operation and send the results back to the user in the form of XML

http://www.codeguru.com/csharp/.net/net_asp/miscellaneous/article.php/c15953/

My article on  “Creating Check All Uncheck All Grid view Web part with Paging, Sorting Functionalities in SharePoint 2007 in a Step by Step Manner ” was published in CodeProject.com site.

And the url is http://www.codeproject.com/KB/sharepoint/GridviewSharepoint.aspx

another article was published in CodeProject
 ”Creation of a SPGridview webpart having pagination, sorting , filtering functionalities in sharepoint site in step by step manner”. Link is http://www.codeproject.com/KB/sharepoint/SPGridviewWebpart.aspx

Codeproject article name is
Creating CheckAll UncheckAll Gridview webpart with Paging,Sorting functionalities in Sharepoint 2007 in step by
step manner
and the link is :
http://www.codeproject.com/KB/sharepoint/GridviewSharepoint.aspx

Creation of a SPGridview Webpart having Pagination, Sorting, Filtering Functionalities in Sharepoint Site in Step by Step Manner   http://www.codeproject.com/KB/sharepoint/SPGridviewWebpart.aspx

Creating CheckAll UncheckAll Gridview Webpart with Paging, Sorting Functionalities in Sharepoint 2007 in a Step by Step Manner    http://www.codeproject.com/KB/sharepoint/GridviewSharepoint.aspx

Part 1: Installing Features and Adding Breadcrumbs to Custom Pages in Sharepoint Central Administrat

http://www.codeguru.com/csharp/.net/net_asp/miscellaneous/article.php/c15953__3/

A Sp is taking 45min to execute How do improve the performance for this SP
– Firstly look for joins and remove unnecessary columns in select statement
– See the execution plan and analyse where the more cost is taking
– If possible try to create indexes and again see the performance
– If it is an OLTP database, create a view with index Row_Number function
What are the enhancements provided in SQL 2008 at performance level.
What are the tasks done by you in SSIS (Integration Services)
difference between Trigger and Check Constraint
How many system databases are there and what does each db do
Advantages of View Table Partitions Types of Trigger
 .Net How do u enable paging for a grid with improved performance.

I have two tables (table1 and table2). I want to set a flag in table1 for
each common row with table2. I

Solution:

Update

iwf_requestdetails

set

LastUpdatedStatus=f.Status_ID

from

iwf_requestdetails i innerjoin [FinalWorkflowDetails1] f

on

i.[FormNo] = f.[FORM_NO]

TABLE #ActiveCustomer

(

RowID

intIDENTITY(1, 1),

formno

varchar(50),

adddel

varchar(50),

optionid

varchar(50)

)

DECLARE

@NumberRecords int, @RowCount

int

DECLARE

@form_no varchar(50),@previousform_no varchar(50),@add_del varchar(50), @option_id varchar(50

)

INSERT

INTO #ActiveCustomer(formno,adddel,optionid

)

select form_no, add_del, option_id from dbo.iws_kapiti_optionsorderby form_no

SET

@NumberRecords =

@@ROWCOUNT

SET

@RowCount =1

WHILE

@RowCount <= @NumberRecords

BEGIN

SELECT

@form_no = formno,@add_del = adddel,@option_id = optionid

FROM

#ActiveCustomer

WHERE

RowID = @RowCount

if

@add_del =

‘A’

begin

end

if

@add_del =

‘D’

begin

end

SET @RowCount = @RowCount + 1

END

DROP

TABLE#ActiveCustomer