WorkflowService
Class finesse.workflow.WorkflowService
Provides an API which consists of methods that allow a gadget to submit the workflow task.
Example
Methods
init(containerServices)
Initiates the WorkflowService and accepts finesse.containerservices.ContainerServices as a parameter.
Parameters
Name |
Type |
Description |
Required |
---|---|---|---|
ContainerServices |
Function |
Provides container level services for gadget developers. Gadgets can utilize the container dialogs and event handling to add or remove a service. |
Yes |
submitTask(payload)
Allows to trigger workflow for digital channels.
Parameters
Name |
Type |
Description |
Required |
---|---|---|---|
payload |
Object |
The action data of the JSON object as per the specification. |
Yes |
-->dialogId |
String |
Unique identifier of the dialog that helps in debugging an error. For example, dialogId, eventId, chatId and so on. |
Yes |
-->mediaType |
String |
The type of media under which the dialog is classified. For example, CHAT and EMAIL. |
Yes |
-->state |
Enum |
The workflow statuses are based on the task that is run. Values for Unified CCX are:
Values for Unified CCE are:
|
Yes |
-->taskVariables |
Array |
The corresponding value of the workflow name for the individual task. For example, the keys of the callVariables are callVariable name and callVariable value. |
No |