Database views with the table type "proxy" are unions of different table views. The column definition is used to map the columns between a "Proxy" type view and the underlying table. The DBQueue Processor calculates the actual view definition from the column mapping. This only takes into account tables that are not disabled by a preprocessor condition. Templates and formatting rules cannot be defined for columns in these views.
Views of type "Proxy" are primarily used for displaying the Unified Namespace. For example, the proxy view UNSRoot is used in the Unified Namespace to map the table ADSDomain or LDAPDomain.
The following information is displayed for a database view of type "Proxy".
|Table||Name of the table in the data model.|
|Type||Table type "Proxy".|
|Additional view definition||
Database query generated as a SELECT statement for setting up the database view. View definition extensions are generated by the DBQueue Processor. The following are taken into account when generating:
The extensions are linked with each other with the Union operator.
|Condition for view definition||Limiting condition as WHERE clause for setting up the database view.|
|Columns||Database view columns.|
The following mappings are required to map ADSDomain in Unified Namespace to the database view USRoot.
For example, the column Ident_Domain in the table ADSDomain is mapped to the column Ident_root of the proxy view UNSRoot.
For example, the view UNSRoot expects a target system type in the column UID_DPRNameSpace. This column is not in the tables ADSDomain. Thus 'ADS-DPRNameSpace-ADS' as UID_DPRNameSpace is entered as an extension to the proxy view in the table ADSDomain.
The DBQueue Processor generates the extended view definition from the data. The following statement is a excerpt from the generated extension.
select ... Ident_Domain as Ident_UNSRoot..., 'ADS-DPRNameSpace-ADS' as UID_DPRNameSpace from ADSDomain
Views with the table type "read only" can be parts but also unions of the underlying tables. Views with type "read only" are predefined. Templates and formatting rules cannot be defined for columns in these views.
Database views of type "read only" are mainly used to edit the user interface and for creating reports.
The following information is displayed for a database view of type "Read-only".
|Table||Name of the table in the data model.|
|Type||Table type "Read-only".|
|Additional view definition||
Database query as a SELECT statement for setting up the database view.
Several extensions for the view definition can be defined. The extensions are linked with each other with the Union operator.
When you add a column, an entry is created in the table DialogColumn. When you delete a column, the entry is removed from the table DialogColumn.
|Condition for view definition||Limiting condition as WHERE clause for setting up the database view. The condition is attached to the view definition generated from the extension.|
|Columns||Database view columns.|
|NOTE: The default configuration is moved to a configuration buffer during handling. You can retrieve changes from the configuration buffer and restore the default configuration in this way.|
To edit column properties
NOTE: Select a table column in the Designer, then you can start the Schema Editor from the task Show column definition.
|Table||Name of the table to which the column belongs.|
Name of the table in the data model.
Language dependent column name for displaying in the administration tool’s user interface. Translate the given text using the button.
|Comment||Additional information about the column. The remarks are shown in the help function for each administration tool. Translate the given text using the button.|
|Disabled by preprocessor||
If a column is disabled by a preprocessor condition, the option is set by the Database Compiler.
You can add preprocessor conditions to columns. The column is therefore only available when the preprocessor condition is fulfilled.
The sort order specifies the position for displaying the column on the generic form and the custom tabs of the default form. Columns with a value less than one are not displayed.
|Group||Group is used to display the column on general master data forms. A new tab is created for each group on the generic form.|
If the table is of type "view" then the link to the base table is given here.
Example: The database view Department is a sunset of the base table Basetree. The columns of the table Basetree are entered as base columns.
|Adjustment of permitted values list is not allowed||Specifies whether permitted values can be customized for this column.|
|Defined list of values||Marks whether the value in this column must correspond to the values in the List of permitted values, or are empty.|
|List of permitted values||If a column is principally enabled for permitted values editing, that means the option Customizing permitted list not allowed is not set. If the option Defined list of value is set, then you can add to or extend a value list.|
|Defined bitmask||Meaning of each bit position if the column contains a bitmask. The first bit in the definition start with the index 0.|
Specifies whether this column can be given in multiple languages. Permitted values are:
The combination of values determines the resulting translation.
Syntax of Data in this column. The syntax type is used to give the One Identity Manager tools the appropriate syntax highlighting or input assistance. Permitted syntax types are:
|Number of decimal places||This contains the number of decimal places used for displaying real and integer values. A value can be given to three decimal places, for example. Prices are given to two decimal places by default.|
Additional information about displaying dates and times in the user interface.
Column weighting in indexing. This is used for the full text search index in the Web Portal. Increasing weighting results in a higher position in the search results.
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. Columns to be index are given the weighting "1" in the default installation.
Table Lookup Support
Each value in these columns are prepared for fast table lookup support. The search is also supported by single values in MVP columns. The internal mapping of prepared data in done in the table QBMSplittedLookup.
Permitted values are:
You can extend the list of permitted values and customize the results.
The functionality can be used for finding a unique central user account, for example, or a unique default email address for an employee. Columns in the default installation, which are taken into account when mapping the central user account or an email address, are labeled with this property. The results are displayed in the views, QERCentralAccount and QERMailAddress.
|Data type in database||
Shows the .Net data type for the column. This is used internally and cannot be edited. The Net data types are mapped internally to SQL data types. If no value is given, the data type is taken from the database schema. Permitted syntax types are:
|Size in database||Length of the column in the database|
|Primary key||The primary key is given when the database is created.|
|UID column||Specifies whether this is UID column. This option is only permitted for columns with the .Net data type "String" and length 38.|
|Default value||Specifies whether a default value is defined for this column in the database schema.|
|BLOB value||This option is used to label text columns whose data contents is so large that they cannot be kept internally in one line in the SQL sever and are therefore saved as a reference. This allows speedier access to the data.|
|Log changes||Specifies whether changes to this column are logged.|
|Log changes when deleting||Specifies whether the column is logged when an object is deleted.|
|Export for SPML schema||This option determines whether the table should be exported for the SPML schema.|
|Not for export (XML export)||This column is not exported in data transports. The property is taken into account when data is transported between database.|
|Not for import (XML import)||This column is not imported in data transports. The property is taken into account when data is transported between database.|
|MVP column||This is a MultiValuedProperty (MVP) whose individual values are separated by char(7) or chr(7).|
Specifies whether the column contents can consist of more than one line. Columns that are labeled with this option are displayed on a common form with multiline input fields.
|Dynamic foreign key||
Dynamic foreign keys reference object keys in another tables. The object key is made up of the table name and the value of the primary key of the actual object. Permitted tables can be limited. All tables are permitted, if there are no restrictions.
|Column contains description||One column with a description can be labeled with this option per table. The description is only displayed on user interface assignment controls.|
|Column contains hierarchy information||
One column, which maps hierarchy information in readable form can be labeled with this option per table. The column is used for mapping the hierarchy to the mapping control elements in the user interface.
|Part of primary key||This column is part of the primary key|
|Part of alternative primary key||Alternative primary keys are already specified in the default version, but the definition can be customized. Alternative primary keys are used for data transport amongst other things.|
|Part of the key of a many-to-many table (dynamic)||
Labels the foreign key of an many-to-many table (dynamic). A (dynamic) many-to-many table's foreign key and dynamic key are identified with this option.
|Display in Filter Designer||The column is displayed in the Filter Designer or the Rule Editor for creating requests.|
|Recursive key||This option specifies whether this column has a link to a parent object. This input is needed for displaying hierarchical tables. For example, the table ADSContainer contains a column UID_ParentADSContainer with a link to the parent Active Directory container. The column UID_ParentADSContainer is labeled with this option in order to display this hierarchical link on forms.|
This option is used to specify whether the value in this column should be encrypted or not. When the database is encrypted the value in this column is encrypted.
|Permissions not issued automatically||Permissions for predefined permissions groups are not issued automatically for custom schema extension on a predefined table, even if the configuration parameter "Common\AutoExtendPermissions" is set.|
|Proxy view column||If the column is used in a "Proxy" type view, the corresponding column in the view is entered here. For example, the column ADSDomain.DisplayName is mapped in the UNSRoot view to column RootObjectDisplay.|
|Remarks (custom)||Spare text box for additional explanation.|
|Max. length||Maximum length of the column. If the value is "0" the length is taken from the database schema.|
|Foreign key||The column references an object in another table.|
|Min. length||Minimum length of the column. The minimum length must be at least 1 or more for mandatory columns in the administration tools.|
|Column format||Specify the format permitted for value in this column. You can control the permitted format for the column with formatting types and formatting scripts.|
|Overwrites||Specifies whether the template can overwrite or not.|
Defines a value template for this column using other columns or a default value for the column. Write the script in VB.Net syntax which allows all VB.Net script functions to be used.
Limit for the number of objects changed by this template. Once this limit has been reached, processing is aborted with an error message.
|Threshold (asynchronous)||Limit for the number of objects changed by this template. Once this limit has been reached, processing takes place synchronously with the One Identity Manager Service.|
|No automatic truncation by template||If the maximum length exceeded when applying a template, the value is not automatically truncated to the maximum column length if the option is set.|
|Formatting script||Formatting script for the column. Write the script in VB.Net syntax which allows all VB.Net script functions to be used.|
|Custom template/formatting not permitted||Specifies whether the default configuration can be changed by the user, for example, display name, templates and formatting rules.|
|Average column length||Information is determined once a day through the maintenance tasks. The data material can help to plan capacities and maintenance work on the database.|
|Template changed||(Only for internal use) indicates that the template was changed.|
|No DB Transport||Columns labeled with this option cannot be excluded from a custom configuration package. These columns are excluded from data transport.|
Specifies whether the column content is recorded in logs, for example, in the One Identity Manager Service log.