CentraSite 10.5 | CentraSite User’s Guide | Policy Management | Managing Design Time Policies through CentraSite Business UI | Viewing or Modifying a Design Time Policy
 
Viewing or Modifying a Design Time Policy
Pre-requisites:
To examine and modify the properties of a design time policy in CentraSite, you must have one of the following permissions:
*To examine and modify the properties of a organization-specific policy, you must have the Manage Design 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 examine and modify the properties of that policy unless you have permission to manage design time policies for organization ABC.
*To examine and modify the properties of a system-wide policy, you must have the Manage System-Wide Design Time Policies permission.
Important:
If you belong to a role that includes the Manage System-Wide Design Time Policies permission, you have the ability to modify CentraSite's predefined policies. However, you should not do this. These policies perform critical functions within the registry and must not be modified except under the direction of a technical representative from Software AG.
You cannot modify a policy while it is in the Productive state. To make changes to a policy, you can do any of the following:
*Create a new version of the policy, make the necessary changes to the new version and switch the new version to the Productive state when you are ready to put it into effect. Switching the new version to the Productive state will immediately put the previous version in the Retired state. (The Retired state is an end state. After you place a policy in this state, you can no longer reactivate it.)
*Create a completely new policy that includes the required changes. When you are ready to put the new policy into effect, deactivate the old policy and activate the new policy.
*Deactivate the existing policy and make the necessary changes to the policy and then activate it. While the policy is in the Deactivated state, it will not be enforced. This is because deactivating the policy results in an enforcement gap; however, you would not use this approach in a production environment.
*To examine and modify details of a design time policy
1. In the CentraSite Business UI activity bar, click Design Time.
2. To view the Design Time policies:
a. Go to the advanced search panel.
b. In the Narrow Your Results section, perform the following actions:
a. Locate Applicable Scopes. By default, Policy is selected. Additionally, you can also refine your search further by selecting the following options:
*Show only Productive Policies
*Include Predefined Policies
b. Add a Keyword and click the plus button next to the field to add it to the Current Search Criteria recipe.
c. You can also further refine your search by selecting values for the following from their respective drop-down list and clicking the plus sign next to these fields to add them to the search criteria:
Note:
The moment you click the plus sign, the result is refreshed in the Search Results page.
*Applicable Organizations
*Applicable Types
*Applicable Event Types
d. This displays a list of defined Design Time policies in the Search Results page.
3. Click the policy whose details you want to examine and modify.
This opens the Design Time Policy Details page.
4. If the policy is active, deactivate it by clicking from the menu.
You cannot modify the details of an active policy.
5. On the Design Time Policy Details page, examine and modify the attributes as required.
Field
Description
Name
The name of the policy. A policy name can contain any character (including spaces). A policy name does not have to be unique within the registry. However, to reduce ambiguity, you should avoid giving the same name to multiple policies. As a best practice, we recommend that organizations adopt appropriate naming conventions to ensure the assignment of distinct policy names.
Description
(Optional). Additional comments or descriptive information about the policy.
Version
The user-assigned version ID assigned to this policy. You can use any versioning scheme for identifying different versions of a policy. The identifier does not have to be numeric. Examples:
0.0a
1.0.0 (beta)
Pre-release 001
V1-2007.04.30
CentraSite also maintains a system-assigned version identifier for a policy. The system-assigned version identifier is independent from the version identifier that you specify in this field.
Priority
An integer that represents the priority of this policy with respect to other policies that might be triggered by the same event.
*Priority values 0 through 10 and values greater than 9999 are reserved for predefined policies. You cannot assign these values to the user-defined policies that you create in CentraSite Business UI.
*The default priority for a user-defined policy is 11.
Scope
The settings on this profile specify the Applicable Types and Event Types that are applicable to the policy.
States
The settings on this profile specify the lifecycles and state changes to which this policy applies.
Note:
The States profile is present only if the scope of the policy includes a Pre-State Change or Post-State Change event.
Policy Actions
The settings on this profile, specify the actions that CentraSite executes when the policy is enforced.
6. Click Save.
Note:
If the selected asset and event types are not compatible with the current set of actions in the action list, CentraSite does not permit you to save the policy. You must correct the policy's action list or its scope to save the policy successfully.
7. When you are ready to put the policy into effect, activate the policy.