Sailpoint Issue document.docx (535.8 KB)
The identity attributes are in Chinese characters, however the value from Workday is plain text English.
The identity attributes are derived from the workday attributes with the Remove Diacritical Remarks transform.
Not sure why the identity attribute value is in Chinese characters. The Identity Start date was Sept 7th, Identity has processing error while applying transform to ADcn identity attribute. Due to that Identity not changed from Onboard lifecycle state to Active. Could you please help on this issue.
Hi @ravikumar7284 Remove diacritics won’t convert non-ASCII to ASCII, it will only remove diacritics (accents, marks, etc) from ASCII. Seems to me you want to be using the legal name, rather than the preferred name for your CN transform.
Hello Ravikumar. I would start by looking at the adCn processing error.
Your Chubb AD Account Name transform reads preferredFirstName, firstname, preferredLastName, and lastname using identityAttribute. SailPoint notes that identityAttribute is not intended inside another identity-profile attribute calculation because those attributes are calculated in parallel and may not yet contain current values. This can lead to identity exceptions, so it may be related to the AttributePromotionException you are seeing. (Identity Attribute transform docs)
I would suggest replacing those four identityAttribute inputs with direct Workday accountAttribute inputs for the corresponding source fields, while keeping your existing preferred-name/fallback logic. (Account Attribute transform docs)
After the change, use Preview on the Identity Profile and check adCn, preferred first/last name, and Lifecycle State. If they calculate as expected, run Actions > Process Identity for the affected identity. Also verify that cloudLifecycleState is returning the expected Active lifecycle-state value. (Creating Identity Profiles)
For the Chinese characters, Remove Diacritical Marks does not translate Chinese to English. It can convert something like Ā to A, but it will not convert 刘 to Liu. (Decompose Diacritical Marks)
Since your screenshot shows Workday DISPLAY_FIRST_NAME__c = Lydia while the identity shows a Chinese preferred first name, I would check the result in Preview after fixing adCn. If Preview shows Lydia, reprocessing the identity may correct the stored value. If Preview still shows Chinese, I would verify the exact Workday account and source attribute being evaluated.
Hi Harish, Thanks for your time. I will update the transform and preview the identity
Hi Harish, Thank you for the detailed guidance.
I agree that the use of identityAttribute references within the Chubb AD Account Name transform could be contributing to the issue, especially since preferredFirstName, preferredLastName, firstname, and lastname are identity attributes that may be calculated in parallel and not always be available during transform evaluation.
I’ll review the transform and test replacing those identityAttribute references with the corresponding Workday accountAttribute values while retaining the existing preferred name and fallback logic.
I’ll also use Identity Profile Preview to validate the calculations for adCn, preferred first/last name attributes, and Lifecycle State, and then reprocess the affected identity to confirm the results.
Hi Harish, Thank you for your suggestion. I found the root cause for this issue.
Here is the root cause analysis:
It seems the identity was initially onboarded with Chinese characters (刘 / 翊彤). While Workday was later updated to English (Lydia / Liu), the identity record remains frozen because the attribute promotion process fails and rolls back.
And as per the logs, it is the transform Chubb AD Account Name that has failed.
It seems that in the Chubb AD Account Name transform, the regex [^a-zA-Z] strips the current Chinese characters on the identity down to empty strings “”.
The outer concat adds 7 spaces (" "), but the subsequent substring attempts to read 8 characters (end: 8).
Because the total string length is only 7 characters, it throws an out-of-bounds AttributePromotionException, and the refresh fails, the issue is due to the Chubb AD Account Name transform.
So for now, to update the transform definition directly by ensuring the padding length is at least 8 spaces (change " " to " ")(7 spaces to 8 spaces). The issue has been resolved and user lifecycle state changed from Onboard to Active. Email address updated successfully.