locked
Difference between workflow and Plugin in CRM 2011 RRS feed

  • Question

  • HI

    Any body help  me the main Difference between Plugin and Process in CRM 2011

    Regards

    Benarji


    Benarji Sandra-MS Dynamics CRM Developer

    Thursday, September 13, 2012 5:55 AM

Answers

  • Hi

    Sl. No

    Criteria

    Plug-in

    Workflow

    1

    Execution before or after the core platform operation (Create, Update, Delete, and so on)

    Executes immediately before or after the core operation (synchronous)

    Queued to execute after the core operation

    (asynchronous).

    2

    Performance impact on the server

    Synchronous plug-ins can increase the platform’s response time because they are part of the main platform processing. Asynchronous plug-ins have less impact on server response time because the code is run in a different process.

    Less impact on server response time because the code is run in a different process.

    3

    Security restrictions

    To register a plug-in with the platform requires a System Admin or System Customizer security role and membership in the Deployment Administrator group.

    Users can interactively create workflows in the Web application. However, to register a custom workflow activity, the deploying user must have the same security roles as those required for registering plug-ins.

    4

    Microsoft Dynamics CRM version (SKU) support

    Supported in Microsoft Dynamics CRM Online when registered in the sandbox. May be supported in partner-hosted installations at the discretion of the partner.

    Workflows without custom workflow activities are supported by all product versions. Custom workflow activities are not supported on Microsoft Dynamics CRM Online

    5

    Length of processing time

    A plug-in registered for synchronous or asynchronous execution is restricted to complete its execution within a 2 minute time limit. 

    Works well for either short or long processes.

    6

    Works when the Microsoft Dynamics CRM for Outlook client is offline

    Both online and offline are supported.

    Workflows do not execute when offline.

    7

    Process and data persistence

    Plug-ins execute to completion. Plug-ins must be written to be stateless where no in-memory data is persisted.

    Workflows can be paused, postponed, canceled, and resumed through SDK calls or by the user through the Web application. The state of the workflow is automatically saved before it is paused or postponed.

    8

    Impersonation

    Plug-ins can perform data operations on behalf of another system user.

    Workflows cannot use impersonation.

     

        

     

     

     

     

     


    Thanks & Regards Dhamodharan R

    • Proposed as answer by Parthiban.T Thursday, September 13, 2012 9:07 AM
    • Marked as answer by HIMBAPModerator Monday, December 9, 2013 9:18 AM
    Thursday, September 13, 2012 6:14 AM
  • Hello,

    The main differences are following:

    1. Workflows at the moment can be executed only in Asynchronous mode.

    2. To build workflow you don't need to have any knowledge of .Net.

    3. Workflow can be triggered On-Demand but plugin reacts only on system events.

    4. Workflow can be triggered on following events - Create, Update, Delete, Assign and Changin of State of record. Plugin can be triggered on much more system events.


    Freelance Developer for Dynamics CRM 4.0/2011

    Thursday, September 13, 2012 6:03 AM
    Moderator

All replies

  • Hello,

    The main differences are following:

    1. Workflows at the moment can be executed only in Asynchronous mode.

    2. To build workflow you don't need to have any knowledge of .Net.

    3. Workflow can be triggered On-Demand but plugin reacts only on system events.

    4. Workflow can be triggered on following events - Create, Update, Delete, Assign and Changin of State of record. Plugin can be triggered on much more system events.


    Freelance Developer for Dynamics CRM 4.0/2011

    Thursday, September 13, 2012 6:03 AM
    Moderator
  • Hi

    Sl. No

    Criteria

    Plug-in

    Workflow

    1

    Execution before or after the core platform operation (Create, Update, Delete, and so on)

    Executes immediately before or after the core operation (synchronous)

    Queued to execute after the core operation

    (asynchronous).

    2

    Performance impact on the server

    Synchronous plug-ins can increase the platform’s response time because they are part of the main platform processing. Asynchronous plug-ins have less impact on server response time because the code is run in a different process.

    Less impact on server response time because the code is run in a different process.

    3

    Security restrictions

    To register a plug-in with the platform requires a System Admin or System Customizer security role and membership in the Deployment Administrator group.

    Users can interactively create workflows in the Web application. However, to register a custom workflow activity, the deploying user must have the same security roles as those required for registering plug-ins.

    4

    Microsoft Dynamics CRM version (SKU) support

    Supported in Microsoft Dynamics CRM Online when registered in the sandbox. May be supported in partner-hosted installations at the discretion of the partner.

    Workflows without custom workflow activities are supported by all product versions. Custom workflow activities are not supported on Microsoft Dynamics CRM Online

    5

    Length of processing time

    A plug-in registered for synchronous or asynchronous execution is restricted to complete its execution within a 2 minute time limit. 

    Works well for either short or long processes.

    6

    Works when the Microsoft Dynamics CRM for Outlook client is offline

    Both online and offline are supported.

    Workflows do not execute when offline.

    7

    Process and data persistence

    Plug-ins execute to completion. Plug-ins must be written to be stateless where no in-memory data is persisted.

    Workflows can be paused, postponed, canceled, and resumed through SDK calls or by the user through the Web application. The state of the workflow is automatically saved before it is paused or postponed.

    8

    Impersonation

    Plug-ins can perform data operations on behalf of another system user.

    Workflows cannot use impersonation.

     

        

     

     

     

     

     


    Thanks & Regards Dhamodharan R

    • Proposed as answer by Parthiban.T Thursday, September 13, 2012 9:07 AM
    • Marked as answer by HIMBAPModerator Monday, December 9, 2013 9:18 AM
    Thursday, September 13, 2012 6:14 AM
  • 2.To build workflow you don't need to have any knowledge of .Net.

    This is the one of the best and suitable difference.

    Thanks

    Thursday, December 5, 2013 8:36 AM