Properties can be derived from other properties within an object. This lets computed and composite values be created in the object. Such derived properties are named virtual properties. The value of a virtual property can be calculated in two ways:
Using a script called by the
onRetrievescript hook. This script then calculates the current value of the virtual property based on the related properties.
queryConfigto identify the relationship fields to traverse to reach the managed objects whose state is included in the virtual property, and the fields in these managed objects to include in the value of the virtual property.
Virtual Properties Using
onRetrieve script hook lets you run a script when the object is retrieved. In the case of virtual properties, this script gets the data from related properties and uses it to calculate a value for the virtual property. For more information about running scripts on managed objects, see "Run Scripts on Managed Objects".
Prior to IDM version 7.0, using
onRetrieve scripts was the primary method for calculating virtual properties. This method will continue to work, but is not as performant as using
queryConfig. There may be some cases involving custom logic where a scripted solution is still the preferred answer. For more information about customizing scripts for role calculation, see Grant a Role By Using Custom Scripts.
Virtual Properties Using
Virtual properties can be calculated by IDM based on relationships and relationship notifications. This means that rather than calculating the current state when retrieved, the managed object containing the virtual property is notified of changes in a related object, and the virtual property recalculated when this notification is received. To configure virtual properties to use relationship notifications, there are two areas that need to be configured:
The related managed objects need to be configured to use relationship notifications. This lets IDM know where to send notifications of changes in related objects. For more information, see "Configure Relationship Change Notification".
In order to calculate the value of the virtual property, you need configure what relationships to check, and in what order, when it receives a notification of a change in a related object. This is done using the
queryConfig property tells IDM the sequence of relationship fields it should traverse in order to calculate (or recalculate) a virtual property, and what fields it should return from that related object. This is done using two fields:
referencedRelationshipFieldsis an array listing a sequence of relationship fields connecting the current object with the related objects you want to calculate the value of the virtual property from. The first field in the array is a relationship field belonging to the same managed object as the virtual property, the second field is a relationship in the managed object referenced by the first field, and so on.
For example, the
["roles","assignments"]. The first field refers to the
rolesrelationship field in
managed/user, which references the
managed/roleobject. It then refers to the
managed/role, which references the
managed/assignmentobject. Changes to either related object (
managed/assignment) will cause the virtual property value to be recalculated, due to the
notifyRelationshipsconfigurations on managed user, role, and assignment. These configurations ensure that any changes in the relationships between a user and their roles, or their roles, and their assignments, as well as any relevant changes to the roles or assignments themselves, such as the modification of temporal constraints on roles, or attributes on assignments, will be propagated to connected users, so their
effectiveAssignmentscan be recalculated and potentially synced.
referencedObjectFieldsis an array of object fields that should be returned as part of the virtual property. If this property is not included, the returned properties will be a reference for the related object. To return the entire related object, use
queryConfig, the virtual property is recalculated when it receives a notice that changes occurred in the related objects. This can be significantly more efficient than recalculating whenever an object is retrieved, while still ensuring the state of the virtual property is correct.
When making changes to what object fields to return using
referencedObjectFields, the changes will not be reflected until there is a change in the related object that would trigger the virtual property to be recalculated (as specified by the notify, notifySelf, and notifyRelationships configurations). The calculated state of the virtual property is still correct, but since a change is necessary for the state to be updated, the returned fields will still be based on the previous configuration.