Creating a notification with field values from a custom table not extended from task

[Steve_M]

We have a scoped application that requires approvals. The approvals are showing up just fine and the email notifications are going out. However, we can't seem to pull any values from the source table using the typical syntax.

In the Message HTML section we have:

Number : ${sysapproval.number}
Requester: ${sysapproval.requester}
Change classification: ${sysapproval.change_classification}
Description: ${sysapproval.description_of_change}
End date : ${sysapproval.end_date}

All the text shows up but all the field names are empty. I've looked at other examples and this is what it shows.

I did look at the Approvals table and I see the request and the Approving value is pointing to the custom table and the right item in the table the request is for. It even shows the right source table. For some reason they're going out blank.

This is what the log shows:

Number :
Requester:
Change classification:
Description:
End date :
 
Ref:MSG69521317​

Also when I add the following no email is sent.  It's like it can't find the email object.

Comments:
Please approve or reject this request using the links below.  If rejecting, please provide reason in your email response.
 
${mailto:mailto.approval} Approve via Email
 
${mailto:mailto.rejection} Reject via Email
 
 
Click here to view Approval Request: ${URI}
Click here to view the Request : ${sysapproval.URI_REF}

It pops this error in the log. This is the just the top part of it.  This works in other places.

For input string: "mailto.approval": java.lang.NumberFormatException: For input string: 
"mailto.approval": java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
java.lang.Integer.parseInt(Integer.java:580)
java.lang.Integer.parseInt(Integer.java:615)
com.glide.substitution.FieldSubstitute.replace(FieldSubstitute.java:63

Any ideas on what I might try?

Thanks in advance,

Steve

[Michael Bachme1 · Accepted solution]

We had a similar issue, but for KB approvals. Our solution was to use "document_id" instead of "sysapproval". Something like that may work for you.

[Steve_M]

That did the trick for getting the data to show up. Now if I can just solve the approval links having an issue. Thanks for the reply!

[Michael Bachme1]

Glad to hear that did the trick. What might work for the approval link is to use ${URI}. As you may know, it places a link to the Approval entry on the sysapproval table, not the actual record needing approval.

[Sue143]

@Michael Bachme1 

I am experiencing a similar issue. I would be interested to know if you were able to fix the links to approve/reject or how did you approach a solution for this issue?

Thank you.