Last updated on MARCH 23, 2014
Applies to:Identity Manager - Version 220.127.116.11.2 and later
Information in this document applies to any platform.
When the XL.UserDeleteDelayPeriod is set and the end date of some user is passed the user is marked as "Disabled" and the usr_automatically_delete_on
is set for the user (when the Disable/Delete User After End Date scheduled task is ran).
When enabling the disabled user from UI or via trusted recon with single recon event the user is marked as "Active" and the usr_automatically_delete_on is cleared. However if the user is activated
again via bulk recon event the user is set as "Active" but the usr_automatically_delete_on is left untouched even if the EnableUserActionHandler which should clear the field value is marked as
executed and completed. The problem is that when created from bulk recon handling the ENABLE orchestration is created as PostProcessOnlyBulkOrchestration for which the "action" events are not
executed but only marked as "completed". See OrchProcessData.runActionEvents() for details.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms