I have checked with the Pega CS developers and they say that is the only such example in the product. There is a demo flow that makes a call to google maps, but you wouldn't be running that in production without having implemented it yourself.
There is a control “PortalCoBrowsing” in the default portal provided with Pega Customer Service. This is native in the customer service stack, so any application built on top of Pega Customer Service will have this too.
In the original comment Udhay states that "It is fixed." I'm trying to understand exactly what that means. Does this mean that this site that he is referring to that is called out for in the code must be added to our whitelist /safe sites? We have added Usefirefly.com for our agents, but have not added this site and are having random disconnections. If this site should be added, please reply as such.
Hi Dan, Pega has provided hotfixes to disable calls out to the co-browse server for those customers that don't use co-browse. That was the original issue reported and the hotfix addresses that.
It sounds like you are actually a co-browse customer and have a legitimate need for your agents to go to the server. The "fix" mentioned here does not apply to you. If you are having random disconnects and other issues while using co-browse, that's a completely unrelated issue and you should contact GCS for support.
Yes, we are co-browse customers and have gone to support, but are simultaneously trying to see what it could be on our side causing the problems. If this server referenced is required by agents to use beyond the usefirefly.com, we will need to whitelist it as it will either be blocked or have minimized capability through our group policies which are very restrictive. Any server or address called out separately from the usefirefly.com site would need to be explicitly called out or is at risk of being blocked.