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. |
|
Driver Configuration File |
|
Select when you want to use the original User Application driver configuration file shipped with Designer.Select when you want to upload a new user application driver configuration file. You might obtain a User Application driver configuration file when performing an upgrade or installing localization or template updates. |
Import |
|
Select this option if you want 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. |
|
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. |
|
Deploy |
|
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 in Section 2.5, Validating Provisioning Objects. Deselect this option to prevent deployment of definitions that fail validation. |
) |
Select this option if you want Designer to prompt you to include runtime configuration objects in the deploy. You should include runtime configuration objects when you are moving a driver set from a test environment to a production environment (or any time you want a complete copy of an existing environment). If you are simply redeploying some updated objects to an existing driver, then you do not need to include the runtime configuration objects at deployment because they already exist. |
|
Localization |
|
Establishes the set of languages that Designer developers are allowed to localize display labels and form control tooltips. The languages specified here are displayed in the localize dialog boxes used in the directory abstraction layer editor and provisioning request definition editor. Click the button to access the dialog box. Once you apply the change, the language is available in Designer. Removing a language from this list does not cause any translated strings for the language to be removed. They are still stored with the object, the language is just not displayed in the localization dialog boxes. |
Workflows |
|
Use this dialog box to remove or preview existing form templates. |
|
Show Activity ID—Select this preference when you want the Workflow 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. |
|
|
|
This is the amount of time (in milliseconds) for Designer to connect to the Identity Vault. If this 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 via the ECMA expression builder. |