Additional information on importing a package

This topic provides information on the items that are imported or not imported when importing a package.

• If the forms and processes use custom services, the services are automatically imported.

• A custom service group, and the items associated with the group, that is, the category, custom services, server variables, and web service references are also imported.

• Data models if they do not exist or if they are of a higher version than the one on the target system are imported.

• If the target system already has resource extensions, imported ones are added.

• Only the resource group members that do not exist on the target system are imported.

• Test plans associated with the processes (business process, case definition, fragment, business rule, skin, custom service) are imported.

• The work queue automation rules (decision tables) contained in a process are automatically imported; the resources are not included in the import, but the configuration remains the same if the same resources with the same IDs exist on the target system.

• If the same package with the same version already exists, the package is imported without any error or a warning message. If there are any different artifacts, than those artifacts are imported. Also, when you click the Rollback solution option, the target server is reverted to how it was prior to import, and if the package already exists, the package is replaced with the previous copy.

• If the package includes an item (such as saved Capture control layout, regular expression, import connection, import source, job schedule, work allocation rule, event, target, alert, category (including items within the category), process, site, theme, navigation, note type, page rendition, reporting tag, checklist data, lookup, thread pool, and persona) having the same name but a different ID as an existing item on the target system, the package is not imported and an error message is displayed.

• When importing a package, the categories behave in the following manner:

  • A category that has a different name and ID can be added to the target system.

  • A category with the same name or ID if existing on the target system cannot be added.

  • If any errors occur during import, and if you select to roll back the solution, the category is deleted on rollback.

• If the package includes the forms and processes using local assembly and when you try to import it into a tenant (On-premise multi-tenant or Azure) a warning message is displayed.

  If a process or a form assembly are exported individually, the local assemblies used within them if any are not exported. If you wish to include local assemblies also, you must export processes and forms as part of the package.