Previous Topic: Logical Attribute Handler API Model

Next Topic: Custom Messages

Calling Sequence

As with all custom objects and handlers created with the CA Identity Manager APIs, CA Identity Manager executes a logical attribute handler by calling methods in the handler’s adapter object.

CA Identity Manager calls LogicalAttributeAdapter methods in the following stages of task screen processing:

  1. initializeOptionList(). This is the first method CA Identity Manager calls before it displays a task screen. This method gives the logical attribute handler an opportunity to populate any option lists on the task screen.
  2. Either of the following methods:

    When toLogical() or initialize() returns successfully, CA Identity Manager displays the task screen.

  3. validate(). Allows the handler to validate user input. This method is called after the user clicks Submit on the task screen.
  4. toPhysical(). Allows the handler to convert logical attribute values to physical attribute values.

CA Identity Manager calls logical attribute handlers in the order in which they are listed in the Management Console. In each successive handler, CA Identity Manager calls the method that is appropriate for a given stage of task screen processing. For example, validate() is called in each handler when the user clicks Submit.

Note: CA Identity Manager calls business logic task handlers after all logical attribute handler processing is complete. Thus, business logic task handlers have access to the logical attribute values and the physical attribute values set by the logical attribute handlers.