Exporting configuration items from the source environment

You can export configuration items. The export process creates a JAR file, which is automatically saved to the repository. You can also download the migration file to save it locally.

Important: Use this migration process if you want to export a questionnaire template with question dependencies, response actions, and other data. If you use FastMap to export a questionnaire template, you don't get all the components and data associated with the template.

Before you begin

You must be logged in as an OpenPages® administrator who has the ExportConfiguration application permission. You must also have read and write access to the Migration Documents folder. For more information, see Types of application permissions.

The export will fail if you have invalid triggers. Disable triggers before you export.

About this task

Important:
  • If a background import, export, or validate configuration process is currently running on the system, you must wait until processing is complete before submitting another configuration job.
  • You cannot export while in System Admin Mode (SAM). For more information, see System Admin Mode (SAM).
  • The export will fail if you have invalid triggers. Disable triggers before you export.

Procedure

  1. Log on to the source OpenPages application as an administrator.
  2. Disable System Admin Mode, if it is enabled. For more information, see Enabling and disabling System Admin Mode.
  3. If you want to migrate hidden settings, set Show Hidden Settings to true.
  4. Click Open Administration menu Administration menu > System Migration > Export Configuration.
  5. Click Add Items.
  6. Select the items that you want to export.
    For example, if you want to export profiles, click Object Profiles and then select the profiles that you want to export.

    You can select items from multiple categories.

  7. Optional: If you want to export an item, but don't want to export other items that it is dependent on, select Do not include dependencies.

    For example, if you want to export views without its dependent object and field definitions, select Do not include dependencies.

    This option is not available for all export items.

  8. Click Select.
  9. Review the list of selected items. If you want to change them, click Edit Selections.
  10. Click Save Migration File.
    The History tab is displayed and the items are exported to a migration file in JAR format.

    The migration file is saved to the Migration Documents folder in the repository.

  11. Optional: To download the migration file to your local system, click Download.