You can import an object, a folder, a package, or a content package that was exported. The export process creates the XML file that the import process uses.
Note: If you exported a folder as a content package, the product imports the exported folder as a nonmodifiable content package in the import folder. You cannot cut and delete from a content package. You can copy the automation objects from a content package and paste them to another folder to modify them. You can view all the imported content packages in the Operations tab Content Packages palette.
Follow these steps:
Note: Ensure that the XML file you want to import is no larger than 250 MB.
Note: If you import to an empty folder, there can be no conflicts with existing names.
Processes the imported object as a new version of the existing object. Select this option if the purpose of the import is an upgrade and you want to keep the history of previous versions. If the imported object has the same release version, the product overwrites the existing release version with the release version of the imported object.
Stops the object import and keeps the existing object. The import process lists the objects that have conflicting names. If there are conflicts, import to an empty folder. Alternatively, you can rename the object in the source environment and then repeat the export and import. This option is a good choice when the objects you are importing are new objects instead of new versions of existing objects.
Delete the existing object and import the new version of the object as version 0.
Specifies whether to set the imported version as Current. This option applies if you selected Import and Replace in Step 6.
Note: If you search in a folder hierarchy with a content package, the product returns only objects in the current release version of the content package. The product also returns objects that reside in the folder hierarchy but are not in the content package.
Specifies whether to set the imported custom operators to Available. You cannot use custom operators until they are made available.
Specifies whether to publish the custom operator groups. Publish when importing the object, folder, or package into a different Domain than the one from which the file was exported. Publication publishes the custom operator groups to the Domain-level Modules tab, where every environment also contains the groups that inherit from the Domain.
Note: If you do not have Group_Config_Admin rights, this option is disabled.
|
Copyright © 2014 CA.
All rights reserved.
|
|