Once a custom policy type has been deployed, an Active Roles administrator can add a policy of that type to a Policy Object. This is accomplished by selecting the policy type in the wizard that creates a new Policy Object or in the wizard that adds a policy to an existing Policy Object.
Which wizards to use, depends upon the policy type category:
- For a policy type of the Provisioning category, a policy of that type can be added only to a Provisioning Policy Object.
- For a policy type of the Deprovisioning category, a policy of that type can be added only to a Deprovisioning Policy Object.
To configure a policy of a custom policy type
- Follow the steps in the wizard for creating a new Policy Object or in the wizard for adding a policy to an existing Policy Object.
For example, if the policy type is of the Provisioning category, you could use the New Provisioning Policy Object wizard opened by the New | Provisioning Policy command on a container under Configuration/Policies/Administration in the Active Roles console.
- On the Policy to Configure page in the wizard, click the type of the policy you want.
The Policy to Configure page lists the custom policy types together with the pre-defined Active Roles policy types. Each custom policy type is identified by the display name of the respective Policy Type object.
The custom policy types are organized in a tree-like structure that reflects the existing hierarchy of the Policy Type containers. For example, if a Policy Type container is created to hold a particular Policy Type object, the container also appears on the wizard page, so you may need to expand the container to view or select the policy type.
- On the Policy Parameters page, set parameter values for the policy: Click the name of a parameter in the list, and then click Edit.
Parameters control the behavior of the policy. When Active Roles executes the policy, it passes the parameter values to the policy script. The actions performed by the script, and the results of those actions, depend upon the parameter values.
Clicking Edit displays a page where you can add, remove or select a value or values for the selected parameter. For each parameter, the policy script defines the name of the parameter and other characteristics, such as a description, a list of acceptable values, the default value, and whether a value is required. If a list of acceptable values is defined, then you can only select values from that list.
- Follow the wizard pages to complete the wizard.
You can delete a Policy Type object when you no longer need to add policies of the type represented by that object.
Before you delete a Policy Type object, consider the following:
- You can delete a Policy Type object only if no policies of the respective policy type exist in any Policy Object. Examine each Policy Object and remove the policies of that type, if any, from the Policy Object before deleting the Policy Type object.
- Deleting a Policy Type object permanently deletes it from the Active Roles database. If you want to use this policy type again, you should export the Policy Type object to an XML file before deleting the object.
- Deleting a Policy Type object does not delete the Script Module associated with that object. This is because the Script Module may be used by other policies. If the Script Module is no longer needed, it can be deleted separately.
To delete a Policy Type object
- Right-click the Policy Type object in the Active Roles console and click Delete.
Active Roles provides a rich workflow system for directory data management automation and integration. Based on Microsoft’s Windows Workflow Foundation technology, this workflow system enables IT to define, automate, and enforce management rules quickly and easily. Workflows extend the capabilities of Active Roles by delivering a framework that combines versatile management rules such as provisioning and de-provisioning of identity information in the directory, enforcement of policy rules on changes to identity data, routing data changes for approval, email notifications of particular events and conditions, as well as the ability to implement custom actions using script technologies such as Microsoft Windows PowerShell or VBScript.
Suppose you need to provision user accounts based on data from external systems. The data is retrieved and then conveyed to the directory by using feed services that work in conjunction with Active Roles. A workflow can be created to coordinate the operations in account provisioning. For example, different rules can be applied for creating or updating accounts held in different containers.
Workflows may also include approval rules that require certain changes to be authorized by designated persons (approvers). When designing an approval workflow, the administrator specifies which kind of operation causes the workflow to start, and adds approval rules to the workflow. The approval rules determine who is authorized to approve the operation, the required sequence of approvals, and who needs to be notified of approval tasks or decisions.
By delivering email notifications, workflows extend the reach of management process automation throughout the enterprise. Notification activities in a workflow notify people via email about events, conditions, or tasks awaiting their attention. For example, approval rules can notify of change requests pending approval, or separate notification rules can be applied to inform about data changes in the directory. Notification messages include all necessary supporting information, and provide hyperlinks allowing message recipients to take actions using a standard Web browser.
