Exporting Design/Change-Time Policies
Pre-requisites:
To export a design/change-time policy in CentraSite, you must have one of the following permissions:
To export a organization-specific policy, you must have the Manage Design/Change-Time Policies permission for the organization specified in the scope of the original policy. For example, if the original policy is scoped for organization ABC, you are not permitted to export that policy unless you have permission to manage design/change-time policies for organization ABC.
To export a system-wide policy, you must have the Manage System-Wide Design/Change-Time Policies permission.
When exporting a design/change-time policy, keep the following points in mind:
You can export a policy that is active or inactive. You do not need to deactivate a policy to export it.
The export process does not export the following objects that a policy references:
Lifecycle State
Organization
The export process does not export the policy's instance-level permissions. When an administrator imports the policy on the target instance, the import process assigns instance-level permissions.
If the policy includes a custom action,
CentraSite exports the action template for the custom action along with the action's metadata.
If the policy's object scope includes a custom asset type,
CentraSite exports that type along with the policy.
If the policy scope is
Assets, then the type information is exported. So any basic attributes referenced in the policies have to be edited in the target registry (for example, if the policy has assertions such as Set Attribute value or Validate Attribute value). There is one exception, namely if the policy uses classification attributes in the policy assertions; in this case, the type information is included in the export.
The export process exports the parameter values assigned to the actions in the policy. If the parameter value is a reference to an instance of one of the following object types, you must export the referenced object and import it on the target instance of
CentraSite before you import the policy:
Organization
User
Group
If referenced User/Group objects do not already exist on the target instance of CentraSite when you import the policy, the import removes the references to these objects and the import is successful. After the import, you can edit the policy to reference the necessary user/group objects. If a parameter references any other type of object, the export process exports the referenced object with the policy and that object is imported as necessary into the target registry.
If the policy executes on a PreStateChange or PostStateChange event, the lifecycle model and state information on the policy's
States tab is exported. If the specified lifecycle model and states do not exist in the target instance of
CentraSite when the policy is imported, the import process fails (that is, the policy is not imported).
To export a design/change-time policy
1. In CentraSite Control, go to Policies > Design/Change-Time.
2. Locate the policy that you want to export and select Export from its context menu.
3. Specify the options in the Export dialog box and click OK.
4. Save the archive file when prompted to do so.
5. Examine the export log that is displayed by CentraSite Control and check for any errors that occurred during the export process.
