Has anyone used the new “Display Name” primitive operation in a transform? The documentation Display Name | SailPoint Developer Community has got the name and the type swapped. I am looking for a bit more clarity on the JSON body that needs to be used with this operation.
Based on this transform documentation, you do not need any inputs for this transform.
It will take automatically user preffered name (if exist) or given name (firstname) and append with user familyname (lastname).
For example in your mapping attribute you can your identityattribute displayname by displayname transform directly you must select in attribute column one arbitrary attribute (it will be ignored) and in the transform column you can select your displayname transform.
Thank you Ousmane for your response. I did try creating the transform without any input just using the body mentioned in the document. It fails to create the transform:
{
"detailCode": "400.1.0 Required data missing or empty",
"trackingId": "bf4dfbacb08449f88977d7f77907c466",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "Required field \"attributes\" was missing or empty."
},
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "Required field \"attributes\" was missing or empty."
}
],
"causes": []
}
While looking into this “Display Name” transforms documentation, there is no need of inputs.
This transform will take the preffered name (if present) over the given name (or) the given name and adds with the family name. For example, lets say -
given name - ram
preffered name - null
family name - mohan
transform’s output → ram mohan
given name - ram
preffered name - raja
family name - mohan
transform’s output → raja mohan
Only for the use case above it will work. If you need to append any of the values like middleInitial or other, better way is to move to the firstValid transform with concat operations.
Looks like the “attributes” field is mandatory here. So when i gave the attribute fields and given random input in it, then the transform was created properly.
“Type” should be displayName as per the documentation although the example in documentation has a typo in it.
but it does not do anything when i tested it from the identity profile. So looks like it is standard transform which will generate the displayname as given name or preferred name + family name as per the documentation.
If you would like to generate the displayname based on some other fields, i believe then you can make use of concat transform.