10. Provisioning View: What's New

(Home)     Previous     Next


1. Export and Import of Localization Strings for the User Application

The Provisioning view now gives users the ability to export and import localization strings for a User Application. By selecting the User Application or any of its children in the Provisioning view, users enable the right-mouse menu options to Localize > Export Localization Data and Localize > Import Localization Files.

The Export Localization Data option allows users to extract all display label strings from the selected User Application object and its children and store them as unique key and value items in an XML or .properties file. A separate file is created for each of the locales they want to support. These files can easily be sent off to a translation service that can then fill the display label value fields with the translated strings for those locales.

The Import Localization Files option allows users to import the display label values provided by their translation service into the User Application objects. Users have the option to back up their existing display labels in the User Application before it is overwritten with any new labels. This allows users to revert their changes if any of the new display labels are not to their satisfaction.

2. Supported Locales for User Application Configuration

In Identity Manager 3.5, the supported locales for the User Application are stored in the User Application driver. Thus it is longer be possible to edit the supported locales in the Preferences pages in Designer.

Furthermore, because Identity Manager 3.0.1 doesn't support self-localization of the User Application, a read-only list of locales is used for 3.0.1 User Application drivers.

3. Support for IDM 3.0.1 and IDM 3.5 User Application Drivers

The Provisioning view, the Provisioning Request Definition editor, and the Directory Abstraction Layer editor now all support both Identity Manager 3.0.1 and Identity Manager 3.5 User Application configurations.

The Identity Manager 3.5 User Application driver configuration file is available only if the associated server is using Identity Manager version 3.5.

4. Migration of Identity Manager 3 or 3.0.1 User Application Configuration to Identity Manager 3.5

The Provisioning view makes it possible to migrate a User Application configuration from Identity Manager 3 or 3.0.1 to Identity Manager 3.5. The migration handles the Directory Abstraction Layer and Provisioning Request Definitions as well as the runtime configuration objects. The runtime configuration objects are objects used by the User Application (and stored in the Identity Vault) but not editable through Designer. This include objects such as themes and cache configuration.

If the User Application configuration can be migrated, the Provisioning view's right-mouse menu contains a Migrate item when activated on a User Application. After the migration, the following dialog box appears:


The dialog box shows all the migrated objects, along with any errors, warnings or messages that occurred during the migration. It's possible to undo the migration (for example, if errors occurred). Furthermore, you can specify whether the migrated configuration should be deployed. Note that it's not possible to deploy parts of a migrated configuration. Only the entire configuration can be deployed. Similarly, it's not possible to import into a migrated configuration.

You can save a summary of the migrated User Application configuration by clicking the save icon in the top left corner.

5. Deployment to pre-Identity Manager 3.5 Identity Vault Prevented (Identity Manager 3.5 Only)

When deploying an Identity Manager 3.5 User Application driver, configuration or objects, the Provisioning view first checks parts of the schema in the Identity Vault to ensure that the schema has been updated with the changes required for Identity Manager 3.5. It is not possible to deploy an Identity Manager 3.5 User Application configuration to an Identity Manager 3.0.1 Identity Vault or to any vault that doesn't contain the required schema changes.

6. Support for Directory Abstraction Layer Queries (Identity Manager 3.5 Only)

The Provisioning view now displays Directory Abstraction Layer Queries if the User Application driver has Identity Manager 3.5.


Other Enhancements & Bug Fixes
  1. Cleanup right mouse menu in Provisioning view - Click here for details...
  2. Export to File does not retain directory location of last export - Click here for details...
  3. Should be possible to see the version information for a UAD in the PV - Click here for details...
  4. When creating new User Application, the provisioning email notification templates should be added to the notification template collection - Click here for details...
  5. Would be nice to have an icon next to items to denote undeployed, modified but not deployed objects - Click here for details...
  6. Would be nice if the Provisioning View showed that an object had validation errors and warnings - Click here for details...


(Home)     Previous     Next