Identity Manager 8.1 - Configuration Guide

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.

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

• Column properties

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.

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

Related Topics

• Creating formatting scripts
• Column properties

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.

Related Topics

• Predefined formatting types
• Using scripts
• Column properties

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

• Table properties
• Templates for generating values