change.itil.approve.role.req (sysapproval fields)

[Justin Docken]

Hello, 

I'm trying to add some additional information to our "Approval Request - Req/RITM" request, which utilizes the change.itil.approve.role.req email template, and I'm wondering where I can see a list of available fields that are being Dot walked from "sysapproval" which isn't a table. The table utilized is Approval [sysapproval_approver], but the Dot walked fields don't belong to this table.

Example from the body of the change.itil.approve.role.req email template:

Short Description: ${sysapproval.short_description}

Priority: ${sysapproval.priority}

Category: ${sysapproval.category}

These fields don't belong to the [sysapproval_approver] table. Where are they coming from and where can I see all of the fields available to me via sysapproval?

Thank-you!

[Mahendra RC · Accepted solution]

Yes Justin.. similarly it will pick the data from REQ and RITM because if the approval is for any other table like REQ, RITM etc then sysapproval field will refer REQ/RITM or any other for which the approval is created. So this sysapproval field will always have the reference of the record for which the approval is created. It will pick the value for dot walked in fields from those table

[Mahendra RC]

Hello @Justin Docken 

There is a field name sysapproval on sysapproval_approver table which stores the record for which the approval are generated. For example if the approvals in sysapproval_approver table are generated for Change Request record then sysapproval field on sysapproval_approver table will have reference of that Change request as shown below:

so the below field are dot walked from Change Request table:

Short Description: ${sysapproval.short_description} // Change Request.Short Description

Priority: ${sysapproval.priority} // Change Request.Priority

Category: ${sysapproval.category} // Change Request.Category

[Justin Docken]

Hello Mahendra! Thank-you for your response, this does help, and I'm curious then if the sysapproval_approver record is tied to a RITM or a REQ, will the Change Request Dot Walked fields NOT pull any information into the email? I'm seeing that in fact there is information pulled into the email regardless of what type of record the approval is for. 

Can you please help me understand how these DOT walked fields can pull information in for any of these types of records with the same field name that is Dot walked? Maybe, because the field name is the same across all of these types of records? Thank-you!

[Mahendra RC · Accepted solution]

Yes Justin.. similarly it will pick the data from REQ and RITM because if the approval is for any other table like REQ, RITM etc then sysapproval field will refer REQ/RITM or any other for which the approval is created. So this sysapproval field will always have the reference of the record for which the approval is created. It will pick the value for dot walked in fields from those table

[Mahendra RC · Accepted solution]

Hello @Justin Docken 

Just wanted to check with you, if the above response answered your question. If yes, then please do close this thread/question by marking the appropriate response as correct.