Working with a database based collection includes adding properties or object as well as removing and delete objects from a collection or database.
All important procedures for managing database-based collections are described below:
To add a proxy property to a database based collection
Proxy properties allow transparent use of database columns (base property) with modified metadata. Metadata includes:
You can modify a property within a component to match the requirements of the component exactly using proxy properties. Ensure the database of a proxy property is always the base property value. Updating the value through proxy properties always have additional effects on the base property.
A proxy property is added under the selected collection node.
To add more proxy properties to a database based collection
|
NOTE: Each object, which is in the collection at runtime, now has an additional property. You can handle this like a database based property, for example, to store temporary data. |
To add a new object to a collection
This could be the Initializer node of the component, for example.
|
NOTE: Ensure the object is only added in the collection. |
To modify a property in a database-based collection
In the steps below, the display value in the Entry date column in the White pages view is modified from <dd.MM.yy> to <yyyy-MM-dd> as an example.
|
NOTE: The steps for this function can be used for the Child relation column and Foreign key relation column functions. For more information about these functions, see the One Identity Manager Web Designer Object Model Documentation. |
In our example, we presume that the <dd.MM.yy> display value is set.
The display in the definition tree view switches to Configuration (custom).
In our example, the following expression could be used.
FormatDate(EntryDate, "yyyy-MM-dd")
In the Entry date column, the display value is yyyy-MM-dd.
To remove objects from the collection or delete them from the database
This could be the Initializer node of the component, for example.
To save objects in the database
This could be the Initializer node of the component, for example.
Data is linked in a database by relations to each other. You can use these relations to load data from the database in the simplest way.
Prerequisite for using such a collection is a collection containing source data.
There are different type of relations for defining a collection:
A foreign key relation helps automatically load those objects in a database view that were referenced by objects from another collection through a foreign key relation.
A child relation helps automatically load those objects in a database view that reference objects from another collection through a child relation.
To define a collection with a foreign key relation
You do not have to trigger loading for this type of collection. The moment the data is available in the source data collection, the foreign key referenced objects are automatically loaded.
To define a collection with a child relation
You do not have to trigger loading for this type of collection. The moment the data is available in the source data collection, the referenced objects are automatically loaded.
For different use cases, it is necessary to examine database objects from multiple tables together. The special collection type Database objects from multiple tables in the object model is available for this.
To define a collection with the option "Database objects from multiple tables"
A collection like this is database based, but can accept objects from multiple database tables.
For more information, see "Database Objects" as a collection. You must explicitly provide the database table from which the objects will be loaded.
|
NOTE: You can use the database query wizard in a module or component of a collection or when you want to add a new module or component. |
You cannot execute SQL expressions directly in Web Designer for security reasons. Instead, this wizard helps you create SQL expressions which are stored in the QBMLimitedSQL table and linked to at least one permissions group in the QBMGroupHasLimitedSQL table. Your own collection node is added for the query.
To create a database query
|
NOTE: The navigation depends on whether you have selected a custom module/component or a default module/component. Default database objects first require an object extension. For more information, see Extensions. |
The Wizard for creating or selecting a database query page is displayed for an SQL expression to be entered or selected.
This displays following input and text fields are displayed.
Setting | Description |
---|---|
Collection name | If necessary, overwrite the standard name for the collection that you are adding with this query. |
Identifier | In this input field, enter a unique identifier that is used later to identify the entry. |
SQL expression | Enter the complete expression in this text field. You can also declare parameters. |
Description | Enter a description of this entry here. This makes it easier for other users to understand and classify this expression. |
Specify the dialog groups that can execute the SQL snippet in the Wizard for creating or selecting a database query page. All dialog groups are selected.
|
NOTE: You can check your database query with Test statement. As soon as the database processes running in the background are complete, you can test the new expressions. |
This display the Processing page and generates the new collection and SQL expression.
To select a database query
|
NOTE: The navigation depends on whether you have selected a custom module/component or a default module/component. Default database objects first require an object extension. For more information, see Extensions. |
The Wizard for creating or selecting a database query page is displayed for an SQL expression to be entered or selected.
This displays the following input and text fields.
Setting | Description |
---|---|
Collection name | If necessary, overwrite the standard name for the collection that you are adding with this query. |
SQL snippet | Select an existing snippet in the options box that you can then use and edit in the SQL expression field. |
SQL expression | If necessary, extend the selected snippet and preset parameters in the text field. |
Specify the dialog groups that can execute the SQL snippet in the following Wizard for creating or selecting a database query page.
|
NOTE: Dialog groups already in a standard module collection cannot be deselected. |
|
NOTE: You can check your database query with Test statement. As soon as the database processes running in the background are complete, you can test the new expressions. |
This display the Processing page and generates the new collection and SQL expression.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy