Notifications
Announcements
No record found.
Hi,
I have one basic doubts. Can any one please clarify me.
Why we are using interface for plugin and why we are using abstract class for custom workflow.
Thanks,
Seenivasan SR
*This post is locked for comments
Please have a look on the link:
stackoverflow.com/.../why-the-plugins-implement-iplugin-interface-and-workflows-custom-inherits-the
Thanks :)
Hi Seenivasan,
This is due to design of Dynamics CRM . The Iplugin is a base interface for plugin development and to make a call inside dynamics CRM event execution system.
Custom workflow supports the registration and execution of custom workflow activities in addition to the out-of-box activities provided by Windows Workflow Foundation and using System.Activities namespace. Custom Workflow Activities are the custom CRM activity steps i.e. technically a .net assembly which are being used as a step in CRM workflows to achieve some business task which can be done using simple CRM workflow options.
Hope this helps.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
SA-08121319-0 4
Calum MacFarlane 4
Alex Fun Wei Jie 2
