Hi,

you should also note the agent 'capabilities' at any point in time - it will give an indication of what is possible.

for example: when the agent object is created - 'canLogin' is false, but after activation 'canLogin' should be true (and also 'canDeactivate').

rgds

CIS Package Support

Hi,

Activation is the creation of a Client Session instance on the server, with a specified (or default) Agent profile.
Once an Agent's Client Session has been activated, then the Agent may login to the Contact Center - to start work.

The Agent doesn't have to be logged in to the contact center to start & receive Interactions - only routed Contact Center work.

So, an Agent logs in (i.e. agent.login()) to go ready / not ready etc.

rgds

CIS Package Support

Hi Don,

Your assumption is correct - the Interactions collection will be populated based on server events.

To understand how best to get working with interactions, have a look at the sample applications, or here:

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/customer_interactive/tech/the_work_api.gsp

To be notified when an interaction has been added to the collection:

//these events are attached to the Work object

work.addOnInteractionCreatedCallback(callback);

work.addOnInteractionDeletedCallback(callback);

and to add specific callbacks to an interaction object, example:

//this event is attached to the interaction object itself

interaction.addOnInteractionUpdatedCallback(callback)

Or, you could use a data-binding approach - as shown in one of the sample applications.
Both sample application show how to work with interactions, and carry out actions on an individual interaction - such as 'accept', 'end' etc.

It's also worth gaining an understanding of 'capabilities' at this point:

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/customer_interactive/guide/tutorial_capabilities.gsp

as these are also set by the server - they will give an indication on whether a requested action will be successful (i.e. on an interaction object there are a list of 'capabilities', if the 'canAccept' capability is false, then 'interaction.accept()' will likely fail)

thanks

CIS Package Support

Hi,

The Customer Interaction Services Package is built on Oceana.
At the moment CM Ad Hoc Conferencing is not supported by Oceana.

Thanks,
CIS Package support

Hi Liz,

Yes, Workspaces is built on the Customer Interaction Services package (as well as with other packages in the Client SDK).

You can have a look here:

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/customer_interactive/tech/the_work_api.gsp

To see how to work with Interactions.

You can also have a look at the sample applications included with the CIS package - these also exercise the Consult / Conference / Transfer methods.

Thanks,

CIS Package support

Hi Matthew,

The auth tutorial is a good place to start:

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/customer_interactive/guide/tutorial_auth.gsp

The credentials you mention are an Oceana Agent's credentials - so you will need a full Oceana solution to get the samples up and running.
The infrastructure requirements for each package are specified on this page

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/introduction/index.gsp

thanks

CIS Package Support

Hi Matthew,

The final documentation went live last week - with extra tutorials on auth (and with auth included in the test apps).
Can you review these, and let us know if you still have any questions?

Generally the flow is to retrieve an SSO auth token using the IDMS package, and then use this with the CIS package.
You then activate your client session, and login to the contact center to start accepting work.

thanks

CIS Package Support