Importing a file using the Import wizard

Use the Import wizard to import rules and data instances from a .zip file, JAR file, or application bundle into your current Pega Platform system. Use this form to upload files up to 1 GB in size; for larger files, use File Transfer Protocol (FTP) or another means to place the file into the ServiceExport directory.

To import a file, do the following steps:

1. Access the Import wizard by clicking Designer Studio > Application > Distribution > Import.

2. Select a new or existing file to import:
   1. To import a new file, use the field to browse to and select the local file, upload the file to the server, then click Next.
   2. To select a file that is already on the server, click Next.

3. Select the file to import from the list.

4. Optional: To view the components of the file and select individual instances to load, click Show content details.

5. Optional: To display a detailed view of the contents of the imported file on the next screen, select the Enable advanced mode to provide more granular control over the import process check box.

6. Optional: Opt not to create a restore point or save metadata. Although it is a best practice to create restore points and save metadata, if you must limit import time, select Do not set restore point or save metadata. If you do not create a restore point, you cannot roll back to the current state of your system.

7. Click Next to begin import operations. If you selected the check box in step 4, click Next again.

   During the import process, the system confirms that each imported ruleset version has the same or a higher ruleset version identified as a prerequisite. For example, you cannot import a product archive exported from a Pega Platform 05-03-01 system into a Pega Platform 04-02-60 system.

8. If applicable, respond to missing dependency error messages:

   If a dependency is missing from the target system, you see an error message. You can opt to either stop the import, or allow the import to continue with missing dependencies. The best practice depends on the specific missing item and your system:

   • If the only error message refers to missing hotfix dependencies and recommends that you ignore the missing dependencies, check Allow import with missing dependencies and click Next to continue the import.
   • For production systems, if you see any other error message, cancel the import, correct the missing dependency, and repeat the import.
   • For testing or development systems, if you see any other error message, you can opt to either cancel the import, or allow the import to continue with missing dependencies. If there are missing dependencies and you continue with the import, some rules may not work correctly.

9. To close the form, click Done.

Open topic with navigation