Create an Email template

[gracieux12]

I am creating an email template for approval access requests and want to inform the user about the timeline for completing the request. Is there a way we can include the anticipated SLA in the email, similar to what we display in the UI?

For instance:

Congratulations! Your access request, Request ID: ${requestId}, has been approved, granting you access to Application: ${applicationName}. IMPORTANT – Now that the request has been approved, it will take approximately ${slaHours} hours to fulfill. Please do not attempt to access the application until this timeframe has passed.

Binding variables to use:

• ${requestId}: This will dynamically insert the unique identifier for the access request.
• ${applicationName}: This will dynamically insert the name of the application or the specific access that has been requested.
• ${slaHours}: This will dynamically insert the anticipated time in hours required to fulfill the access request.

Question for the Team: Can we implement the email template in this way by pulling the anticipated SLA data (${slaHours}) from the same field we use to display it in the UI?

Concern: My main concern is whether we have access to the SLA data at the point when the email is generated and if the binding variable ${slaHours} can be reliably populated in the email template. Additionally, can we ensure that the ${applicationName} variable correctly identifies the application or specific access requested? If there are any technical limitations or alternative methods to achieve this, please let me know.

[rushikeshvartak]

Currently this is not supported you can include Due date in email or mention when request will expired / escalated to next level

[gracieux12]

what is the biding radiable for those  ?

[gracieux12]

what about user id?  any way we can import this in the email template?

[rushikeshvartak]

• For Due Date ${request.duedate.toString().substring(0,10)}
• For username ${user.username}

To get what variables are present to use in the email template, check using the below expression. By putting it in the email body, it will print all variable names with values, and then accordingly, you can use it:


${this.binding.variables.each {k,v -> println "$k = $v" + "" + "br" + ">"}}

[gracieux12]

ok do we have 

•  ApproverFirst ApproverLast 
• approver email address this is just after submitted a request, user should see who will approve it 

[rushikeshvartak]

approvers info
${assignee.email}
${assignee.firstname} 
${assignee.lastname}

[gracieux12]

thanks. What about  

• Approval Confidence: HIGHMEDIUMLOW  
• Request Justification 
• The approval request will expire on :  VARIABLEFORAPPROVALREQUEST. Just to make sure this request is approved on time 

[gracieux12]

Another question: After creating a template, how can we pre-configure it so that this email template is automatically used when that type of request is submitted? For example, a request created template.

[rushikeshvartak]

You can find all variables using below code 

To get what variables are present to use in the email template, check using the below expression. By putting it in the email body, it will print all variable names with values, and then accordingly, you can use it:


${this.binding.variables.each {k,v -> println "$k = $v" + "" + "br" + ">"}}

[gracieux12]

Could you please send me a screenshot of how you are running this and how it displays the data? Additionally, how can I map the email template to create a request event? This should be triggered whenever we create an access request.

[rushikeshvartak]

Add script in email body and raise request and check variables

[gracieux12]

I did create the email template. Now when raising a request, how to map it to point to this template when generating an email?

[gracieux12]

Is there a way to provide the tests on how to map a template to an event?

Like a request has been submitted. An email should be generated. How do we map this email template to this event? 

[rushikeshvartak]

Attach in workflow to validate variables