Hi All,
I ran into an interesting issue last week that I thought I'd share.
We are setting up a data action for service now that will read back banners/announcements that are posted in service now for callers. When running the action, we are doing a sysparam query for several attributes of the post, including whether or not it is public (i.e., result[0].public).
The action worked when tested from the UI, but took the time out route when called in a flow from architect. After putting in a support request and pulling the logs for the action from the edge, the public attribute was identified as the culprit. This is one of a list of "reserved" words in javascript that can mess up how the json package is processed by Genesys.
I was able to correct the issue like so in the translation map: "ispublic": "$.result[0].public". I just changed the result label for the response to "ispublic", and used that in the success template as well.
Ideally the action test would fail if a reserved word is used, but keep this in mind if you're experiencing a strange behaviour on a api you feel should work. This is the 2nd time this has popped up for us with service now.
https://www.w3schools.com/js/js_reserved.asp#ArchitectureandDesign#Integrations------------------------------
Dean Thames
Koch Business Solutions
------------------------------