The application doesn't use any prompts, it makes use of TTS for the voice menus. The properties file is in the project file structure - under the 'config' folder. This folder must be included when exporting the project WAR file.


Prompt files for CM can be found as follows:
Login to Devconnect
Choose Downloads tab
Then under “Customer Experience Management” section choose link “Avaya Oceana Solution”
Filters – Choose Release 3.5

https://www.devconnectprogram.com/fileMedia/download/331e1225-0039-46a1-8835-80effd065b06

The Context Store Snap-In Developer Guide 3.6.0.0 does have a good section about the CS PDC for OD.

The sample application compiles in functionality from a Pluggable Data Connector - the Oceana Services PDC - and this must be dropped into the Eclipse 'plugins' folder and the workspace restarted in order to use it. The filename for 3.5 will be something like 'oceana-pdc-plugin-9.0.16'.

Hi Andrew,
That bundle of reference flows is intended to be used as part of an ecosystem; a Contact Center solution, now known as Oceana. As such, the flows don't stand alone and rely on other components and mechanisms to be in place. For example, it is expected that a front-end provider (like AAEP for voice, or a Chat/Email provider for multimedia) would perform some contact segmentation and determine what Work Assignment Services the customer is interested in. This Contact characterisation, along with additional stuff like Locale and Data Center of origin is written to Context Store by the provider and then read back at the start of the workflow (in the 'Get Context' task) when Contact processing begins.

This is why the input to 'Request Resource' looks empty - we simply pass the data we have obtained from CS telling us what Service the customer is interested in (including the Priority of the Contact and optionally the desired Proficiency of the Agent).

It is possible to use the tasks 'directly' outside of the context of Oceana; however the sample flow you specifically mentioned isn't intended to be used in this way.
Thanks.

The schema is the same as the WORK_OFFER event in the SMGR event catalog (chop off the additional unnecessary services if there’s only going to be a single service used, and maybe dropping the description).

HOWEVER, you shouldn't really be using the REST task at all in this case as the Request Resource API to Work Assignment Engine is asynchronous, so even if the task works, all you will get back is 202.

You should really be using the WA RR task - as part of the Work Assignment task bundle; there is a pre-built workflow that shows you how to use this task and how to handle the async response.