Creating formatting scripts
You can use a formatting script to verify column values. Formatting scripts, as opposed to value templates, are only executed when a value is assigned to the column.
To create a formatting script
-
In the Designer, select the One Identity Manager Schema category.
-
Select the table and start the Schema Editor with the Show table definition task.
-
Select the column and then the Column properties view.
-
Select the Value calculation tab and enter the formatting script for the column in the Formatting script input field.
Write the script in VB.Net syntax which allows all VB.Net script functions to be used.
IMPORTANT: Compile the database to bring the formatting script into effect.
TIP: Test compile using the Schema | Test compile menu item.
Example
The value in the column Mail in the ADSAccount table should correspond to SMPT format. If this is not the case, an error message is sent. The formatting script for the ADSAccount.Mail column can be formulated as follows:
Dim str as String = Convert.ToString(Value)
If str.Length > 0 Then
If Not VID_IsSMTPAddress(str) Then
Throw New Exception("""" & str & """ is not a valid SMTP address.")
End If
End If
Related topics
Column dependencies for setting values
There may be dependencies between individual values, for example, by using value templates or customizers that require values to be set in a specific order. In the case of One Identity Manager tools the correct order is enforced through blocking or releasing input fields. In the case of data import and when using SPML and web service interfaces, the correct order for setting values also has to be safeguarded.
The following data sources assume the following sequence for specifying the order for setting values:
-
Customizer
The dependencies between columns and an object are stored in customizers.
-
Custom defined dependencies
To define custom dependencies between columns
-
In the Schema Editor, select a table column.
-
In the Column properties view on the Dependencies tab, define the predecessor of this column.
-
Column dependencies due to value templates
In this case, values used by a template (for example, Person.Firstname, Person.Lastname) are set before values that are created by a template (for example, Person.CentralAccount).
If circular dependencies occur whilst determining the order for setting the values, they are aborted at the point of lowest priority.
Related topics
Permitted values for a column
To permit only certain values for a column, you must define a list with the permitted values. Once the column display name has been created, the list of permitted values is no longer valid. For some columns of the One Identity Manager schema, already permitted values are supplied when the schema is installed.
NOTE: You can only enter or extend a list of permitted values for a column if the option Customizing permitted values list is not allowed is not set.
To create a list of permitted values
- In the Designer, select the One Identity Manager Schema category.
- Select the table and start the Schema Editor with the Show table definition task.
- Select the column and then the Column properties view.
- Select the Column tab and enable the Defined list of values option.
- Click the [...] button next to the List of permitted values input field to open the input dialog.
-
Click 
and enter the value and display name.
NOTE: To edit a value, select the value and click 
. To delete a value, select the value and click 
.
- (Optional) Use
or 
to specify the display order.
- (Optional) Translate the given text using the
button.
- Click Save.
IMPORTANT: Compile the database to bring the list of permitted values into effect.
Example
In the Spare field no. 01 input field for an employee, the values internal and external should be permitted. The list of permitted values is defined as followed:
1=internal 2=external
For an employee with the value 1, the display value internal is shown on the forms in the Manager.
Display columns with permitted values in the Manager
A special control element is used in the Manager to display columns for which a list of permitted values has been defined. The control element is displayed as a simple input field if no list is defined. If a list is defined the control element is shown as a menu.
Figure 10: Input field for list of defined values (with and without defined entries)
The control element is only available for columns on default predefined forms as well as custom columns (usually CustomProperty01-CustomProperty10).
Related topics
Configuring columns for full-text search
Full-text searching uses an external search index, which returns an object key as result. The object key is used to run a search query in the database. This database search query takes the permissions of the logged in user into account during the search. A maximum of 1000 objects can be returned by through the search index.
The One Identity Manager full text search can be used in the Web Portal and in the Manager. For more information, see the One Identity Manager Web Portal User Guide and the One Identity Manager User Guide for One Identity Manager Tools User Interface.
-
Prerequisites for using full text search is an application server installed with the search service.
-
If you run the Web Portal directly over an application server installed with the search service, you can use the full text search immediately.
-
If you are working with the Web Portal and an application server without a search service installed or with a direct database connection, you will need to enter an application server with a search service in the Web Portal configuration file. Full text search is available in the Web Portal once this has been done.
-
To use full text search in the Manager, you must run the Manager over an application server with an installed search service.
For more information about installing an application server and configuring the Web Portal for full-text search, see the One Identity Manager Installation Guide.
The following applies for the configuration of the full text search:
-
The columns XDateInserted, XDateUpdated, and XObjectKey must be available if you want to index a table or database view for full text search.
- Columns for full text searching must be weighted. Increasing weighting results in a higher position in the search results. The default installation provides columns for the full-text search with a weighting of 1.
Example
The column Person.CentralAccount is weighted with the value 1. The column ADSAccount.SAMAccountName is weighted with the value 0.5. This results in the employee being listed before the user account in the full text search.
-
Only columns with the .Net data types string or text can be included in the full-text search.
Exception: Columns that contain a list of permitted values, can always be added to the full text search.
- Columns from tables with the usage type Work tables or Historical transaction data cannot be included in the full-text search.
-
Columns of assignment tables (M:N tables, M:all tables) cannot be included to the full-text search.
The search service indexes the following:
The searched index is updated when changes are made to a table with indexed columns, to referenced tables or translations.
Certain important columns are already indexed for full text search in the default installation. You configure more columns for full text searching if you require.
To configure a column for full text search
- In the Designer, select the One Identity Manager Schema category.
- Select the table and start the Schema Editor with the Show table definition task.
- Select the column and then the Column properties view.
- Select the Column tab and edit the Index weighting property.
- If the value is less than or equal to 0, no indexing takes place.
- If the value is greater than 0, the data value is indexed.
Related topics
