Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Forms for the user interface

User interface forms are used to display and edit data in the user interface. The basic information for representing data on the user interface forms is described in form definitions and form templates. The form definition referenced by the interface form needs to be found. The form template given in the form definition is checked for existence in the form archive and to see if it labeled for the correct display purposes.

Detailed information about this topic

Recommendations for editing forms

  • If necessary, you can disable individual predefined forms to prevent them being shown in the user interface. They remain disabled even after schema installation.
  • The default installation of One Identity Manager already provides a series of form templates and definitions, for example for editing master data as well as many-to-many relations and object relations (Parent/ChildRelation). These can be used for easily creating your own forms.
  • To display information about a base object, you create an overview form.
    • You can do this using the Overview Form Editor in Designer.
    • Create menu items for object relations you need to display frequently, and use these menu items as reference in the form elements of the overview form.

      TIP: You can have the Overview Form Editor create the menu items for object relations.

      • Select the object relation you want to display and drag and drop it on an element in the element area of the Overview Form Editor.
      • Use the context menu items Create list element reference or Create reference to data element.

      The menu items are entered below the menu item InfoSheets.QIM.Links with the labels InfoSheet.List.<table> and InfoSheet.Node.<table>, respectively.

      The condition for the menu items is defined as the variable %<table>WhereClause%. In the form element you assign a condition as WHERE clause to the variable.

  • Default forms can be used to customize column extensions on default tables under certain conditions.
  • To edit the master data of custom tables, use the Form Editor of the Designer to create an interface form with the form definition VI_Generic_MasterData.
  • To define mappings, create additional interface forms with the form type MemberRelation.
  • Assign the forms and menu items to the Manager application.
  • Assign the forms and menu items to the permissions groups for non role-based and role-based login.
  • If necessary, you can provide your own form templates in a form archive (*.Forms.vif).

Related Topics

Editing user interface forms

User interface forms are connected to object definitions, so that different forms are offered in the user interface depending on which object is selected. These interface forms are made available to system users, taking into account their permissions group memberships, by the additional assignment of interface form to permissions groups. Further more, interface forms can be defined for separate menu items. When the associated menu item is selected in the navigation or the item is selected in the result list, the interface forms are shown for all system users without taking their permissions group memberships into account.

Predefined configurations are maintained by the schema installation and cannot be edited apart from a few properties.

NOTE: You can disable individual predefined tasks to prevent them being shown in the user interface. They remain disabled even after schema installation.

Related Topics

Notes on working with the Form Editor

Use the Form Editor to create and edit the interface forms, such as the master data forms or assignment forms. All user interface forms are displayed in the form overview.

  • Forms that are disabled by preprocessor conditions are grayed out in the form overview.
  • Use F5 to refresh the form overview in the Form Editor.
  • Forms can be displayed hierarchically or in a list. The interface forms are grouped by form template and form definition in the hierarchical representation. To change the display, select Options | Tree/List view.
  • Using the Options | Show captions menu, you can switch between the forms’ technical names and the user-friendly captions.
  • To display additional columns in the form overview, use the Options | Select columns menu.
  • Define filters to restrict the number of forms displayed in the form list. Select the menu items Define filter or Manage filters for this purpose. For detailed information about working with user-defined filters in Designersee One Identity Manager User Guide for One Identity Manager Tools User Interface.
  • Use the form preview while editing master data forms. Select the View | Form preview menu item to display an additional Form preview tab in the Form Editor.

    The form preview shows the contents of the interface form. You can see which base tables will be used to display the data. The permissions of the logged in Designer user are taken into account when loading and displaying an interface form.

    If a form cannot be loaded, an appropriate error message is displayed.

Related Documents