You can only define bitmasks for columns with theint type.
NOTE: You can only enter or extend a bitmask for a column if the option Customizing bitmasks is not allowed is not set.
To create a bitmask
-
In the Designer, select One Identity Manager Schema.
-
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 settings tab and set the Defined bitmask option.
-
Under Sort criteria of bitmask, select the sort criteria for displaying the value.
You have the following options:
-
Click 
and enter the following properties.
-
Select the Database > Commit to database and click Save.
Related topics
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 full text search can be used in the Manager and in the Web Portal. For more information, see the One Identity Manager Web Designer 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 full text search result. 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 identity being listed before the user account in the full text search.
NOTE: Weighting does not have any effect on how the results are sorted in the user interface. For example, if you limit the search in the Web Portal to the 100 best matches, weighting determines which 100 objects are returned. But these 100 objects are then sorted again by the user interface.
-
Only columns with the .Net data types String, Text, or Int can be included in the full-text search.
Exception: Columns that contain a list of permitted values, can always be included to the full text search.
-
Columns of tables with the Work tables or Historical transaction data usage type 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:
-
Column content
-
Foreign key column display value
-
Display values for lists of permitted values
-
Translation for every active language
-
Object display value, if the table's primary key column is configured for full text search
The object's display value comes from the display pattern defined for the table. The display value's weighting comes from the table's primary key column weighting
Example:
The Person.UID_Person column is configured for full-text search. The display pattern of the Person table is defined as %InternalName% (%CentralAccount%).
So the display value of Alex Miller (AlexM) is indexed for the identity Alex Miller.
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.
-
Select the Database > Commit to database and click Save.
Related topics
In principle, a user's permissions for displaying and editing columns are controlled by permissions in permissions groups.
However, you can also use scripts to conditionally display or edit scripts. For example, in this way you can control whether or not a column, on a main data form in the Manager, is displayed or can be edited only if another column has a specific value.
Example:
A system role is disabled until the release data is reached. During this time period, the user must be prevented from changing the disabled option in the Manager.
To do this, a script is created specifying the edit permissions for the ESet.IsInActive column.
If $ReleaseDate:Date$>Connection.LocalNow Then
Else
End If
NOTE:
-
The script does not change the user’s permissions but simply the behavior if the object is loaded in one of the tools. If you want to limit visibility and editability of a column, change the column permissions of the permissions groups. For more information, see the One Identity Manager Authorization and Authentication Guide.
-
The scripts only affect interactively loaded objects.
-
For example, in lists in the Manager or in the Web Portal, objects are not loaded interactively so the scripts do not work.
-
In the Web Portal, a lot of objects are not loaded interactively due to performance reasons. If you want to use this behavior in the Web Portal, you must customize the components in the Web Designer. In this case, there can be adverse effects on performance when objects are loaded. For more information about editing Web Designer components, see the One Identity Manager Web Designer Reference Guide.
To specify a script for conditionally displaying and editing a column
-
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 Permissions scripts and enter the following scripts in VB.Net syntax.
-
Visibility script: Script for conditionally displaying the column. If the return value is false, the column is not displayed in any tools.
-
Editability script: Script for conditionally editing the column. If the return value is false, the column cannot be edited in any tools.
-
Select the Database > Commit to database and click Save.
Related topics
To edit column properties
-
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 in the Schema Editor and edit the column properties.
-
Select the Database > Commit to database and click Save.
Related topics
. To delete a value, select the value and click
. To delete all values, click
.