As a Webex developer, we want to give you advance notice of a key functionality change with spark-admin and spark-compliance scopes.
The following authorization scopes are now deprecated and will no longer work after August 15, 2018:
Webex Teams apps which currently use spark-admin scopes to perform compliance activities as an organization administrator will need to transition to spark-compliance scopes over the next two months. After this change, organization administrators will no longer be able to perform compliance activities. Instead, these activities will be limited to only the compliance officers for an organization.
The deprecated scopes have been removed from the Webex for Developers site and are no longer available for new applications, testing via Test Mode in the Webex Teams API Reference, or with an administrator’s portal token.
If any of your apps make use of the spark-admin scopes listed above, please update them now.
We'll keep you posted on any other changes on this, and, of course, will continue to update you on other refinements we make to further improve and enhance the Webex Teams API.
Hello, Does anybody know why the Call Costume Variable Report does not match the number of Handle calls total from Contact Service Queue Activity Report? I have removed all Contact Disposition and focus on the Handle (2) calls and still, it doesn't m...
Hi allI wondering if anyone can help me with this issue. We have multiple UCCX11.6.2 HA clusters within our environment and have been having an issue with calls getting though the UCCX script queue and disconnecting when they are being presenting to ...
I have created a button to display when call is active and in agent in TALKING status but noticed button is displaying when Agent trying to Consult with other agent(since agent status is TALKING) and would need help on how to hide this button for Consults...
Setting up a small trial flow in CVP 12.5 to communicate with a Google DF agent. I find that when I use the DialogflowIntent and DialogflowParam elements that CVP ignores the text defined within Google DF and instead uses the local TTS defined in my call ...