Populate Manager Field on Recon

Question

Hi, the manager attribute in the user-search-profile of the console is empty after each recon using DBAT connector to a non-dba_users table (by the way, the DBUM connector to a dba_users table DOES populate the manager field using the scheduled jobs). I'd like to get that job working that populates the manager field working with the DBAT table (which is the majority of accounts).
When searching the manager field, the available choices are either full name or userid.
Which path should I take to modify the DBAT job to populate the manager field?

Answer 1

If you have to search on the basis of some value of manager and if nothing is available directly, don't write this manager key population code in the Process Event Handlers.
Because since Process Event Handlers will always be triggered and they will always try to obtain Manager Login from your Database, even for any other user attribute.
Also, it would mean that for 10000s of user records, 10000s times individual user records will connect with the trusted database for picking up their individual managers... Then it defeats the Trusted Source recon purpose...
Rather write one separate custom scheduler which will be executed after say 30 minutes... It will Create database connection with your trusted database just once... So, in this way you are simply extending the OOTB Trusted Recon functionality... If you had the source code for OOTB database trusted recon, you would have embedded the logic to figure out the manager login for the user then and there itself... Since you don't have source code, you should let the OOTB recon do its default behavior. Don't use OOTB for manager, just populate USR_UDF_CUSTOM_MANAGER_SOME_VALUE attribute...
And on day 0 Trusted recon when the volume will be a lot, after all recon events are properly linked, then execute your second custom scheduler for populating manager and also some other things which your OOTB doesn't provide for in a straight forward way... Don't use Event Handlers for handling this functionality... Use Event Handlers only if there is a way to figure out the manager login within OIM Database... And yes, in that case writing custom scheduler will be an overkill... At the same time if for figuring out manager is not straight-forward and you have to hit the Trusted Database on an individual basis, use custom scheduler which will be able to process 10000s records in one go... Take into consideration all points before making your design...