Hi. We are generating (email) with some complex(identity attribute rule). We need to perform this logic, only the first time user is aggregated from HR aurhoritative source. We need to prevent this code to be run for example, if user is updated on source. How can we check this information? ** note: we have to do this because email is not in HR, and not all users have AD.
Here is a thought…
use idn.countIdentitiesBySearchableIdentityAttribute() with an Identity Attribute that is mapped to a unique attribute from HR. If count is > 0, then the identity has already been created and return identity.getEmail(). Else, generate the email.
However, read the second paragraph about uniqueness check below
2 Likes
Thanks @iamnithesh !! Yes, I know about discouraging from generate unique identity attributes. But this client has an HR which it unique attribute is the person id. Regulations for my country prevent to use personal information (such id number) as any attribute of a system profile, a login for example.
I also though to create an ETL which reads from HR and write to some table, so I can user a fixed field from that table. But this implies to ask an aditional server and a database from client architecture.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.