Importing Design/Change-Time Policies
Pre-requisites:
To import a design/change-time policy in CentraSite, you must have one of the following permissions:
To import 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 import that policy unless you have permission to manage design/change-time policies for organization ABC. If the archive contains a system-wide policy or custom action templates, you must also belong to a role that has the Manage System-Wide Design/Change-Time Policies permission.
To import a system-wide policy, you must have the Manage System-Wide Design/Change-Time Policies permission.
When importing a design-time policy, keep the following points in mind:
If the policy, or any related object in the archive already exists in the target instance of
CentraSite, the existing object is overwritten.
When the imported policy
is added to the registry, the import process assigns the Organization, Lifecycle State, and Activation State properties to the imported policy as follows.
Property | Value assigned to new policy |
Organization | The organization of the user that is performing the import, unless the policy is a system-wide policy. If the policy is system-wide, the policy's Organization attribute will remain set to All. |
Lifecycle State | The initial state for new policies. Note: If you are using the lifecycle model for policies that is installed with CentraSite, the imported policy's state is set to New. |
Activation State | Inactive |
Additionally, CentraSite assigns instance-level permissions to the imported policy just as though you created the policy manually. (In other words, the imported policy receives the same permission settings as the policies you create from scratch.)
When an imported policy
replaces (updates) an existing policy in the target registry, all of the policy's properties, except for its permission settings, are updated according to the policy object in the archive. This includes the policy's organizational scope, its lifecycle state, and its activation state (that is, whether the policy is active or inactive). If the referenced organization and lifecycle model does not already exist on the target registry, the import process fails. Also, be aware that the import process replaces the policy on the target regardless of whether the target policy is currently active or inactive. Due to this behavior, you might want to import only new versions of a policy, and not use the import process to directly replace a version of a policy that already exists.
If the archive file contains a reference to an object that is not already present in the target registry or is not included in the archive file itself, the policy will not be imported.
If design/change-time policies exist for the events that the import process initiates (for example, the creation of a policy), those policies is triggered.
To import a design/change-time policy
1. In CentraSite Control, go to Policies > Design/Change-Time.
2. Click the Import icon.
3. Click Browse and select the zip file containing the policy that you want to import.
4. To automatically replace the policy if it already exists, select Allow replace of existing objects.
5. Click OK.
6. When the import process is complete, check the import log to make sure that the policy and its associated objects were imported successfully.
7. If the import process was successful, open the policy in CentraSite Control and do the following:
a. Inspect the parameter settings for each action in the policy to ensure that they are set properly. Specify appropriate values as necessary.
b. Inspect the other properties assigned to the policy and ensure that they are set appropriately.
c. Activate the policy.