Where did you put the data action in your script.  Did you go to the start page properties and select Data Action as the start page load action?  If you don't see Data Action, you might need to enable that in the Script properties.  

------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com

Original Message:
Sent: 01-15-2024 11:39
From: Serena Spaccesi
Subject: Action in Script Pop Up for OUTBOUND calls

#ArchitectureandDesign
#DigitalChannels
#Implementation
#Integrations
#Outbound
#RemoteWorkEnablement
#Reporting/Analytics
#Unsure/Other

------------------------------
Serena Spaccesi
Indra Italia spa
------------------------------

Hi Serena,

Be aware that the interaction state might take a while until it is really connected. So if you call this only once at the beginning of the call the state might be still different from connected. You can solve this with a recursive call until the call is connected:

Call this action through the page load action and it should produce the results you are looking for.

Hope this helps!

Hi @Peter Faust What do you mean by 'call this action through the page load action'?  How do I set it? I would be grateful. I probably mistake this, unknowingly.
Thank you 

Hi Serena,

Be aware that the interaction state might take a while until it is really connected. So if you call this only once at the beginning of the call the state might be still different from connected. You can solve this with a recursive call until the call is connected:

Call this action through the page load action and it should produce the results you are looking for.

Hope this helps!

Hi Serena, 

The page load action Robert already mentioned. So when the script initially loads you can call one action during startup defined in the page properties. Since the call usually is not yet connected at the start of the script you must implement some sort of delay until the call is connected. This can be achieved as shown in my screenshot with the LoopAction. When the loopaction is started for the first time the script is loaded, it checks the connection status for the first time. If its not connected it waits for 5ms and the calls itself again. This is repeated until the call is connected. This will stop the loop and the action in the else path will be started. So now you can react on the real connected status.

Hi @Peter Faust What do you mean by 'call this action through the page load action'?  How do I set it? I would be grateful. I probably mistake this, unknowingly.
Thank you 

Hi Serena,

Be aware that the interaction state might take a while until it is really connected. So if you call this only once at the beginning of the call the state might be still different from connected. You can solve this with a recursive call until the call is connected:

Call this action through the page load action and it should produce the results you are looking for.

Hope this helps!

Apologies if this isn't completely on topic, but can you tell me if these "pop-ups" are actual message box pop-ups or if this is just "repainting" a screen on an already open webpage type thing ?  Thanks 

Hi Serena, 

The page load action Robert already mentioned. So when the script initially loads you can call one action during startup defined in the page properties. Since the call usually is not yet connected at the start of the script you must implement some sort of delay until the call is connected. This can be achieved as shown in my screenshot with the LoopAction. When the loopaction is started for the first time the script is loaded, it checks the connection status for the first time. If its not connected it waits for 5ms and the calls itself again. This is repeated until the call is connected. This will stop the loop and the action in the else path will be started. So now you can react on the real connected status.

Hi @Peter Faust What do you mean by 'call this action through the page load action'?  How do I set it? I would be grateful. I probably mistake this, unknowingly.
Thank you 

Hi Serena,

Be aware that the interaction state might take a while until it is really connected. So if you call this only once at the beginning of the call the state might be still different from connected. You can solve this with a recursive call until the call is connected:

Call this action through the page load action and it should produce the results you are looking for.

Hope this helps!