Previous versions of Designer did not populate a driver's Engine Control Values until the driver was
deployed. This was necessary because the Identity Manager engine version defines what engine controls are available
for a driver. Versioning in Designer now allows ECVs to
populate when a driver is created, based on the Identity Manager version of the server that is associated with the driver set.
For example, the following image shows the ECVs that are created when a driver is dropped onto the Modeler view
and there is a v3.5 server associated with the driver set.
Changing a version of an Identity Manager server affects the engine controls for all drivers in the driver set that
are associated to the server. With this version of Designer, when the Identity Manager version changes, the engine
controls for all associated drivers are updated to match the version. During the update process, all
current settings for existing engine controls are merged into the new engine controls. Using the previous example,
the engine control Subscriber channel retry interval in seconds is set to 60 seconds in the 3.5
engine version. The following image shows the new engine controls after the Identity Manager server version is changed to 2.0.
While the value of the Subscriber channel retry interval entry remains at 60 seconds, the
engine controls for Use non-compliant backwards-compatible mode for XSLT and the Qualified form for rename
events entries are not valid 2.0 engine controls and are removed.
The Test Authentication button on the Identity Vault properties page has been changed in this release of
Designer to allow users to refresh the connection to the Identity Vault. If a connection has not been established
to the Identity Vault, the button shows Test connection; once a connection is created, the button shows Refresh connection.
Selecting this button allows the user to create or, when a connection becomes unresponsive, to re-create
a connection to the Identity Vault.
Designer lets you connect to a server/host system by specifying the hostname/alias name.
This feature eliminates the need to remember the ip address
of the host system. This is supported throughout all of Designer.
In the previous Designer release, setting the driver trace level live did not restart the driver after
the update. In this release, the driver gets restarted once the trace level is updated.
The Set Driver Trace Level Live page also allows you to specify if you want the setting to be simultaneously set in the local Designer
model as well.
This milestone provides check boxes to select the drivers and added Select All and Deselect All buttons to check and uncheck
all the drivers respectively.
Previously, if you wanted to use a GCV in a policy and couldn't remember the name of the value, you would have to go into the XML view to
figure it out. Now, the GCV Information page displays the GCV name, as well as the display name and description.
You can now directly browse eDirectory/NDS application objects. The properties of these application
objects allow you to configure the required connectivity information and credentials.