Here you select the export file (created with the Export function
of the Design Explorer view) or the file produced
by the Pacbase batch
migration procedures. You specify the location and projects into which
the instances contained in this file are to be imported.
- File extension
- Select the file extension. The default extension is xmi,
which corresponds to the extension of a file exported with the Export function
of the Design Explorer view.
The ta2 extension,
which is the other possible extension, corresponds to a file produced
by the Pacbase batch
migration procedures.
- From file
- Click Browse to locate the export file
or the file produced by the Pacbase batch procedures.
- Into location
- Click the downward arrow to display the locations which exist
in the Design Explorer view. Select one of them.
You
can also enter a location which does not exist; it will be created
by the import.
- Options
- Here you indicate the projects (the physical organizations) into
which the instances contained in the file are to be imported. You
have two options:
- Import into a default structure of projects:
This structure reflects the structure of the Pacbase database in Libraries.
If you select this option, each Library corresponds to a specific
project, named after the Library. You keep the benefits of the Pacbase Library-related
inheritance principle. For example, a Program stored in an AAA project
(coming from the AAA Library), can then call
a Data Element as it is stored in the BBB project
or in the CCC project.
- Import into a project: All the instances
are imported into the same project, which you must select. You must
be aware that this option deprives you of the benefits of the Pacbase Library-related
inheritance principle.