Creating your first custom action
Custom actions are the most recent addition to server-side extensions. They belong to the family of processes and are similar to custom workflow activities. One advantage of using a custom action, as opposed to a custom workflow activity, is that not only can they be called from a workflow, but they can also be easily called from JavaScript and even be early bound and called as an SDK message call.
In this recipe, we will convert the previously created custom workflow into a custom activity.
Getting ready
You will first need a custom workflow activity to convert into a custom action. The workflow activity created and deployed in the previous two recipes is a good candidate. Similar to previous extensions done from within Dynamics 365, a System Customizer role is required, along with a Dynamics 365 solution to contain your extension. We will reuse the existing Packt solution created in the previous chapters.
How to do it...
- In Dynamics 365, navigate to
Settings...
