Customising the IdM User Interface - MSKEYVALUE and Display Name

[paul_abrahamson_sap]

Hi,

When you look at the assigned persons in a role / privilege assignment or when assigning people to groups or even custom entry types etc. If your MX_PERSON record has a DISPLAYNAME the UI displays the DISPLAYNAME, however if it doesn't have the DISPLAYNAME attribute it appears to show the MSKEYVALUE.

Does anyone know how to get the system to display both the MSKEYVALUE and the DISPLAYNAME either as columns in the assigned section or as a concatenated string?

We do know how to alter the layout of the main search screen, this is just about the actual assigned persons table within a UI task for an attribute which is an entry reference attribute.

Example, we have a requirement where we link a number of MX_PERSON records in an attribute called Z_RELATED_IDS which is an entry reference to MX_PERSON. This way we can link related identities to each other. However if all of them have the same display name it's not possible to see which one is which in terms of their MSKEYVALUE which in our case is their Windows login name and the local part of their email address. So it's hard to distinguish one record from the other without first clicking on the hyperlink to bring up the person popup window.

Thanks

Paul

[former_member2987 · Accepted solution]

Paul, the only way I know to concatenate the values and have them appear on the screen would be to put the value into display name.

Are you referring to having the values (MSKEYVALUE and DISPLAYNAME) appear in the resilts grid?

Matt

[paul_abrahamson_sap · Accepted solution]

Thanks this would be the simplest solution.

Our MX_PERSON records Display Name will hold the person's full name as presented from the golden source systems. For Staff that is SAP HCM and for Students, it will be the Student Record System.

We could concatenate the MSKEYVALUE onto this in the To Identity Store Passes, but in the case of records maintained only in IdM (i.e. no golden source e.g. Visitors and other External identities), we currently allow the Service Desk to specify / modify the display name. If we then automate the concatenation as an action task linked to the web-enabled task, we could end up concatenating the MSKEYVALUE multiple times after each edit of the record. This would require some javascript to intelligently examine the existing DISPLAYNAME and if it contains the MSKEYVALUE already then not append it, otherwise append it.

This is all possible, but I'm not sure if the need justifies the effort?

We could also populate the DISPLAYNAME in a validation class using the extension framework, but we currently don't have NWDS enviornment in our landscape and so developing and deploying validation classes won't be an option for us.

Thanks for the feedback.