Deciding when to use a workflow vs. a plug-in is usually a straight forward process. In general, I always recommend using workflow to automate business processes especially if the business process will be later modified/maintained by “business” people (non IT).
However, there are some characteristics that will guide you to use one versus the other that do require you to know a bit more details of the task that you are trying to achieve. For example, if you require performing an action right away, let’s say when a record is updated (synchronous), then you have to use plug-ins because workflows are always asynchronous.
The following table gives a quick comparison between workflows and plug-ins and when to use each one, hope you find it useful.
Humberto Lezama Guadarrama
PingBack from http://www.travel-hilarity.com/airline_travel/?p=5496
Freaky CRM Link Love for June 2008
Okay, so I'll give you a baker's dozen of some really good stuff from the perspective of a Microsoft
In MS CRM 4.0 SDK ,under the Plugin topics ,(Registration Of Plugins programmatically specifically) ,its given that ,for custom workflow activities fist create the instance of a plugin assembly for your custom activity assembly.Next, create an instance of a plugintype for each custom workflow activity class in your assembly. Finally, set the PluginAssembly property of RegisterSolutionRequest and execute the request.
I don't understand the words "custom workflow activity".
Can any one please help me in this matter.
What are Plug-in Entities?Can anybody share their comment on this?.
cAn anybody tell me how to create lookup record?