Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Defining decimal places for displaying values

For columns with the data types Double, Decimal, Int, Long or Short, you can define the number of decimal places for displaying values in the user interface.

In columns with the data types Int, Long or Short, the decimal point is shifted in the value display when the decimal places are specified. In columns with the data types Double or Decimal, the value is displayed with the corresponding number of places after the decimal point. Take this behavior into account when calculating with different data types.

Example
  • Prices (Int data type) are entered with two places after the decimal point. In the front-end a price of €3.50 is displayed as 3.50 and saved in the database as 350.
  • Quantities (Double data type) are specified for example with three places after the decimal point. In the front-end, a quantity of 100 pieces is displayed with the value 100,000, while the value 100 is saved in the database.

To define the number of decimal places

  1. In the One Identity Manager, select Designer Schema.
  2. Select the table and start the Schema Editor with Show table definition.
  3. Select the column and then the Column properties view.
  4. Select the Column tab and enter the number of decimal places to be used in the Number of decimal places input field.
Related Topics

Predefined formatting types

You can specify column formats based on predefined formatting types. By combining formatting types with each other, you can obtain the formatting you required.

Note: If there is a column or column combination for a table that needs to be unique, you define multi-column uniqueness in Designer. For more information, see Defining unique columns.

To specify formatting types

  1. In Designer, select One Identity Manager schema.
  2. Select the table and start the Schema Editor with the task Show table definition.
  3. Select the column and then the Column properties view.
  4. Select the Value calculation tab and define the formatting types in the Column format input field.
    Table 28: Permitted formatting types
    Value Formatting type Permitted values
    0 None No special formatting = default
    1 IP address IP address [0-9]³.[0-9]³. [0-9]³.[0-9]³
    2 MAC-ID MACID [0-9,A-F]12
    4 Drive letter Drive letter [A-Z]1:
    8 Number [0-9]+
    16 Uppercase Uppercase
    32 Uppercase server dependent (only maintained for compatibility reasons)
    64 NT name All characters are permitted except for „!@/\:,“[];|=+*?<>“
    128 Phone Phone [0123456789#/-+*]n
    256 Exchange name All characters are permitted except for „ÄÖÜäöüß“!§$%&\|/<>#*{}[] ²³~^,“
    512 ASCII characters and numbers All characters from the 7-bit ASCII character set

    2048

    URI

    Uniform Resource Identifier

    4096

    Email address

    Valid email address

IMPORTANT: Compile the database to implement the formatting type.

Related Topics

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

  1. In the One Identity Manager, select Designer Schema.
  2. Select the table and start the Schema Editor with the task Show table definition.
  3. Select the column and then the Column properties view.
  4. 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.

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 column ADSAccount.Mail 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 administration 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:

  1. Customizer

    The dependencies between columns and an object are stored in customizers.

  2. Custom defined dependencies

    To define custom dependencies between columns

    1. In the Schema Editor, select a table column.
    2. In the Column properties view on the Dependencies tab, define the predecessor of this column.
  3. 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
Related Documents