I believe it's crucial for the SDK to expose the ContactSwitchEvent. This would significantly improve dynamism when switching between contact cases and enable richer functionality for SDK users.
Currently, this event isn't transmitted through the SDK's WebSocket connection. Furthermore, the window event remains confined to the Agent CXone domain. This prevents a parent application (e.g., when Agent CXone is embedded in an iframe) from listening to these events, as the Agent's context doesn't pass them to the window.parent.
Exposing this event via WebSocket or by sending it to the window.parent would be a valuable improvement, allowing for greater interactivity between Agent's digital case switching and the SDK user's application features.
I believe it's crucial for the SDK to expose the
ContactSwitchEvent. This would significantly improve dynamism when switching between contact cases and enable richer functionality for SDK users.Currently, this event isn't transmitted through the SDK's WebSocket connection. Furthermore, the window event remains confined to the Agent CXone domain. This prevents a parent application (e.g., when Agent CXone is embedded in an iframe) from listening to these events, as the Agent's context doesn't pass them to the
window.parent.Exposing this event via WebSocket or by sending it to the
window.parentwould be a valuable improvement, allowing for greater interactivity between Agent's digital case switching and the SDK user's application features.