Business Logic Task Handler API Summary

Operations

Task-Level Validation

Called by

CA IdentityMinder

When called

Depending on what methods are implemented, the custom handler can be called at the following points during task execution:

When a task session is created (to initialize or process task data)
After selecting a subject from the search result, but before presenting data to a user
Before submitting the task to the BLTH adapter.
After a user submits a task, but before any security checks
After security checks are done, but before the asynchronous phase

Operates on

CA IdentityMinder objects associated with any task screen in the CA IdentityMinder environment. Performed by global handlers. (Java implementations only.)
CA IdentityMinder objects associated with the particular task screen where the handler is specified. Performed by task-specific handlers. (Java or JavaScript implementations.)

Object update

Updates happen in the following ways:

In the task session, through the get... methods in BLTHContext. Because CA IdentityMinder generates events for these updates before writing the data to the data store, the updates can be subject to workflow approval processes, auditing, and security checks.
Directly in the data store, through the provider objects. No events are generated for these updates, so any workflow approval, auditing, and security checks are bypassed.

Can validate?

User input on a task screen against task screen field values, information in CA IdentityMinder objects, and information in third-party data sources.

Note: You can also perform attribute validation using JavaScript and regular expressions. For more information, see the Configuration Guide.