How we can handle special character in email logic

[SIRAJMOLLA]

Hi All,

I need one help for my email generation rule. we are using Saviynt email generation.We are using advance config from global configuration email generation. We have one complex logic there we are checking employee type and cost center and preferred name and based on the condition matching we are adding email domain and in condition if preferred name present then email is generated like below-

preferredname.lastname@domain

if not present then firstname.lastname@domain and domain name is adding based on condition matching and also based on employee type suppose it is non employee type then email like below

preferredname.lastname.ext@domain

or

firstname.lastname.ext@domain

and we also have incremental part if generated email already present then its checking the next rule that is separated by # .we have increment upto 10 that's why we have same rule with adding increment in every rule ten time separated by #.The rule is working fine as expected but we see currently if we are using Name like below-

Firstname - IGAIMS

Lastname - TÈstuserinc

Then email is generating like below-

igaims.tstuserinc.ext@domain

In the above email you guys can see special character "È" ignored by Saviynt but when we are having hyphen('-') in the lastname that time it is showing like below-

Firstname- Neha

Lastname- Hi-n

Email-    neha.hi-n.ext@domain

Then above email you guys can see its adding hyphen in the email. This are issue we are facing.

and customer also asking if below list of special character is present in the name then we need to add the conversion character in the email-

 I need help to do the email logic as mentioned above if anyone having any suggestion please let me know.

With Regards,

Siraj Molla

[pmahalle]

Hi @SIRAJMOLLA ,

Saviynt provides the FN_EIC_REPLACE DB functions to perform replace actions

Use this DB function to replace the accented letters and special characters with alternatives to transform them into acceptable characters that can be parsed by EIC. This DB function works in conjunction with the REPLACE_MAPPING dataset provided by Saviynt, which contains default alternatives for replacing these letters and characters. You can extend this dataset or create new alternatives in another dataset based on your requirements and use it with the DB function. This DB function can be used with the user import preprocessor and with advanced configuration of identity rules (System Username Generation, Email Generation, and Account Name). For more information, see Normalizing the Identity Data Using the User Import Preprocessor and Configuring Identity Lifecycle Setup. For more information about creating datasets, see Creating Datasets.

• If you want to use the DB function with the default dataset, use the following syntax: FN_EIC_REPLACE(STRING_TO_BE_REPLACED,null)

• If you want to use the DB function with another dataset, use the following syntax: FN_EIC_REPLACE(STRING_TO_BE_REPLACED,'REPLACE_MAP_CUSTOM')

where REPLACE_MAP_CUSTOM specifies the name of the dataset.

Refer below document for more details:

https://docs.saviyntcloud.com/bundle/EIC-Admin-v2022x/page/Content/Chapter02-Identity-Repository/Dat...