You can customize some Provisioning view behaviors by setting preferences. You access the preferences page through
. The preferences include:Table 2-2 Provisioning View Preferences
Preference Category |
Setting |
Description |
---|---|---|
General |
|
When this is selected and you delete a User Application from the Modeler, Designer asks whether you want to delete the provisioning objects on disk as part of the delete operation. If you do not delete the provisioning objects, they are left on disk, even though the User Application is deleted. |
|
When you delete an object in the Provisioning view or the directory abstraction layer editor, you are prompted to confirm the deletion. This preference determines whether the check box labeled in the confirmation dialog box is selected by default.Selecting this preference means that the check box is selected and the default is to delete the Identity Vault object. The local object is always deleted. |
|
|
Select this option if you want Designer to launch the Provisioning view when you create a new User Application driver or import an existing one. |
|
|
Select this option if you want Designer to validate display names to ensure:
Applies to display names defined by using the directory abstraction layer editor, provisioning request editor, or provisioning teams editor. |
|
|
Select this option so Designer displays provisioning request definitions organized by category. You specify the category in the Overview panel. Categories are defined in the Provisioning Category list defined in the directory abstraction layer. |
|
|
Select this option so Designer displays all localized e-mail templates as selectable options in the tab. The Java language code is appended to the name of the e-mail template. For example, cn=Provisioning Notification Activity_es, cn=Default Notification Collection,cn=security indicates this is the Spanish language version of this template.When you select a localized template, that language is used regardless of the user’s default language. When you select the default template (the template without a locale code), the e-mail is in the user’s default language (if the default is a supported language). |
|
|
The amount of time (in milliseconds) for Designer to connect to the Identity Vault. If it is set too low, you might encounter an error when trying to set Trustee Rights on a provisioning request definition or when trying to access the Identity Vault through the ECMA expression builder. |
|
Import/Deploy |
Import |
: Select this option for Designer to delete local objects if the corresponding Identity Vault objects were deleted. This ensures that the Identity Vault and local files are in sync. Deselect this option if you want to leave the local files alone. |
Import |
: Select this option if you are importing the driver from a test environment and want to deploy to a production environment. The User Application driver runtime relies on objects stored in the driver that you are not able to access in Designer. If you deploy a driver that does not contain these objects, it does not work properly. Deselect this option if you are importing the driver, modifying it, and deploying it back to the same driver set because the driver already has the runtime configuration objects. |
|
Import/Deploy |
Deploy |
Section 2.6, Validating Provisioning Objects. Deselect this option to prevent deployment of definitions that fail validation. : Select this option if you want to deploy objects that fail validation checks. At deployment, Designer validates the definitions being deployed following the validation rules outlined inWARNING:Deploying objects that fail validation can result in errors in the User Application runtime. |
Migration |
|
When you select the command, Designer displays a dialog box that warns you that schema changes (that are needed to support new features) must be made before you can deploy the migrated driver. If the updates have not been made, you should cancel the migration until they are complete. If you don't want to see this warning when you select the command, deselect this option. |
|
This preference is only relevant for User Application drivers that haven't been deployed to the directory (for example, User Application drivers that have been imported from a driver configuration file). When a User Application driver that has not been deployed is migrated, an additional dialog box is displayed that prompts you to deploy the driver. Select the option if you always want Designer to deploy the User Application driver, and you don’t want this dialog box displayed. |
|
|
When you select the command, Designer displays a dialog box that warns you that all editors will be closed. Select this option if you don’t want this warning displayed each time you choose the command. |
|
Validation Mask |
|
Use this dialog to define the validation masks available to form controls such as the Text control. The validation masks are regular expressions and must follow regular expression syntax. Designer provides a default set of validation masks. If they do not show up as validation masks in the form controls property sheets, you can enable them by clicking , then clicking . |
Workflows |
|
Use this dialog box to remove or preview existing form templates. |
|
: Select this preference when you want the tab of the provisioning request definition editor to display the Activity IDs for each activity in the flow. Activity IDs are used by the ECMA expression builder and are written to the User Application’s error logs. : Select this preference when you want the tab of the provisioning request definition editor to display the Flow Path Types for each activity in the flow. Flow Path Types are used by the ECMA expression builder and are written to the User Application’s error logs. |