Overview of usable Velocity attributes for email templates

Hi,

I would like to add one identity attribute of our identity mapping in the “Access Request Reviewer” email template. I need to adress the recipient of the entitlement, but the SailPoint documentation is not that transparent to me. Let’s say my identity attribute is called “uid”. I was trying to add it in the email template with ${recipient.uid}, but this was failing. I only found this documentation Available Email Templates - SailPoint Identity Services, but so far it didn’t help. I also tried __recipient.uid and $__recipient.uid, but it didn’t work either. Does anyone know how I can achieve this and is there a better documentation for velocity attributes?

With kind regards

Fabienne

Hi Fabienne,

The “Access Request Reviewer” email template uses version 1 global variables.

You can fetch user identity data and use it in the template.
The example is provided in the sample above.

user → The email recipient’s identity data → Any attribute of the identity including, but not limited to, name, alias, firstname, lastname, displayName, uid, manager, phone, workPhone

To fetch user attributes, you have to specify with ${user.attribute}. For example ${user.name}

Hope that helps!

Hi @fabienne_florian,

If you are looking to get the entitlement recipient’s attributes, I don’t think you can refer that in this email template.

The ${user} variable is used to get the email recipient’s details as per the version1 template.

I know some email templates like LCS change template supports something like ${identity.uid}. Don’t think this template supports that.

I would suggest to treat the email templates more as a notifications / heads-up system, not so much like shopping receipt dispenser. e.g. If it was a banking system, think about what information it would email to the customers, and what information is expected to be fetched / read /viewed via secure channels.

For example, avoid having uid, org-chart, entitlement / role / AP details in the notification.

Hi, yes, I mean to the recipient of the entitlement. “User” is refering to the recipient of the email. Sorry, maybe that was not that clear in my description.

I just tried ${identity.uid}, but this didn’t work either. So, I guess this is not possible if this is template 1.

I just wonder why there are some attributes in the OOTB email template which are not mentioned in the documentation like: ${requestedForIdentityName} which is the name of recipient of the entitlement. I mean this must be related to the identity attribute “displayname”. So I was wondering if there is some non-documented option for getting the uid.

With kind regards

Fabienne

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.