HTML not Rendering in Comments from IPaaS
Hello, I have an IPaaS HTML notification template that gets set correctly; however, when I used the Update Ticket action and provide comments, the HTML is not rendered in the Comments section of the ticket (see below). Is there a configuration setting that I am missing so the HTML is rendered correctly?
Thanks Tevis
Answers (2)
Hi Tevis - here is the screenshot I promised you. This screenshot uses your "TDX Tickets (Production)" connector actually!
As you can see, when you search "Update Ticket" in the search box, you have a few options. One of them is in a section that starts with "TDX Tickets (Std)". This section means standard actions - actions created and maintained by TDX.
If you select the Standard Action version of "Update Ticket", you should see "HTML Description" in the list of parameters below.
If you don't see a "TDX Tickets (Std)" section on your connector, make sure the standard action is enabled:
- On the top nav, go to Administration > Connector Definitions
- Find TDX Tickets and click on it
- On the left nav, select Standard Actions
- Make sure the box next to "Update Ticket" is checked
- No need to save, it will auto-save
Note that this is only an issue because you have connectors that were created prior to the "Connector 2.0" release we did about a year or so ago. Any newly-created connectors will automatically have the Standard Actions set up.
I do have one question on using the STD action in that the AppID in the action call is not populated. See the following.
https://app.screencast.com/v3WHnufh5IxOP
Thanks, Tevis - Tevis Boulware Thu 6/29/23 10:55 AM
Regarding that AppID issue, the video is too cropped. I can see you're using the Production TDX Tickets connector, but what application are you using it in? Is it possible that the credential you're using is pointed to sandbox, and therefore can't get the production AppIDs? - Carrie Willis Fri 6/30/23 9:25 AM
Hi Tevis,
In your notification template, please try using {{{tripleBrackets}}} around any fields where HTML will be used. For example, if your template has a macro like {{commentBody}} , change it to {{{commentBody}}} .
Using triple brackets around a macro will remove any HTML encoding and allow the HTML to come across as rendered. Using double brackets will replace any HTML with its plaintext equivalent.
Let me know if that works for you!
Best,
Carrie
Ah, understood. If you go to your connector definition for TDX tickets, you should see a "Standard Actions" area. Make sure to check the box for "Update Ticket", which will add the standard action to your connector. The "HTML Description" element should be there on the standard action.
Carrie - Carrie Willis Wed 6/28/23 2:36 PM
Thanks, Tevis - Tevis Boulware Wed 6/28/23 6:48 PM