Is there a way to make it so that if I navigate between customers while using the script webpage component, it will not return to the original page and lose any form data that was on there before I went to look at another customer?
I am creating a form for the agent to use during the conversations and would not want them to have to redo the information going between different customers if that is possible.
Does anyone have some insight on this or even is this possible?
Managing state is the responsibility of your web application. The script component simply loads a URL that can contain information from variables at the time it's loaded, such as the conversation ID. Your application would keep a cache of the work in progress data entered by the agent, likely partitioned using the conversation ID. This cache could be in a client-side store, such as local storage or indexed DB, or could be something you provide within your infrastructure, like a database on your web server. When the agent navigates within Genesys Cloud and causes your app to be reloaded for a different conversation, your app would load its initial state from its cache instead of the defaults used for a new conversation.
I am running into a similar issue, and we have set up an intgration that refrences a screen pop URL that we use to input customer information, The integration works well and the entered information does not get erased when switching between conversations. One problem with this is that the call attribution is not passed as it is with the screen pop.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.