Third-party Activity Examples

In this example, there are two activity assemblies that are added to the system with a category of "Custom Activities":

First Assembly

  • Assembly: ActivityAssembly1.dll
  • Dependencies: ActivityAssembly1Dependency1.dll, ActivityAssembly1Dependency2.dll

Second Assembly

  • Assembly: ActivityAssembly2.dll
  • Dependencies: (none)

All assemblies need to be copied to the following location:

\Program Files\Proficy\Proficy Workflow\Applications\Workflow

ActivityExtensions.dita

The ActivityExtenions.dita file contains the necessary information and path locations for the 3rd party assemblies to be used with Workflow. Continuing our example utilizing ActivityAssebly1.dll and ActivityAssembly2.dll from above, including their dependencies, the ActivityExtensions.dita file should contain the following code:

<ActivityExtensions xmlns="http://schemas.datacontract.org/2004/07/Proficy.Workflow.Services">
  <ActivityExtension>
    <AssemblyUri>net.tcp://localhost/Workflow/ActivityAssembly1.dll</AssemblyUri>
    <Category>Custom Activities</Category>
    <DependencyAssemblyUris>
      <DependencyAssemblyUri>net.tcp://localhost/Workflow/ActivityAssembly1Dependency1.dll</DependencyAssemblyUri>
      <DependencyAssemblyUri>net.tcp://localhost/Workflow/ActivityAssembly1Dependency2.dll</DependencyAssemblyUri>
    </DependencyAssemblyUris>
  </ActivityExtension>
  <ActivityExtension>
    <AssemblyUri>net.tcp://localhost/Workflow/ActivityAssembly2.dll</AssemblyUri>
    <Category>Custom Activities</Category>
    <DependencyAssemblyUris/>
  </ActivityExtension>
</ActivityExtensions>

Result

After the assembly DLL and DLL dependencies are placed, and the ActivityExtensions.dita is created, you must restart the Proficy Server service and Workflow client. Upon opening up a new workflow in the Workflow Editor, you will see your new assemblies below the Activity Toolbox.