i need a step by step approach for creating the emailTemplate and triggering the notifications
hi @MIDHUNKUMAR_A You can achieve this in SailPoint IIQ by combining a custom QuickLink, a workflow, and email templates. Here’s a high-level approach that worked for me:
- Create the Custom QuickLink
- Built a Custom Workflow
<Workflow name="CustomQuickLinkWorkflow">
<Step name="Start" next="Approval"/>
<Step name="Approval" type="approval" next="CheckApproval">
<Approvers>
<Identity name="spadmin"/> <!-- or use a role/group -->
</Approvers>
<EmailTemplate>approvalNotification</EmailTemplate>
</Step>
<Step name="CheckApproval" next="Approved" reject="Rejected">
<Script>
<![CDATA[
if (approvalResult == "Approved") return "Approved";
else return "Rejected";
]]>
</Script>
</Step>
<Step name="Approved">
<EmailTemplate>approvedNotification</EmailTemplate>
</Step>
<Step name="Rejected">
<EmailTemplate>rejectedNotification</EmailTemplate>
</Step>
</Workflow>
- Set Up Custom Email Template
<EmailTemplate name="approvalNotification">
<To>${approver.email}</To>
<Subject>Approval Needed</Subject>
<Body>A new request has been submitted and needs your approval.</Body>
</EmailTemplate>
- Linked theCustom Workflow to the Custom QuickLink
<QuickLink name="CustomRequest" workflow="CustomQuickLinkWorkflow" ... />
so now im working in a local instance then do i just need to configure email inside each and every attribute or file redirection of those notifications
Hi @MIDHUNKUMAR_A Yes, if your dev SMTP is already configured, you can set the email redirection to your own email address for testing purposes.
If SMTP isn’t set up or you prefer not to send actual emails during development, you can redirect the notifications to a file instead (e.g., emails.txt). That way, you can still verify the content and flow of the notifications without sending real emails.
one more thing ${approver.email} this is just where it is getting fetched from ?
Hi @MIDHUNKUMAR_A Hey!
Good question — ${approver.email} is a placeholder that IdentityIQ fills in at runtime. It pulls the email address from the Identity object of the person who’s assigned as the approver in your workflow.
So, for example, if your workflow has something like:
<Approvers>
<Identity name="spadmin"/>
</Approvers>
Then ${approver} refers to the spadmin identity, and .email grabs their email address from their identity profile in IIQ.
If you’re using dynamic approvers (like a rule or a script), just make sure the workflow sets the approver variable correctly — otherwise, the email template won’t know who to send to.