Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/08/2022 06:33 AM
Hi,
I am using the below variable for task creation.
Binding Variable | Description |
${task?.requestKey?.id} | Obtains the request ID associated with the task |
The task id that comes in the email is a 3 digit number which is different than the actual request id or the task id. In the Saviynt system, which id is picked up by this variable and how can I match it in the system?
Thanks
K
08/08/2022 06:59 AM
Request ID: ${requestid} --> Actual Request ID(Request History/Request Approval)
Task No:${task?.id} --> Actual Task ID (visible under tasks (pending/Completed))
08/08/2022 07:01 AM
08/08/2022 08:11 AM
Hi, Thanks for your responses but ${requestid} and :${task?.id} did not work for me in the task creation template. Also is does ${task?.requestKey?.id} display? ${task?.requestKey?.id} comes back with an id which I cannot match in the system so wondering what id that is.
08/08/2022 09:34 AM
${task?.requestKey?.id} gives internal process id.
Can you confirm where email template is attached workflow/Endpoint Level/Global Config
& share logs if its not fixed
08/08/2022 09:45 AM
Thankyou @rushikeshvartak. If this an internal process id then I think Saviynt should not give this as a binding variable for task creation email because I dont know how the fulfillment team will use it unless there is a good reason for this to be sent out in the email (Just my thought).
When I add request id or task id in the email for task creation, the email does not trigger whereas request id works fine for task completion. I will try to get the logs.
Again, Thankyou so much for all your help !!
08/08/2022 11:12 AM
Easy way to find all variables in email template
use below code in email body.
${this.binding.variables.each {k,v -> println "$k = $v" + "<" + "br" + ">"}}
08/15/2022 06:47 AM
@km Did it resolved your issue if yes you can accept working solution 🙂