Resolve Script Activity References

While adding a workflow to a package template, if the workflow contains Script Activity, the Resolve Assembly Path grid appears in the workflow settings form.

While installing a package, you can use the Resolve Assembly Path grid to resolve the assembly file path in the target environment.

The custom assembly files (DLLs) referenced in the workflow are automatically identified and appear in the package settings form.

The Resolve Assembly Path grid contains the following fields:

• Assembly Name [Action Name]: Displays the assemblies used in a workflow and the actions in which the assemblies are referenced. If one or more DLLs reference the same path, then the DLLs are displayed as comma separated list with their respective action name in the Assembly Name [Action Name] fie.

• Source Assembly Path: Displays the referenced DLL paths in the source environment.

• Target Assembly Path: Displays the referenced DLL paths in the target environment. The DLLs are copied to the same path in the target environment, as mentioned in the Source Assembly Path. To copy the DLLs to a different location in the target environment, enter the path in the Target Assembly Path.

  You can also specify the target assembly path of your choice in the Target Assembly Path field. In this case, ensure that the target assembly path you specify is valid and the files exist in it before you install the package. If the files do not exist in the path, then manually copy the files to the target environment .

  If the target assembly path is not valid or the files do not exist in it, then the workflow is installed in draft status (with the invalid assembly path) and you will not be able to publish the workflow. The following message appears in the pre-install validation:

  Files referenced in script activity do not exist (Workflow cannot be published) : <target assembly path\DLL name>

While entering the assembly path, ensure to follow the scripting guidelines as mentioned in Script - References topic.

While packaging a workflow with script activity, the package recognizes the DLLs or assemblies referenced in the script activity. However, these DLLs or assemblies are not packaged. Add these assemblies to the Additional Package Files to package the assemblies also in the package template. Using the additional package files, you can also install the assemblies referenced in the script activity along with the workflow.