Request creation and submission methods
There are numerous ways that a request can be generated.
Automated request generation via auto-discovery
When auto discovery runs, Bravura Identity identifies changes (adds/deletes/changes) are identified. Components that provide idtrack
functionality can process those changes then submit the appropriate workflow requests. For example, when a new record in a Source of Records (SoR) target is identified, idtrack
implementing component logic will execute, automatically populate and send a request to onboard a user.
You can identify components that implement idtrack
functionality by searching for the string <provides>IDTRACK</provides>
in the manifest.xml
files in the components directory.
Some configurations for idtrack
can be found in the hid_global_configuration policy extdb table. These entries will be identifiable as they will contain namespace=AUTOMATION
.
Automated request generation via automatic assignment
The automatic assignment process utilizes user class membership to automatically assign/unassign roles or groups to a profile.
Automated request generation via role enforcement
The role enforcement process utilizes role membership to submit requests to automatically assign/unassign roles or groups to a role.
Automated request generation via Attribute Propagation
When a user's profile attribute is updated, Bravura Identity can be configured to automatically propagate the updated profile attribute value to its mapped account attributes.
Manual request via wizard in Bravura Identity user interface
From the user interface, when a user clicks a request link such as My Profile > View and update profile > Request a group membership it opens the pre-defined request wizard. Each page of the wizard is a form that facilitates the input of the necessary request attributes. When the user clicks the Submit button, the request is generated and populated with the specified request attributes.
Custom Scripts
Requests can also be created from custom scripts. Some API calls that can be used to submit requests are:
WFPDRSubmit API call
A simpler API for submitting requests. Less granular than WFRequest*.
May be called remotely via SOAP to create/submit a request from a specified PDR.
May also be called locally via custom script directly from the Identity application node.
WFRequest* API calls
WFRequestCreate / WFRequestAttrsSet / WFRequestSubmit / etc.
May also be called via SOAP or locally on application node.
Can provide more control over the process of creating and submitting a request in comparison to WFPDRSubmit.