The steps that classic workflows and action processes can perform are limited; for example, there is no capability to handle many-to-many relationships. You cannot add a contact to a marketing list, or remove a case from a queue using a workflow.
Developers can extend the capabilities of classic workflows and actions by writing custom workflow activities in C# and uploading a .NET assembly to the CDS.
Typical custom workflow actions that you might require are the following:
- Date/time functions; for example, date difference and business day calculations
- String functions; for example, trim
- Regex functions; for example, phone number validation
- List functions; for example, add and remove a contact to/from a marketing list
- Calculations; for example, tax
These functions appear as additional steps in the workflow editor. You add these custom actions as steps like any other step and set their properties.
Creating custom actions is outside the scope...
