About protecting objects on export
- Last UpdatedDec 04, 2024
- 2 minute read
Protecting an object on export does not change the object in the galaxy from which it was exported. Protection is effective only on import of protected objects. Specific behavior is described as follows:
|
Element or Function |
Description |
|---|---|
|
Base Templates |
Are protected by default and cannot be checked out, edited or renamed. |
|
Protected templates and graphics |
Cannot be checked out, edited, or renamed, but can be deleted. A template derived from a protected template is unprotected. Protected templates and graphics are marked with a lock icon. |
|
Ancestor objects |
Are protected in the exported .aaPKG file when a child object is protected. |
|
Protection effective |
Protection is effective on import of protected objects. A protected object retains its protected status even when exported using the standard Export Object(s) workflow. |
|
Instances |
Cannot be protected. Only templates and graphics can be protected. |
|
Select both template and instance for export |
The option to export objects as protected is disabled. Only templates and graphics can be protected. |
|
Export workflow |
The export workflow is the same as for all objects except that you can select the option to export As Protected Object(s). |
|
Graphics |
Graphics and client controls directly or indirectly embedded in a protected graphic are also protected. Protected graphics can be opened in the Graphic Editor as read-only. |
Protected objects are marked in the Template folder, Visualization folder, or Application views (Model, Deployment, or Derivation View) with a shield icon to the right of the object name..
