Skip to content

Commit 5bd44ef

Browse files
authored
Merge pull request #1400 from MicrosoftDocs/master
Pushing content updates live
2 parents 5c098a6 + 2719d26 commit 5bd44ef

File tree

1 file changed

+5
-2
lines changed
  • powerapps-docs/developer/common-data-service

1 file changed

+5
-2
lines changed

powerapps-docs/developer/common-data-service/plug-ins.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: "Use plug-ins to extend business processes (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
33
description: "A plug-in is a .NET assembly that you can upload to the Common Data Service. Classes within the assembly can be registered to specific events (steps) within the event framework. The code within the class provides a way for you to respond to the event so that you can augment or modify the default behavior of the platform." # 115-145 characters including spaces. This abstract displays in the search result.
44
ms.custom: ""
5-
ms.date: 1/23/2019
6-
ms.reviewer: ""
5+
ms.date: 03/27/2019
6+
ms.reviewer: "phecke"
77
ms.service: powerapps
88
ms.topic: "article"
99
author: "JimDaly" # GitHub ID
@@ -31,6 +31,9 @@ The classes in the assembly that can be registered to a step must implement the
3131

3232
Plug-ins can be configured to execute synchronously or asynchronously. A synchronous plug-in will cause the operation to wait until the code in the Plug-in completes. This has an impact on perceived performance of the system. The operations in an asynchronous plug-in are placed in a queue and are executed after the operation is completed so that the operation can complete with minimal interruption.
3333

34+
> [!NOTE]
35+
> [!INCLUDE[cc-d365ce-note-section](./includes/cc-d365ce-note-section.md)] [Write plug-ins to extend business processes (Customer Engagement)](/dynamics365/customer-engagement/developer/write-plugin-extend-business-processes)
36+
3437
## When to use plug-ins
3538

3639
People frequently compare workflows and plug-ins as the choices to apply custom business logic. There is significant overlap in the capabilities of workflows and plug-ins. Plug-ins can do everything workflows can do but the inverse is not true. But this doesn't mean you should just use plug-ins for anything that can't be done with a workflow. There are other capabilities to achieve requirements without using plug-ins.

0 commit comments

Comments
 (0)