Share
ReportIn which scenarios shall we go for a Plugin and which scenarios shall we opt for a custom Workflow (iworkflow)
You’re offline. This is a read only version of the page.
In which scenarios shall we go for a Plugin and which scenarios shall we opt for a custom Workflow (iworkflow)
Hi,
The comparison and points are for Code Activity and plugins. Where I say workflow it means Custom Code Activity.
You need to think in perspective of workflow, because the Custom Code Activity is used in a workflow.
When it comes coding part, both look similar (except parameters). Both are .Net class libraries.
Only thing, differentiates them is custom code activities works in a workflow (process) and registered only for limited events. However, plugins can be registered on more supported events.
Hi Wahaj Rashid,
thanks for the detailed explanation,
I was particularly looking for the difference between an codeActivity workflow (which we build using c# code) and a plugin. from the development perspective, is there any advantage choosing one over the other ?
Hi,
Thank you for your query.
When it comes to coding possibilities, I do not see any limitation in one or other.
Your decision should depend on on following:
In my opinion, Custom Code Activities should be preferred if you do not need to register your code on a special message. However, if your requirement is to intercept more complex events (like GrantAccess, RetreiveMultiple, you have to opt for Plugin.
Also, plugins can be used for more generic tasks as you can register same code with multiple entities (if your code handles it).
Here is a similar thread for your reference:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (