Skip to main content

Importing rules and data by using the Import wizard

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

Import rules and data instances from your file system or repository into your Pega Platform instance by using the Import wizard. Rules, data, and other artifacts in the imported file are added to the rules that are already in this system. Use the Import wizard to upload archives 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.

Note: Access to the Import wizard might be restricted, because you should use deployment pipelines to migrate applications between environments. Deployment Manager is one method by which to implement a pipeline. For more information, see Using Deployment Manager for model-driven DevOps.

For more information about restricting access to the Import wizard, see Importing rules and data by using the Import wizard.

Note: Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.

  • Ensuring that users migrate applications with a pipeline by restricting the Import wizard

    You can restrict access to the Import wizard so that users migrate applications between environments by using a deployment pipeline instead of by importing applications through the wizard. By creating a deployment pipeline, you can use a standardized process to migrate applications.

  • Importing custom XML files for input streams

    Use custom XML files for use as an input stream by importing the XML files as a Java archive (JAR) and extracting the files using an activity.

  • Importing custom Java archives and classes

    Incorporate third-party Java functionality into Pega Platform™ by importing a Java archive (JAR) file or class.

  • Pre-import and post-import collections

    Add steps to the pre-import and post-import collections to take specific actions based on archive metadata. Pre-import steps run before every archive import attempt. Post-import steps run after every successful archive import.

  • Selecting a file to import

    Select an archive file of rules and data instances to import.

  • Setting advanced mode and reviewing the archive contents

    Optionally use advanced mode to review and select the archive contents before you import the archive. You can also set additional import options for schema and rule changes.

  • Updating dependent applications

    You can select the built-on applications for which you want to update dependent applications. If a dependent application is built on an application for which there is a later version, it is automatically updated to use the latest version of the built-on application after you import the archive.

  • Viewing and applying schema changes

    Review the list of schema changes to determine whether to proceed with the import and either automatically apply the schema changes, or download a SQL DDL script that defines the changes and manually apply the DDL to the database.

  • Inserting new instances by importing an archive

    Specify which new instances in the archive are added to the target system.

  • Addressing older instances in an import archive

    If your target system includes instances that are newer than the instances in the archive, specify which instance to keep.

  • Automatically populating new columns in existing tables

    If an import adds columns to existing tables, use advanced mode to automatically expose and populate the new columns after the import.

  • Scheduling indexes for population

    If the archive you import includes new indexes, schedule a post-import job to add and populate the new indexes.

  • Resolving pre-existing rule conflicts

    If your import archive includes rule instances that are already present in the target system, resolve the conflict before you continue the import.

  • Changing the built-on version of an application to the current version

    If you imported an application that was built on an earlier major version of Pega Platform and did not automatically update dependent applications to be built on the latest version of the application, edit the application definition to include the current version.

  • Using restore points to enable error recovery

    Restore points mark a significant point in time for your system. You can roll back to a restore point later to return the rules and data of the system to that point in time. For example, if importing an application caused problems, you might want to roll it back.

  • Pre-import and post-import collections

    Add steps to the pre-import and post-import collections to take specific actions based on archive metadata. Pre-import steps run before every archive import attempt. Post-import steps run after every successful archive import.

  • Temporary files

    Temporary files are created in temporary files directories on the Pega Platform server to temporarily contain information that is required during installation or browsing.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice