Programming Guides › Programming Guide for Java › Logical Attribute API › Logical Attribute API Overview › Calling Sequence

Calling Sequence

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

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

1. initializeOptionList(). This is the first method CA IdentityMinder 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:
   • toLogical(). For tasks (such as Modify User) that act on existing managed objects, allows the logical attribute handler to convert the managed object’s physical attribute values to logical attribute values.
   • initialize(). For tasks that create a managed object (such as Create User), allows the logical attribute handler to supply default logical attribute values for display on the task screen.

   When toLogical() or initialize() returns successfully, CA IdentityMinder 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 IdentityMinder calls logical attribute handlers in the order in which they are listed in the Management Console. In each successive handler, CA IdentityMinder 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 IdentityMinder 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.