File Distribution

The following list describes the behavior of the custom file distribution in a package module:

Note: The dll files having names starting with SE.BPM., SE.TOKENPROVIDER, WORKTASKS, WORKFLOW, XMLRESOURCEHANDLER.NET2 will not be included while creating the package.

• While installing the package, if the target environment contains files that are not versioned then these may not be overwritten.

• When you uninstall a package containing custom dependent files, the 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 AVEVA Work Tasks installation path.

• We recommend to package custom files from AVEVA Work Tasks relative path. When you package the custom files from a non-relative path of AVEVA Work Tasks, all package files get installed in the [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\BIN folder.

  • While installing the package containing custom dependent files, if the source folder is relative to the AVEVA Work Tasks installed path, and the folder does not exist in the target machine, then a new folder is created and the file is copied to it. For example, if the path of the CustomEmployee.dll file is C:\Program files\AVEVA\Work Tasks\\Custom Folder\CustomEmployee.dll, then a folder named Custom Folder is created in the target machine and CustomEmployee.dll is copied to it.

  • While installing the package containing custom dependent files, if the source folder is not relative to the AVEVA Work Tasks installed path then the files are copied to [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\BIN folder. For example, if the path of the file CustomEmployee.dll is C:\Custom Folder\CustomEmployee.dll, then CustomEmployee.dll is copied to the [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\BIN folder in the target machine. 

• Only strong-named assemblies can be installed into the GAC. Ensure that you select the GAC option accordingly for packages.

Note: As the installation path for AVEVA Work Tasks 2023 R2 is different, the existing packages in the repository having custom files pointing to old path may not work as expected when the product is upgraded.