Work with packages
You can modify, export, copy and delete a package.
To work with packages, navigate to. A list of packages appears.
For more information on packages, see Packages.
Modify a package
In the Packages list, click the package to modify.
The package opens in a new browser tab.
- Make changes as needed.
- Save the package.
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 the sub-packages. Only resources that have at least read permissions can export a package.
In the Packages list, on the context menu of the package to export, click
Alternatively, you can also export the package using the Export option on the package modeling bar.
The Export dialog box is displayed.
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.
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.
A message prompts you to download the ZIP file.
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.
Only associations of process and forms are automatically included in the package.
Skins are not included as part of associations; you need to include them as part of process export options.
The thread pools, server variables, web service references, and server XML expression variables are automatically exported.
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.
Copy a package
In the Packages list, on the context menu of the package to copy, click
A copy of the package prefixed with
Copy 1 of <package name>appears on the Packages page.
- Customize the package as needed.
- Save the package.
Delete a package
In the Packages list, on the context menu of the package to delete, click Delete.
On confirmation, the selected package is deleted.