我自己深入研究了这个主题，发现了一些我想分享的有趣的东西， 所以这是compare的完整列表:

I went deep into the subject myself and found interesting things i want to share, So here is the complete list of compare :

• 插件只能触发数据更改(如更新或创建记录)，但是自定义工作流程会参与流程(工作流程，对话框等)中

• Plug-in's only fire on data change like updating or creating records but custom workflows take part inside a process ( workflow, dialog, ... )

因此，工作流不仅可以在数据更改时触发，而且可以在过程中的任何时候随时随地触发.您可能已经了解到，这是实现复杂的业务逻辑所需的真正的灵活性.

As a result , workflows not only can be triggered on data change, but on demand at anytime at any point inside their process. As you might have already understood, It is the real flexibility needed for implementing complicated business logic.

插件将不接受参数或传递的数据， 但是自定义工作流程可以通过使用如下所示的InArgument属性来实现:

Plug-ins won't accept arguments or passed-data, But custom workflows make it possible by using InArgument properties like below :

[Input("Case")]     //label of the field shown in workflow
[ReferenceTarget("incident")]     //if using EntityReference, must point the type
public InArgument<EntityReference> yourArg { get; set; } //almost every data type is supported