Blogs

Finesse Developers,

Are you excited about Cisco Live in Orlando? We are because we're anxious to share all of the progress that the Finesse team has made over the past year. We also want to provide details on our Finesse 10.0 release.

There are two Finesse sessions this year:
  • BRKCCT1031 -- Cisco Finesse: Revolutionizing the Agent Experience
  • BRKCDN1001- Programming with the Finesse API
  • ...Read More

 

Finesse gadgets can be hosted on your own web server or on the Finesse server itself.

To host gadgets on your own web server, you host the gadget just as you would any web site. You could use IIS, Apache, etc. That is up to you.
...Read More

 

bMost of the information you need is in this Finesse Developer Center and there is a detailed presentation for Finesse Developers here https://communities.cisco.com/docs/DOC-28452

You can explore the Finesse Developer Center http://developer.cisco.com/web/finesseand if you can’t find what you need, let us know.
...Read More

 

I. Disclaimer
-------------------------------------------------------------------------------

The SampleGadget_WebService sample gadget is intended to serve as an example of
using the gadgets.io.makerequest function to make a request of a web server that is
accessible via Finesse server.



This is only a sample and is NOT intended to be a production quality ...Read More

 

The SampleGadget_Logging sample gadget is intended to serve as an example of initializing and using the
Finesse logger.

This sample illustrates how to initialize the logger and log a message to the console and the Finesse agent logs on the Finesse server.

1. initialize private var
clientLogs = finesse.cslogger.ClientLogger;
2. connect with hub ...Read More

 

Showing 1 - 5 of 22 results.
Items per Page 5
of 5

Forums

« Back to General Questions

Add an option to sign-in API for extension-less login

Combination View Flat View Tree View
Threads [ Previous | Next ]
I'm not sure if this would be possible, but it would be nice to have the extension parameter of the SignIn API be optional. The 'agent' would be signed into the web service so they could make other request but Web Services would not sign that agent into the CTI server. The call control API's of course would be disabled. This would make it possbile to develop an application to access Agent and Queue based statistics without requiring a phone to be configured.  This application would be usefull to executives, who rarley have agent extensions, or even supervisors who do not require a CTI controlled phone. 
 
I'm not sure if this is currently in the plans, but I thought I'd throw it out there.

Good point, Scott.  We will take on this work when we do supervisor controls. 

Collateral


No files available