33.1 Understanding File Formats and Import Flows

Previous versions of Identity Governance supported the export and import of data related to various functional areas in CSV, JSON, XML, or ZIP format. The current release provides an enhanced export and import capability including export and import of data as a ZIP file containing a single SQLite database file. If you need to open the SQLite database file, you will need to use a database browser application.

If necessary, you can edit the exported files, then import them. However, we recommend that if you need to make any changes to the data, you make the changes using the user interface options, then export. If you choose to edit the files manually, proceed with caution. When you import manually edited files, Identity Governance will not import the file if the edits are not done correctly or if the file is not in the expected format.

When you import data, you either directly import a file (basic import flow) or use an enhanced import flow that enables you to upload, then preview and search imported data. In the enhanced import flow, by default Identity Governance automatically refreshes the imported data when the import process detects a change in the system that affects the loaded import file. For example, during technical role import, if Identity Governance detects any change in the system because of an application publication that leads to changes in permissions, or if any technical role is modified, added, or deleted, then Identity Governance automatically refreshes the imported data. If you want to disable the automatic refresh behavior, change the default value of the com.netiq.iac.importExport.refreshPrompt property using the Advanced Global Configuration menu.

Though the enhanced export and import capability supports compressed SQLite file as the export format, you can continue to import CSV, JSON, or ZIP files exported from previous versions of Identity Governance.