Previous Topic: Design Time ActivitiesNext Topic: Screen-Defined Logical Attributes


Run Time Activities

The following activities occur when the end user executes a task on the task screen:

  1. Before displaying the task screen, CA IdentityMinder retrieves the value of the Date physical attributes (mm.dd.yyyy) from the database, and then calls toLogical() in the handler.
  2. The toLogical() method’s custom code converts the physical attribute value to the three logical attribute values. CA IdentityMinder then displays the logical attribute values in the associated Month, Day, and Year fields.
  3. While working in the task screen, the end user decides to edit an account, which is about to expire. To do so, the user changes the expiration date, and then submits the task screen.
  4. CA IdentityMinder calls the toPhysical() method. The method’s custom code converts the logical attribute values in the Month, Day, and Year fields into the associated Date physical attribute value. CA IdentityMinder then writes the Date value in the data store.