Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners Click HERE | EMEA/APJ Click HERE |
02/11/2024 01:31 PM
Trying to concatenate systemUserName and a custom string as part of email generation rule and Saviynt constantly forgets about the systemUserName.
Even though systemUserName is properly generated, email shows up as '@domain'
Rule definition
Result after import:
Solved! Go to Solution.
02/11/2024 01:36 PM
Use advanced configuration
02/11/2024 09:02 PM
Can you try something like this :
case when (users.employeetype = 'Contractor') THEN concat ('C-', users.username) ELSE users.username END
02/12/2024 07:03 AM
I had given this a try and got stumped by an interesting Saviynt behavior... it hates having > evaluations in the condition... my condition was LOCATE('-',users.firstName) > 0. Changed it for = 0 and switched around the actions and it works now, but still not with SystemUserNam
02/12/2024 06:56 AM - edited 02/12/2024 06:57 AM
I had tried using the advanced configuration but it appears as systemUserName is also being generated on the initial import, there is no value available for email assignment
I tried running another import after creation with only email address generation and a sytemUserName existing but it still could not pick it up.
Should it be possible to generate email after identity creation?
The solution I am considering now is to duplicate the systemUserName rules into email generation but it would not guarantee the value used for systemUserName would be the email prefix
02/15/2024 02:13 AM
All tests were unsuccessful. I wasn't able to use the email generation on an existing identity.
Solution identified is to build the email from systemUserName through preprocessor as part of subsequent user import.
If anyone has a better idea, I'll take it...