We need to implement business logic to assign an issue to the team member who has been assigned with the fewest issues. This requirement can't be implemented using the OOB functionality; however, we can develop custom business logic using a different option. The two main options are to use a plugin or a custom workflow. Both options can be used to implement business requirements based on the developers' choices and the requirement details. The plugins and custom workflows have their own features. We can review these differences in the following table:
|
Plugin |
Custom workflow |
|---|---|
|
A plugin can either be executed synchronously or asynchronously. |
A workflow can be executed asynchronously only. |
|
A plugin is supported on all deployment models. |
A custom workflow is supported only on on-premise deployment. |
|
Configuration or medication of a plugin requires a technical resource. |
Once a custom workflow is written by a technical resource, a non-technical resource can configure the workflow using CRM UI. |
|
A plugin is most suitable when we need a response without any delay. |
A workflow is the best option when there might be a delay in the result. |
|
A plugin supports multiple event. We can refer Message entity support for plugins to get all supported events. This file comes with Microsoft CRM 2011 SDK. |
A workflow can be configured for some specific event available in the workflow designer. |
|
We can register images in a plugin. |
We cannot register an image for a workflow. |
Tip
Very soon, we are going to get a Microsoft CRM 2011 service update, which will allow us to write a custom workflow for Microsoft CRM 2011 online as well. You can refer to http://gustafwesterlund.blogspot.in/2012/04/workflow-activities-in-crm-online.html for more information on this.