# Driver Editor

The following figure illustrates the driver editor. This editor provides a graphical interface so that you can manage Identity Manager Driver objects, policy sets, and policies.

In this section:

- Accessing the Driver Editor
- Using the Driver Editor
- Policy Manager Overview

## Accessing the Driver Editor

You can access the driver editor from either the Outline view or from the Enterprise Editor.

### From the Outline View

1. Select Window > Show View > Outline.

2. In the Outline view, right-click a driver, then select Show Driver Policy Sets.

### From the Enterprise Editor

1. Open the Project View.

2. Right-click a project, select Open With, then click Enterprise Modeler.
3. Right-click a Driver object (not the application), then select Show Driver Policy Sets.

You can also click the Policy Flow icon on the Outline view toolbar.

[Return to Top]

## Using the Policy Editor

The Policy Editor consists of three main areas:

- Policy Flow
- Policy management
- Policy overview

### Policy Flow

The Policy Flow area enables you to view and manage the Drivers Class/Attribute filter as well as policies contained in the various policy sets. When you select a policy set (for example, a Publisher matching policy set), the Policy Set Manager displays the policies contained in that set, and the Policy Builder displays the rules in a selected policy.

The policy flow image also displays the flow of documents through the system. For example, an input document generated by the application follows the Publisher path identified by the green arrow beginning with the Input Policy Set and moving toward the Identity Vault. Result documents generated by the Identity Manager engine for the input document continue to follow the green arrow flowing back to the connected system through the Schema Mapping and Output Policy Sets.

Input documents generated on the Subscriber channel behave similarly by following the orange arrow beginning at the Identity Vault and flowing to the connected application. Result documents generated by the application and Identity Manager driver continue to follow the orange arrow back through the Input and Schema Mapping Policy Sets to the Identity Vault.

Only Add operations flow through the Matching, Creation, and Placement Policy Sets on both the Subscriber and Publisher channels. All other operations follow the dotted line, bypassing these policy sets to the Command policy set.

Policy Flow Key

The Policy Flow Key describes aspects of the policy flow image, such as empty or filled Policy Sets, as well as the path that documents take on the Publisher and Subscriber channels. Documents on the Subscriber channel begin at the Identity Vault, while documents on the Publisher channel begin at the connected application.

Keyboard Support

Keystroke | Description
--- | ---
Up Arrow | Navigate Up
Down Arrow | Navigate Down
Tab | Navigate Down
Shift + Tab | Navigate Up
Left Arrow | Switch Channels
Right Arrow | Switch Channels

[Return to Top]

### Policy Set Manager

The Policy Set Manager contains a tool bar and a list of policies.

The policy list displays all the policies contained in the selected policy set. During a transformation, the policies within the list are executed from top to bottom. The toolbar contains buttons and a drop-down menu that you can use to manage policies displayed in the list. Management of policies includes editing, adding, deleting, renaming, and changing the processing order of the policies.

When you select a policy in the list, the following occurs:

- A read-only copy of the policy is displayed in the Policy Builder area.
- Buttons located on the tool bar or in the tool bar drop-down menu are enabled or disabled.

Policy Manager Toolbar

Operation | Description
--- | ---
Edit a Policy | Launches the appropriate policy editor.
Add a Policy | Launches the Add Policy wizard.
Delete a Policy | Deletes the policy from the project.
Remove a Policy | Removes the policy from the selected Policy Set but doesn't delete the policy.
Move Up | Moves the policy up in the processing order.
Move Down | Moves the policy down in the processing order.

Keyboard Support

Keystroke | Description
--- | ---
Up Arrow | Moves the selected policy up in the processing order.
Down Arrow | Moves the selected policy down in the processing order.
Delete | Deletes the policy from the project.
Minus | Removes the policy from the selected policy set.
Plus | Launches the Add Policy Wizard.
Ctrl + Z | Undoes the last operation.
Ctrl + Y | Redoes the last operation.

### Policy Builder

The Policy Builder displays a read-only version of the selected policy.

To access the Policy Builder and make changes to a policy:

1. Select a policy in the Policy in the Policy Set Manager
2. Select the edit icon from the Policy Set Manager tool bar.
   This opens the policy in the appropriate editor.

[Return to Top]

## Policy Manager Overview

To access the Policy Manager Overview, click a Notify filter in the driver editor.

### Policy Flow Key

The Policy Flow Key describes the following:

- Components in the policy flow process
- The path that documents take on the Publisher and Subscriber channels

### Add Policy Wizard

The Add Policy Wizard enables you to do the following:

- Create a policy
- Copy an existing policy
- Link an existing policy into a policy set

To launch the Add Policy wizard:

1. Select a driver in the Outline view.
2. Select a Set item in the Policy Set Manager, then click the Add icon on the toolbar.

Create a Policy

1. In the Add Policy Wizard, select Create a New Policy, then click Next.

2. Provide a policy name.

3. Accept the default container, or browse to and select the Driver, Publisher, or Subscriber object where you want the policy to be created.
   This decision depends on how you want to organize the policies. By default, policies are placed under the container object that is selected in the Outline view when the Add Policy Wizard is launched.
   For example if you move to a Publisher object in the Outline view and then add a policy to a policy set, the policy defaults to the Publisher container.

   You would change this setting if you want to create policies in a different container. For example, you can set up a policy library under a dummy driver, put all of the common policies under this driver, and then simply reference the policies from the other drivers. That way, the policy is common. If you need to change a policy, you have to do it only once.

   If a policy is not reused by multiple drivers, you typically create that policy under the driver or channel that is using it.

4. Select how to implement the policy.
   If you click Finish, the policy type defaults to Policy Script.
   To select XSLT or Schema Mapping, click Next, select the policy type, then click Finish.

- Policy Script
- XSLT
- Schema Mapping
  The schema mapping option is available only if the Schema Mapping policy set is selected.

The new policy appears in the expanded Set item.

You can also add a policy by right-clicking a Set item in the Policy Set Manager.

1. Right-click a Set item (for example, Input Set).
2. Select Add Policy.
3. Select how to implement the policy.
4. Name the policy.
5. Select to open the Policy Builder editor immediately after adding the policy.
6. Click OK.

[Add Policy Wizard]

Copy a Policy

1. In the Add Policy Wizard, select Copy a Policy, then click Next.

2. Name the policy.

3. Accept the default container, or browse to and select the Driver, Publisher, or Subscriber object where you want the policy to be created.

4. Launch the Model browser again to select the policy to copy.
5. Browse to and select the policy you want to copy, then click OK.
6. Click Finish to make a copy of the selected policy.

[Add Policy Wizard]

Link to a Policy

1. In the Add Policy Wizard, select Link in a Policy, then click Next.

2. Launch the Modeler browser by selecting the Browse button ( ).

   Note: Linking a policy into a policy set is not permitted when Viewing All Policies.

3. Browse to and select the Policy object you want to link into the policy set, then click OK.

Linking a policy into a policy set doesn't create a new Policy object. Instead, it adds a reference to an existing policy. This reference can be to any existing policy within the current Identity Vault. It doesn't have to be contained within the current Driver object, but the policy type must be valid for the policy set that it is being linked to. For example, you can't link a Schema Mapping Policy into an Input Policy Set.

4. Click Finish to link to the selected policy.

[Return to Top]