

Requests are proxied through the backend Shindig web application. To avoid browser cross-origin issues, REST Gadgets can make REST requests to services hosted on external servers using theĬisco Finesse JavaScript Library API. Third-party gadgets are hosted on the Cisco Finesse server using theģrdpartygadget web application or on an external web server. If considerably larger number of gadgets are configured or if more users sign in (more than the tested number of users) inĪ short time frame, you must monitor the CPU consumption and network bandwidth during users sign in and ensure that the end-pointįailover uses optimization to sign in the users quickly and is not considered the same as a new browser sign in. Higher number of gadgets will also need more browser memory and network bandwidth.

When all the configured gadgets are enabled forĪll the users, it impacts the Finesse server.

The Desktop, the CPU consumption marginally increases during users sign in. When you increase the total number of gadgets that are configured on Of 8 minutes for 2000 users (agents and supervisors). Gadgets are listed in the desktop layout using the tag.įinesse Desktop is tested to perform well with an average of 20 gadgets per Desktop (across all tabs), over a sign in period With specific requirements that are not available out of the box. JavaScript library is available for any customers This helps administrator to provide access to theĬontact center agents for all the applications that is required to service callsĬisco Finesse comes with default gadgets such as, the team performance gadget, callĬontrol gadget, and call popover. The gadgets are applications that are placed Drag-and-Drop and Resize Gadget or ComponentĬisco Finesse is an OpenSocial gadget, which is an XML document that defines metadataįor an OpenSocial Gadget container.
