This is an accompanying blog post to my YouTube video Dynamics 365 Customer Engagement Deep Dive: Creating a Basic Custom Workflow Assembly. The video is part of my tutorial series on how to accomplish developer focused tasks within Dynamics 365 Customer Engagement. You can watch the video in full below:
Below you will find links to access some of the resources discussed as part of the video and to further reading topics:
Full Code Sample
Source Code Management Solutions
- Visual Studio Team Services - Free for up to 5 users and my recommended choice when working with Dynamics 365 Customer Engagement
MSDN - Update a custom workflow activity using assembly versioning (This topic wasn’t covered as part of the video, but I would recommend reading this article if you are developing an ISV solution involving custom workflow assemblies)
You can also check out some of my previous blog posts relating to Workflows:
- Implementing Tracing in your CRM Plug-ins - We saw as part of the video how to utilise tracing, but this post goes into more detail about the subject, as well as providing instructions on how to enable the feature within the application (in case you are wondering why nothing is being written to the trace log :) ). All code examples are for Plug-ins, but they can easily be repurposed to work with a custom workflow assembly instead.
- Obtaining the User who executed a Workflow in Dynamics 365 for Customer Engagement (C# Workflow Activity) - You may have a requirement to trigger certain actions within the application, based on the user who executed a Workflow. This post walks through how to achieve this utilising a custom workflow assembly.
If you have found the above video useful and are itching to learn more about Dynamics 365 Customer Engagement development, then be sure to take a look at my previous videos/blog posts using the links below:
- Dynamics 365 Customer Engagement Deep Dive: Creating a Basic Plug-in
- Dynamics 365 Customer Engagement Deep Dive: Creating a Basic Jscript Form Function