Hello. I'm working on a project to build a refreshed caller verification process. When I put all the steps in an inbound call flow (first data action to look up the record by phone number, two more data actions to retrieve data from additional tables, then a simple bot flow to collect slot values to use in the flow to compare input vs record data, it works fine.
To save on voice bot costs and to ensure that known customer data is not exposed in a bot, I am trying to remove everything but the slot collection values into a common module wrapper for the bot. The inbound call flow does the initial data action (it also feeds the screen pop, so applies to all inbound calls), then I call the common module to run the additional data actions and the bot flow to collect the slots. The slot values are populated and mapped to the common module, but as soon as the call returns from the bot to the common module, an error occurs and the call disconnects.
Since common modules are not exposed in execution history, I tried mapping participant data right after the bot flow, but the module fails to process anything after the return from the bot.
Has anyone experienced this, or is this a known limitation of common modules? I'd like a reusable common module that I can call in multiple flows that returns a simple verified/unverified result.
#Architect#DataActions------------------------------
Vikki Papesh
Principal Genesys Cloud Developer
Tandem Diabetes Care, Inc.
------------------------------