NERM - Email Notification

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi!

Can we use variables and Liquid expressions in the subject line of NERM Email templates?

Thanks.

2

Been a while, but this should be possible if i remember correctly.

3

Yes you can use variables in NERM email template subject. Working example below:

New Contractor Record Created for {{ attribute.ne_first_name_attribute}} {{ attribute.ne_last_name_attribute}}

4

@deepakarora In SailPoint NERM (Non-Employee Risk Management) email notifications, you can use Liquid template expressions in both the Subject and Body of the notification template. SailPoint documentation states that workflow-generated notifications support Liquid templating, and the Subject field is editable alongside the Body field. {{ profile.first_name }} {{ profile.last_name }}

5

Yes Deepak, Liquid variables and expressions work in the subject line as well as the body. So something like this in the subject field is perfectly valid:

New Contractor Request for {{ attribute.ne_first_name }} {{ attribute.ne_last_name }}

To make sure you are using the right variable reference, open your notification under Admin > Templates > Notifications and look at the attribute references shown in the editor. If you want to pull a value from the request being submitted, you could copy it from the Method column under Request Attributes. If you want a value from the existing profile instead, the ID Code column under Your Attributes would be the one to use. This keeps you from having to guess the exact attribute UID.

The Preview button only shows formatting and styling. It will not resolve the variables, so they will show up as raw {{ }} tags. To confirm everything populates correctly, it would be best to test through an actual workflow execution.

If you want to explore more of what Liquid can do in NERM (filters, conditions, loops, nested objects), Zack’s KB post on Liquid Template language use in NERM is a great reference.

6

Thanks, everyone. I was able to resolve this. Actually, I was testing through batch workflow and forgot to turn on the “Create a new request for each profile selected” switch.