04-24-2018 08:29 AM
Hi,
is there a way how to set value for CallVariable on ECE chat or email dialog?
In the event about new chat or email, there is list of available actions for this dialog, where I see also UPDATE_CALL_DATA:
<mediaType>ECE_Chat</mediaType>
<participants>
<Participant>
<actions>
<action>UPDATE_CALL_DATA</action>
<action>WRAP_UP</action>
<action>CLOSE</action>
<action>PAUSE</action>
<action>TRANSFER</action>
</actions>
<mediaAddress>1080</mediaAddress>
<startTime>2018-04-17T10:22:06.518Z</startTime>
<state>ACTIVE</state>
<stateChangeTime>2018-04-17T10:23:14.913Z</stateChangeTime>
</Participant>
</participants>
<state>ACTIVE</state>
<uri>/finesse/api/Dialog/152412_25467640_1</uri>
But when I send PUT request to that dialog with:
<Dialog>
<requestedAction>UPDATE_CALL_DATA</requestedAction>
<mediaProperties>
<callvariables>
<CallVariable>
<name>callVariable1</name>
<value>Some value</value>
</CallVariable>
</callvariables>
</mediaProperties>
</Dialog>
I get back error message:
<ApiErrors>
<ApiError>
<ErrorType>Invalid Input</ErrorType>
<ErrorData>requestedAction</ErrorData>
<ErrorMessage>Invalid 'requestedAction' specified for task</ErrorMessage>
</ApiError>
</ApiErrors>
The same thing works for voice dialogs perfectly, but does not seem to work for non voice dialogs. All other actions like PAUSE, CLOSE etc. seem to be working also for non voice dialogs. So the problem is only with UPDATE_CALL_DATA.
Is it by design or am I doing something wrong?
Thanks
Martin
Solved! Go to Solution.
04-25-2018 10:25 AM
Hi Martin,
Looks like it is a bug. The bug is the fact that UPDATE_CALL_DATA shows up as an allowable action and it should not. It is by design that tasks are not able to update the call variables.
Thanx,
Denise
04-24-2018 11:33 AM
Hi Martin,
Interesting. According to the documentation for non-voice dialogs, I do not see the UPDATE_CALL_DATA being listed: https://developer.cisco.com/docs/finesse/#dialog-apis-for-nonvoice-tasks/dialog-apis-for-nonvoice-tasks
Since the error says that it is an invalid action even though it is listed as an allowable action, I suspect that it is a bug. I will check with the Finesse team.
Thanx,
Denise
04-25-2018 10:25 AM
Hi Martin,
Looks like it is a bug. The bug is the fact that UPDATE_CALL_DATA shows up as an allowable action and it should not. It is by design that tasks are not able to update the call variables.
Thanx,
Denise
04-26-2018 03:09 AM
Hi Denise,
thanks for investigation and clarification.
So probably there is no other way how to write some data to tasks, right?
Thanks,
Martin
04-26-2018 10:15 AM
Hi Martin,
That is correct. There isn't a way to write data for tasks.
Thanx,
Denise
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide