Resolve Custom Activities

When you package a workflow with a custom activity, the DLL, image, and help files automatically identified appear as dependent files. For other files, manually add them by clicking on Add Row. These files are copied to the installed path of the target environment when the package is installed.

If the workflow activity contains a custom activity, the Custom Activities File Details grid to configure the details of each file appears towards the lower section of the settings form. Use the Edit File Location button to configure the file details. The Custom Activities File Details grid replaces the settings form.

The Custom Activities File Details grid contains the following fields:

• Source: The Source fields display the values in the source environment.

• Install in Global Assembly Cache: The Install in Global Assembly Cache field is optional and is used to install the signed DLL in the GAC. When you install the package, clear the Install in Global Assembly Cache check box if the signed DLL is not required in the GAC.

• Click Add Custom Activities File Details + to add a new row for adding additional files which will be installed in the target environment. When you add a new row to include a signed DLL that is required in the GAC, select the Install in Global Assembly Cache check box.

• Click the Delete Custom Activities File Details icon to deleted the selected row. The dependent files will not be installed in the target environment.

Note:

- When you install a package with workflow containing custom activities again (that is in Update mode) but with modifications to custom activity files, the modifications are not reflected in the target environment. In such cases, create a new Package Template and then install the same.

- When you uninstall a package with workflow containing custom activities, the custom activity files will not be removed.

- When you generate a package with workflow containing custom activities, the context-sensitive help for the properties (not the activity) will not be included in the Package Template. In such cases, manually add (using Add Row property) the context-sensitive help files, if required.

- The files available to add using the Add Row property must be relative to the AVEVA Work Tasks installation path as you cannot add files outside of the installation path.

- If the absolute path mentioned in action.xml is the installed path then the files are copied in the target environment.

- If the absolute path mentioned in action.xml is not the installed path then the files are not copied in the target environment. The files are copied to the Global Assembly Cache. You must manually copy the files to the path mentioned in the action.xml.

To correct custom activity during package design or install, see Correct Custom Activities.