The following sections explain how exports are upgraded.
Exports that have the output mode of Preview are directly migrated to a Client File target device.
To use database exports, updated database connection information is required to create new External Connections. You can provide connection information for each database export, which facilitate the creation of new External Connections. If you choose to skip this step during the upgrade process, the database parameter information for the export is retained and migrated, but the output mode is set to Client File so that the export is in working order. After the system is up and running, new connections can be created and the exports can be configured to use them.
File locations in systems prior to this release are configured in context of the client. Since the new system is a Web application, exports need to generate files based on the context of the server. For exports with the File output mode, the upgrade process allows you to provide file location information to facilitate new External Connections that map to a UNC path. If you choose to skip this step during the upgrade process, the filename is retained and migrated, but the output mode of the export is set to Client File. After the upgrade process, a proper External Connection can be created, and the export can be configured to use it.
Ancestor exports are converted to Generation exports with appropriate settings to return the equivalent results as in the original Ancestor export.
Export books containing file information are treated much like File Exports. During the upgrade process, you can create external connections to be used for the combined file, Pre file and Post file for the book. If you choose to skip this step during the upgrade process, the book is set to output to a client file.
Systems prior to this release allowed users to save import file locations and log file locations in context of the client application. In this release, file locations are now saved in context of the server using an External Connection, or an import can be saved to be able to choose a local file at runtime. During the upgrade process, you are given the opportunity to supply connection information that is used to create new External Connections. If you choose to skip this step during the upgrade process, the import requires that you choose a local import file at runtime. The log file is no longer saved to a file. The import results are rendered on the page, and if desired, you can download the results.