Create and deploy workflow libraries using the Developer Toolkit

 

Applies To: Dynamics CRM 2013

Your solution must contain a workflow library project before you can create a plug-in. For more information about how to add a workflow library project, see Create a new Developer Toolkit project.

For more information about creating custom workflow assemblies, see Custom workflow activities (workflow assemblies).

In This Topic

Workflow project

Create and deploy a workflow library

Workflow project

The workflow project provides support for implementing custom workflow activities. Workflow activities that are added to the project that are based on the CRM workflow activity template accelerate the starting point for development. The class generated from the template simplifies some of the common code that is required by many workflow activities including:

• Obtaining execution context.

• Obtaining the tracing service.

• Instantiating the Organization Service proxy.

Create and deploy a workflow library

Use the following procedure to create and deploy a workflow library:

1. In the workflow project, right-click the workflow project node and select Add and then select New Item.

2. In Add New Item – Workflow dialog box, in the Dynamics CRM group of installed templates select the Workflow Activity Class template.

3. Enter the Name of the class you would like to be generated, and then click Add.

4. In the Custom Workflow dialog box specify field values for your workflow activity according to the descriptions in the following table.

   Field	Description
   Name	The name of the workflow activity.
   Friendly Name	A more user friendly name for the type.
   Activity Group Name	The name of the submenu added to the main menu in the Microsoft Dynamics CRM process designer.
   Description	A description of the workflow activity.

5. Open the generated class and add your custom workflow business logic where indicated by the comment // TODO: Implement your custom Workflow business logic..

6. In the Properties of the workflow project, on the Signing tab, select the Sign the assembly check box and set the strong name key file of your choice.

   At a minimum, you must specify a new key file name and do not protect your key file that uses a password.

7. If you are deploying your workflow activity to Microsoft Dynamics CRM Online, you must edit the RegisterFile.crmregister file.  Locate the existing IsolationMode attribute for the workflow and change the value from "None" to "Sandbox".

8. Right-click the CRMPackage project and select Deploy.

   This builds the dependent projects and deploys the workflow activity to the Microsoft Dynamics CRM server. Any subsequent changes to the workflow activity are pushed to the server during the build and deploy process.

Note

You may get the error: Error registering plug-ins and/or workflows. Public Assembly must have public key after you have signed the assembly as described in step 6, when the solution contains a plug-in project that is not signed. All plug-in and workflow library projects must be signed.

See Also

Developer Toolkit for Microsoft Dynamics CRM 2013
Custom workflow activities (workflow assemblies)
Install or uninstall the Developer Toolkit
Developer toolkit features
Create a new Developer Toolkit project
Deploy a solution using the developer toolkit
Create and deploy plug-ins using the Developer Toolkit
Create and deploy XAML workflows using the Developer Toolkit
Create and deploy web resources using the Developer Toolkit