AnsweredAssumed Answered

Custom Code in Post_Data_Process_Handlers_Pkg

Question asked by Venkata Palakaveeti on Aug 10, 2016
Latest reply on Oct 16, 2018 by Edwin Mullie

Like • Show 0 Likes0
Comment • 5

Hi Everyone,

Can anyone please guide me on how to write a custom code in Post_Data_Process_Handlers_Pkg? My scenario is I have to calculate the unique samaccountname for the user based on 1st name and lastname

something like this -- ACCNAME := substr(p_fname,1,1) || '.' || p_lname; Also, I have a logic to check with T_AV_ACCOUNTS table for check if any account exists and then append 1, 2,.... to ACCNAME if the account exists.

I would like to know how do I write this logic (any sample template of custom code will be helpful) in Post_Data_Process_Handlers_Pkg so that post unification user samaccountname is ready and so can be provisioned into AD and exchange for email.

No one else has this question

Outcomes

5 Replies

Venkata Palakaveeti Aug 16, 2016 8:21 AM
Mark Correct
Correct Answer
Hi Everyone, Any help on this is really appreciated.
Like • Show 0 Likes0
Actions
- Venkata Ramana Reddy Kanaparthy @ Venkata Palakaveeti on Aug 17, 2016 5:49 AM
  Mark Correct
  Correct Answer
  Hi... You can place any valid code in the relevant procedure. When you want to update an attribute on users post unification, you should be using the procedure Post_Data_Process_Handlers_Pkg.Post_ID_Unification_Handler
  
  You can change this procedure to add any valid SQL statement and recompile the package. The added SQL will then run from next unification onwards. The SQL depends on your requirement. I am giving very rough example of SQL that you can add in the procedure to update a specific user attribute.
  
  Ex: Update user attribute with firstname.last_name and append 1 when there is already account for user.
  
  update t_master_enterprise_users usr set CUS_ATTR_USER_CAS_7 = first_name || '.'
  || last_name || (case when (select count(*) from t_av_user_account_mappings map where user_id = usr.id and map.deletion_date is null) > 0 then '1' else '' end);
  1 person found this helpful
  Like • Show 0 Likes0
  Actions
  - Venkata Palakaveeti @ Venkata Ramana Reddy Kanaparthy on Aug 18, 2016 3:47 PM
    Mark Correct
    Correct Answer
    Thanks Ramana Reddy.
    Like • Show 0 Likes0
    Actions
Rivka Hoffnung Oct 16, 2018 7:41 AM
Mark Correct
Correct Answer
Hi,

After we used this solution, we figured out that the values we updated through SQL query will not override again through identity collection. For example, a new user "Dede Nomi" was collected from HR. Calculated samAccountName is "DEDENOM1" and t_master_enterprise_users updated as well on this record.

We have another identity collector that extends the user details such as samAccountName.

The collected value for samAccountName is different than "DEDENOM1".The new value is "DEDENOM2" and this value does not update the database.

Can you please assist? We will appreciate your quick assistance
Like • Show 0 Likes0
Actions
- Edwin Mullie @ Rivka Hoffnung on Oct 16, 2018 8:15 AM
  Mark Correct
  Correct Answer
  It has to do with the order of the IDC collectors and how you defined the authoritative source for samAccountName. This blog and referenced pdf provide more details on how unification works
  
  https://community.rsa.com/docs/DOC-64703
  
  Edwin
  Like • Show 1 Like1
  Actions

Custom Code in Post_Data_Process_Handlers_Pkg

Outcomes

Related Content

Recommended Content