All form templates are found in the category User Interface | Forms | Form templates in the Designer. It is not usually necessary to define your own form templates.
To display a form template for a user interface form
|Form source type||
Source of the form template. Permitted values are:
|Assembly name||Name of the assembly file.|
|Class||Full type name of the control.|
|Form template name||
The form template name is necessary for loading the form template from the form archive.
|Form archive||Name of the form archive (Forms.*.vif), containing the form template.|
|Description||Detailed description of the form template.|
|Alternative form template||
It might be necessary to use different form templates of display the interface form, for example, to show an the One Identity Manager web interface or in an administration tool.
The form templates can be linked in order to avoid adding a form definition and an interface form for each form template. For this, you need to assign an alternative form template to the form template. This alternative form template is used when the conditions for displaying the original template are not fulfilled. The form template referenced is determined in order to display the interface form. 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. If these conditions are not fulfilled then the alternative form template is tested for suitability. The form template that fulfills the conditions is used for the user interface display.
|Form type||Type of form.|
This property specifies the intended use of the form template. Permitted values are:
|Info (I)||Forms of type "Info" are only used to display information. Changes to data on these forms cannot be saved. These forms automatically omitted by the automatic form selection in quick edit mode.|
|Edit (E)||Edit (E)Forms of type "Edit" are used for editing data. This is the first form to be loaded by the automatic form selection in quick edit mode.|
|Grid (G)||Forms of type "Grid" are used to show data in table form.|
|MemberRelation (M))||Forms of type "MemberRelation" are used to represent data in an assignment list (many-to-many relation).|
|Report (R)||Forms of type "Report" are used to display data in the form of a report.|
Form of type "Virtual" are not shown in the form’s menu. This form type is used to show editors in the Designer.
|Wizard (W)||Forms of type "Wizard" are used to enter data using a wizard. The forms are displayed in a modal dialog window.|
Form definitions are found in the category User Interface | Forms | Form definitions in the Designer. It is not normally necessary to define your own form definitions.
To display a form template for a user interface form
|Form definition name||Name of the form definition. This name is used for displaying the form definition in the Designer.|
|Form template||Name of the form template to load from the form archive. A form template can be used by several form definitions, such as the form templates for displaying membership trees or the form template for displaying reports. Use the button next to the input field to integrate a new form template in the form definition.|
|Base form for form sequence||By entering a form definition as a base for a sequence of forms, you can create a group of form definitions for one object definition. All form sequence form definitions contain the same base form. The definition of the interface form can only be made for this base form. When the interface form is loaded in the display, the referenced form definitions for all other form definitions in the form sequence are also loaded. You can navigate arbitrarily within the form sequence without leaving the scope of the interface form.|
|Description||Detailed description of the form.|
|Configuration||The configuration data is used to describe the form properties. The form property’s definition is written in XML notation.|
A form definition can be assigned additional tables that are used to display data.
Interface forms that need to be valid for all entries in a database table are allocated a general object definition. Other limited object definitions can have more interface forms. If an entry is selected in the user interface, the currently valid object definitions are used to gather all the interface forms and display them in the user interface in their sort order in the task view and in the context menu.
The following object definitions with interface forms are set up for the table Person.
|Object definition||Assigned Interface Form|
|Person_with_ADUserAccount||Active Directory User Accounts|
|Person_with_LDAPAccount||LDAP User Accounts|
The following interface forms are displayed for a "Person" object that fulfills the "Person_with_ADUserAccount" definition:
|Active Directory user accounts|
A "Person" object that satisfies the object definition "Person_with_LDAPUserAccount" is given the interface forms:
|LDAP User Accounts|
Forms of type "MemberRelation" are implemented to display data in an assignment list (many-to-many relations). Enter the hierarchy path in the table definition to display the table hierarchically. Enter the foreign key column that the hierarchy should be based on.
An Active Directory user account (table ADSAccount) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer). The Active Directory container (table ADSContainer) is, on the other hand, displayed underneath its Active Directory domain (column UID_ADSDomain). The path for the hierarchy structure is entered as follows: