One Identity Manager provides an array of form templates and definitions in the default installation. These can be used for easily creating your own forms.
Another way to create custom forms is to make custom form archives available. Normally, default forms in One Identity Manager are replaced with self developed forms.
Table 41: Form templates and definitions for custom extensions
|
FrmCommonChildRelationGrid |
VI_Common_ChildRelation_Grid |
For editing many-to-many relations with extended properties in the form of a table. |
|
FrmCommonOneChild
AndMemberRelation
FrmCommonOneMember AndChildRelation |
A custom form must be created on which the data to be configured is displayed. |
Assigns many-to-many relations and object relations (parent/child relations) on one form. Two tabs for displaying the data are shown on the form. |
|
FrmCommonOneChildRelation |
A custom form must be created on which the data to be configured is displayed. |
Mapping object relations (Parent/ChildRelation).
If several additional object relations are mapped on a form, the FrmCommonTwoChildRelation and FrmCommonThreeChildRelation form templates can be used as alternatives. One tab is shown per object relation. |
|
FrmCommonOneDynamicRelation |
A custom form must be created on which the data to be configured is displayed. |
Displays dynamic many-to-many relations whose assigned object is referenced through a dynamic Permitted dynamic objects are found in the DialogValidDynamicRef table. A menu is provided for choosing the object type. |
|
FrmCommonOneGenericRelation |
A custom form must be created on which the data to be configured is displayed. |
Displaying dynamic many-to-many relations.
-
Base object can be referenced through a dynamic key.
- OR -
-
Assigned object is referenced through a dynamic key. In this case, the MembersTableName property must be defined in the form configuration. |
|
FrmCommonOneMemberRelation |
A custom form must be created on which the data to be configured is displayed. |
Assigning many-to-many relations.
If several additional many-to-many relations are mapped on a form, the FrmCommonTwoMemberRelation, FrmCommonFourMemberRelation, and FrmCommonFiveMemberRelation form templates can be used as alternatives. On tab is shown per many-to-many table. |
|
FrmElementNavigation |
VI_ElementNavigation |
For displaying the overview form. |
|
frmGeneric |
VI_Generic_MasterData |
For editing object main data. |
|
ReportForm |
VI_Report |
For displaying reports. |
|
WizardForm |
VI_Wizard |
For including wizards. The forms are displayed in a modal dialog window. |
Related topics
Forms of the MemberRelation type are used to display the 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.
Example:
An Active Directory user account (ADSAccount table) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer). The Active Directory container (ADSContainer table) is, on the other hand, displayed underneath its Active Directory domain (column UID_ADSDomain). The path for the hierarchy structure is entered as follows:
Table 42: Example of a hierarchy path
|
ADSAccount |
UID_ADSContainer, UID_ADSDomain |
|
ADSContainer |
UID_ADSDomain |
You can specify an alternative list for objects that do not have values in all foreign key columns after a pipe (|).
Example:
(UID_ADSContainer,UID_ADSDomain|UID_ADSDomain)
Related topics
Self developed form templates can be provided for custom forms in a form archive (*CustomForms.*.vif). You need to add the form template, form definition and interface form with help of the Form Editor if you want to display your custom forms in the user interface.
A wizard is available to swap a default form with all its dependencies for a custom form. The wizard creates the interface form with the form definition and the form template. The properties of the new form are taken from the form it is replacing. The necessary assignments (object definition, menu item, permissions group, and application) are created for the new form and the replaced form is disabled.
To replace custom forms with all dependencies
-
In the Designer, select the User interface > Forms > User interface forms category.
-
Select hierarchical representation of the form overview. Set the Options > Tree/list view menu option to do this.
-
At the highest hierarchy level of the form overview, select the form template of the form to be replaced and start the wizard using the Replace by context menu.
-
On the start page of the wizard, click Next.
-
On the Select file and form page, enter the following information.
-
On the Define form structure page, check the names of the form definitions and user interface forms. The names of the form definitions and user interface forms should all begin with CCC. Use F2 to change the names and select Enter to save the change.
-
On the Select permissions group page, select the permissions group to which the new user interface form should be assigned. Use the 
button to create a new permissions group.
-
The last page of the wizard summarizes the settings for replacing a form. To replace the form, click Finish.
The wizard is closed after replacement is complete. The new form is displayed in the Form Editor form overview after the wizard is complete and you can continue editing it. The replaced form is disabled and can therefore no longer available in the user interface.
Related topics
next to the input field to link in a new form definition for the interface form.
button.
button is disabled.
button is disabled.
button is disabled