Defining decimal places for displaying values
In the user interface, you can define the number of decimal places for displaying values of columns with the .Net data types Double, Decimal, Int, Long or Short.
In columns with the .Net 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 .Net 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 with the .Net data type Int are given with cent 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 with the .Net data type double are, for example, specified 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
-
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 enter the number of decimal places to be used in the Number of decimal places input field.
-
Select the Database > Commit to database and click Save.
Related topics
Using 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
-
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 define the formatting types in the Column format input field.
Table 26: Permitted formatting types
|
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 of the ASCII character set |
|
2048 |
URI |
Uniform Resource Identifier |
|
4096 |
Email address |
Valid email address |
|
8192 |
Prevent XSS characters |
Certain characters that can be used for cross-site scripting (XSS) are invalid. The < and > characters are tested.
Testing only takes place if the QBM | XssCheck configuration parameter is set. If the QBM | XssCheck | Sync configuration parameter is set, testing is also done during synchronization. |
-
Select the Database > Commit to database and click Save.
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 run 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.
-
Select the Database > Commit to database and click Save.
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 web service interfaces, the correct order for setting values also has to be ensured.
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 stopped at the point of lowest priority.
Related topics
