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.
|