Replace existing files
Files that currently exist in the target directory are automatically
overwritten.
Export page
The Export page provides default settings options for exporting ENVY components or
files to a TeamConnectiondatabase.
Storage in TeamConnection
The Component field identifies the TeamConnectiontarget component for your
export action. This component designation, along with TeamConnectionfamily,
release, and work area values supplied in the Context page of the Default
Properties notebook, is necessary to define the context for any new
TeamConnectionparts created by an export action.
Configuration Maps
If the Export all required maps too checkbox is checked, it specifies that
when a configuration map is exported, its required configuration maps (along
with any other required configuration maps, recursively) should be exported
TeamConnection.If this option is enabled, and a configuration map being
exported does have required maps, the maps can only be exported if they
actually exist in the TeamConnectiondatabase.
This option is used to prevent version mismatches when a configuration map
requires other configuration maps, as in the following case:
1. For a configuration map that requires other configuration maps, you do an
export

with

the required maps.
2. At some later time, you export again

without

the required maps.
3. When you attempt to import

with

the required maps, the import may fail,
because a configuration map level in TeamConnectiondoes not match the
level previously exported from ENVY.
Note: The checkbox is checked as the default.
Exporting ENVY components to TeamConnection
The TeamConnectionBridge cascade menu provides an Export choice, which offers
the following choices:
vConfiguration Maps
vApplications
vFiles
Note: Youmust have the appropriate authority to update all parts associated with the
configuration maps, applications, or files to be exported.
As a general rule, it is advisable to export applications and configuration maps along
with any configuration maps required by these ENVY components to avoid version
258 User’s Guide