Data retrieval using database views
You can use the View query module to create data queries using predefined database views and thus control user access permissions.
Table 152: Data source view properties
|
Name |
Name of the data source. |
|
Description |
Description of data source. |
|
Max. lines |
Maximum number of result lines for this query. If this number is exceeded, the report stops generating. |
|
Parent query |
Not used. |
|
Query module |
Select the View query module. |
|
View name |
Name of the database view. |
|
Condition |
Condition for limiting the data set returned from the database table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the Parameters tab.
Syntax for parameters:
@<Parametername> |
|
Sort order |
The data queries are sorted by these database view columns. |
Related topics
Data retrieval using an object
Data queries with the Object query module are created using the object layer and therefore take user access permissions fully into account.
Table 153: Data source object properties
|
Name |
Name of the data source. |
|
Description |
Description of data source. |
|
Max. lines |
Maximum number of result lines for this query.
NOTE: The report only displays results up to this maximum even if the number of results exceeds it. In the default, no error messages or tips are displayed. Any possible messages must be customized in the report. |
|
Parent query |
In a parent query, restrictions are applied to the data record that are passed on to subsequent queries, all members of a department, for example. Parameters that are defined in the parent query are also available in subsequent queries. |
|
Query module |
Select the Object query module. |
|
Table |
Select the table to find the object in. |
|
Columns |
Columns to use in the report.
Some columns are always added to the report definition and must not be explicitly entered here. These include:
- The table's primary key column.
- All columns used in the table display template.
- Pseudo columns (_Display and _DisplayLong) supplied by the table's display template.
- An additional column (<column>_Display) is also created for the display value for foreign key columns and columns with a list of defined values or multi-language entries.
|
|
Resolve foreign key |
Set this option if the display value of the referenced object should be returned in <column>_Display rather than the UID. |
|
Condition |
Condition for limiting the data set returned from the table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the Parameters tab.
Syntax for parameters:
@<Parametername>
Syntax for columns of a parent query:
@<name of parent query>.<column of the parent query> |
|
Sort order |
The data queries are sorted by these table columns. |
Related topics
Data retrieval using single object history
Use data queries with the Single object history query module when you want to create reports about a single object, for example, one employee, with its history data.
Table 154: Properties of data source single object history
|
Name |
Name of the data source. |
|
Description |
Description of data source. |
|
Max. lines |
Maximum number of result lines for this query.
NOTE: The report only displays results up to this maximum even if the number of results exceeds it. In the default, no error messages or tips are displayed. Any possible messages must be customized in the report. |
|
Parent query |
In a parent query, restrictions are applied to the data record that are passed on to subsequent queries, all members of a department, for example. Parameters that are defined in the parent query are also available in subsequent queries. |
|
Query module |
Select the Single object history query module. |
|
Object key |
The object key can be queried directly or using a parameter. Add these parameters subsequently to the report by entering them on the Parameters tab. Columns in a parent query are formatted with the following syntax:
<parent query name>.<parent query column> |
|
Min date or range |
Use the minimum date to specify the point in time that the history data should start from. You can define the date directly or using a parameter. In the case of a parameter, the minimum date of all affected entries in the connected One Identity Manager History Database databases is determined. Add these parameters subsequently to the report by entering them on the tab Parameters. |
|
Columns |
Columns for which the changes are determined. |
|
Resolve foreign key |
Set this option if the display value of the referenced object should be returned rather than the UID. |
The data query returns the following columns.
Table 155: Columns from a data query using single object history
|
ChangeID |
Unique identifier (UID) for the record. |
|
ObjectKey |
Object key or the record. |
|
ObjectUID |
Unique identifier (UID) for the modified objects. |
|
User |
Name of user that caused the change. |
|
ChangeTime |
Time of change |
|
ChangeType |
Type of change (Insert, Update, Delete) |
|
Columnname |
Name of column whose value has changed. |
|
ColumnDisplay |
Display name of column whose value has changed. |
|
OldValue |
Old column value. |
|
OldValueDisplay |
Old column display value. |
|
NewValue |
New column value. |
|
NewValueDisplay |
New value display value. |
Related topics
Data retrieval using multiple object history
Use data queries with the Multiple object history query module to create reports about multiple objects with historical data that can be further restricted by a particular criterion. This could be all employees with a certain last name.
Table 156: Properties of data source multiple object history
|
Name |
Name of the data source. |
|
Description |
Description of data source. |
|
Max. lines |
Maximum number of result lines for this query.
NOTE: The report only displays results up to this maximum even if the number of results exceeds it. In the default, no error messages or tips are displayed. Any possible messages must be customized in the report. |
|
Parent query |
Not used. |
|
Query module |
Select the Multiple object history query module. |
|
Table |
Select the table to find the object in. |
|
Minimum date or range |
Use the minimum date to specify the point in time that the history data should start from. You can define the date directly or using a parameter. In the case of a parameter, the minimum date of all affected entries in the connected One Identity Manager History Database databases is determined. Add these parameters subsequently to the report by entering them on the Parameters tab. |
|
Columns |
Columns for which the changes are determined. |
|
Criteria |
Column, table, and value used for further narrowing down the objects found. The value can be queried directly or as a parameter. Add these parameters subsequently to the report by entering them on the tab Parameters. |
The data query returns the following columns.
Table 157: Columns from a data query using single object history
|
ChangeID |
Unique identifier (UID) for the record. |
|
ObjectKey |
Object key or the record. |
|
ObjectUID |
Unique identifier (UID) for the modified objects. |
|
User |
Name of user that caused the change. |
|
ChangeTime |
Time of change |
|
ChangeType |
Type of change (Insert, Update, Delete) |
|
Columnname |
Name of column whose value has changed. |
|
ColumnDisplay |
Display name of column whose value has changed. |
|
OldValue |
Old column value. |
|
OldValueDisplay |
Old column display value. |
|
NewValue |
New column value. |
|
NewValueDisplay |
New value display value. |
Example:
A history of all employees with the last name "Name1" should be created. The report data can be defined in the following way:
|
Table: |
Person |
|
Min. date: |
MinDate |
|
Criteria: column |
Lastname |
|
Criteria: value |
Name1 |
Related topics
