Export a package

You can export a package for reuse. A package is exported as a .ZIP file.

The exported package includes all the items associated with the package along with subpackages. Only resources that have at least read permissions can export a package.

Export a package in any of the following ways:

  • For recommended approach to automated export of packages, see Automated export and import of packages in Kofax TotalAgility Best Practices Guide.

  • Once you complete creating a package, click Export on the Modeling bar. See Create a package.

  • From the context menu of the package on the Packages list page. See Work with packages.

  • Using the Export option. See the instructions below.

  1. Navigate to Export.
  2. On the Export list, select Package.
  3. On the Package list, select the package to export.

    The deployment configurations defined in the package appear on the Deployment list.

  4. To include the deployment configuration in the package, on the Deployment list, select a deployment type.
  5. By default, no deployment is selected and all the deployment configurations defined in the package are exported. To include the deployment configuration in the package, on the Deployment list, select a deployment type.
    Note The deployment configurations settings for the selected deployment type are exported and the values for the global variables, server variables, web services and device settings defined in the base package as applicable, are overwritten with the values from the selected deployment type. For example, if the server variable value in a base package is BaseDB and the server variable value in the production deployment type is ProductionDB, after export, BaseDB is overwritten with ProductionDB.
  6. Click Export.

    A message prompts you to download the package ZIP file.

  7. Click Yes.
    The package is exported. If any errors occur during export, Error.txt is generated with the error details. In some scenarios, a warning message is displayed and the package is not exported.

    • The associations of process and forms are automatically included in a package. The custom services associated with a process and form are also included.

    • The thread pools, server variables, web service references, field validators and server XML expression variables are automatically exported.

    • When exporting a package that includes custom service group, the items associated with the group, that is, the category, custom services, server variables and web service references are automatically exported.

    • The skins are only included in the package if selected as process export option.

    • Any associated reporting tags are exported.

    • All images included in the package are exported in the Images folder.

    • Any document templates, custom pages, .Net Dlls and style sheet are exported in the Assets folder.

      The .Net DLLs are only exported, if they have been added to the package manually.

    • Depending on the selected options for the device settings (include devices, device profiles and device settings), an XML-formatted string package is generated using the stored data inside the Device Manager database, and these properties are included in the package when exporting.