Previous Topic: Sample Business Logic Task HandlersNext Topic: Example: Calling a Business Logic Task Handler


Calling Sequence

CA IdentityMinder calls business logic task handlers after all logical attribute handler processing is complete, so that business logic task handlers have access to the logical attribute values and the physical attribute values set by the logical attribute handlers.

Business logic task handlers are invoked in the following order:

  1. A CA IdentityMinder admin task is submitted on a task screen.
  2. CA IdentityMinder creates a BLTHContext object for the task, and passes this object to each business logic task handler it invokes.
  3. If any task-specific handlers are defined for the task, CA IdentityMinder invokes the first handler referenced on the task screen.
  4. After all task-specific handlers are executed, CA IdentityMinder invokes any global task handlers defined in the Management Console for the environment, beginning with the first handler defined on the Business Logic Task Handlers screen.

If a business logic task handler throws an exception (or if a JavaScript handler returns false), the task screen is redisplayed with one or more exception messages, giving the administrator a chance to address any errors and resubmit the admin task.

To create a custom business logic task handler, you write a class that extends the base class BLTHAdapter. You can implement your adapter so that CA IdentityMinder can execute the business logic at various points during the synchronous phase of task execution.

You can implement any or all of the following methods in your custom adapter: