Import protected objects

Objects with same Tagname and Codebase as an existing object:

• Skip: Do not import

• Overwrite objects if the imported configuration version is higher (default)

• Overwrite objects regardless of configuration version

Overwrite preferences are governed by the Template Protection Change Management option, "Never overwrite an unprotected object with a protected object" (default).

• Overwrites can occur if both the packaged and galaxy objects have the same protection status.

• A protected object can overwrite an unprotected object only if specifically permitted by clearing the "Never overwrite ..." option.

• When overwriting a protected parent object, protection is not cascaded to child objects. Unprotected child objects remain unprotected.

Base Templates with newer or older Codebases (or minor version updates):

• Skip: Do not migrate

• Migrate

Import and migration of base templates is unchanged by protected object import functionality.

Objects with same Tagname but with a different Codebase:

• Skip: Do not import

• Rename object in Galaxy

• Rename importing object

Object renaming on import can occur only if the object to be renamed is not protected.

• If the object in the Galaxy is protected, and the importing object is not, and Rename importing object is selected, the importing object is renamed to have the suffix "_new".

• If the object in the Galaxy is unprotected, and the importing object is protected, and Rename object in Galaxy is selected, and the Never overwrite an unprotected object with a protected object option is not selected, the object in the Galaxy is renamed with the suffix "_old".