Loading...
Loading...
In Quebec Patch 0, if a customer used Virtual Agent Designer to create a topic which calls a Flow Designer Action/Subflow, and that Action/Subflow returns an output of type "Reference", then upgrading to Quebec Patch 1 will cause a problem. This article contains a workaround for QP1 customers. Steps to Reproduce 1)Create an action in Flow Designer with output of type reference. 2) In VA Designer create a topic that consumes the action. 3)Save/Publish and test Or - Import the update set and sys_cb_topic attached, save/publish and test ACTUAL: Reference is undefined EXPECTED: Reference correspond correctly
In VA Designer, at the topic created in step 2) above: instead of using a low-code "Datapill' to access the "Reference" output param, use a script instead. For example, if the "Reference" output was for the "incident" table and your topic wants to display "short_description" property from that record, write script like this: (function execute() { var obj = JSON.parse(vaInputs.output_reference); var gr = new GlideRecord(obj.value.table_name); gr.get(obj.value.sys_ids[0]); return gr.short_description; })()
PRB1477508
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.