We have a use-case to generate unique username and copy username to systemusername in Saviynt. Data is imported from connected HR SAP source. Currently we are using MODIFYUSERDATAJSON to run preprocessor queries.
Use-case should cover:
1. username should be unique
2. username should have first 5 letters from 'lastname' and first 2 letters of 'firstname'
3. If username already exists, append the username with 1 and then 2 ...goes on
4. ñ should be replaced with n
5. username to be copied to systemusername
To replicate the use-case, we are using file import and passing preprocessor JSON to generate username and systemusername. We have tried many simple to complex query to generate unique username but only simple query works, but we couldn't achieve above use-case because Inner queries and DB functions aren't working. Data from .csv file couldn't be imported, it always shows 0 records in file and 0 inserted.
Any suggestion to achieve this use case?
Solved! Go to Solution.
You can use the out of the box feature to generate username. Go to Admin > Global Configs > Identity Lifecycle > Register User Generation Rule / Username generation rule.
All this logic used in preprocessor can be configured in the UI itself. Same thing can be configured in System Username generation rule as well.
I have seen your best practice post on inline preprocessor. We have above usecase mentioned plus we also tried to use DB functions which is not working as expected (which is mentioned in your best practice solution that it works). I would need your help if you can let me know what's the correct method to use DB functions, case statements because we have given multiple tries and non are working?
The above suggestion from Sai, I believe it doesn't work for import of users through connectors or UI and only works while registering from UI.
[This post has been edited by a Moderator - we do not allow the tagging of employees or other forum users unless they have already been active on the forum thread.)
The above requirement can be achieved by Username generation rule as suggested by Sai, In user upload from UI, if username is passed as blank it will auto trigger the username, same works for User import from connectors as well.
Also on how we can use the functions, it still works try via simple logic and then start expanding the logic, Also when you have used the above use case of inline preprocessing you will get errors in the logs to see to where the sql is breaking, from that you should be able to understand and change it as per your requriement.