[cisco-voip] Maximum variables in Finesse actions

[Damisch, Kevin]

Figured it out.  In my UCCX script, my ECC variable was strConcatenated - it was missing "user" on the front of it.  I renamed it to userstrConcatenated, which fixed it.  But, a typical concatenated string was about 230 characters.  The maximum length of an ECC variable is 210 characters.  So, I had to split it up into 2 separate ECC variables.

Thanks,
Kevin


From: Damisch, Kevin
Sent: Friday, July 22, 2016 8:58 AM
To: 'Damisch, Kevin' <Kevin.Damisch at oneneck.com>; cisco-voip at puck.nether.net
Subject: RE: Maximum variables in Finesse actions

Just giving an update, but still have a question on the Finesse workflow action.  I can get the HTTP request to work when sending in any of the custom variables 1 to 10 in the body of the request.  The web server I am sending the HTTP request to requires all 10 custom variables, but a workflow action restricts you to only 5 variables in a workflow action.  I was able to concatenate the values of all 10 custom variables into a single ECC variable within the script and I set that with the Set Enterprise Info step.  So, I updated my HTTP request action like this:

Name: TestHTTPAction
Type: HTTP Request
Handled by: Finesse Desktop
Method: POST
Location: Other
Content Type: application/x-www-form-urlencoded
URL: https://10.10.10.10/api/PhoneCallTracking
Body: I click the variable icon, choose Custom and type strConcatenated   (I have also tried user.strConcatenated and user.ecc.strConcatenated)
[cid:image002.jpg at 01D1E42E.A94EFE50]

This is what the action looks like:

[cid:image003.png at 01D1E42E.A94EFE50]


I watch the reactive debug go through the Set Enterprise Info step and populate the ECC variable, rings my Finesse agent, I answer it, and it fires off this HTTP action.  The web server does not like the format of the request.  Looking at the web server logs, this is what it shows for the body of the HTTP request from UCCX:

${userstrConcatenated}

If I use custom variables in the HTTP body, the values get passed to the web server just fine.  If I use ECC variables in the HTTP body, it is passing the ECC variable name, not the value of it.  So, my question is - how do you pass the "value" of an ECC variable in the body of an HTTP request action?

Thanks!
Kevin

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Damisch, Kevin
Sent: Monday, July 11, 2016 1:21 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Maximum variables in Finesse actions

Customer has UCCX 10.6(1) and trying setup an HTTP request action in a workflow.  The caller enters values in the IVR and we do some DB/web lookups within the scripts that we populate in custom variables 1 to 10.  We need to pass these 10 variables to a web server via an HTTP request.  Looks like we are hitting a roadblock of a maximum of 5 variables per action:

[cid:image004.jpg at 01D1E42E.A94EFE50]

They are currently using CAD.  Within CDA, we use IPC Actions sent to a custom application on the agent's machines.  We are sending 11 variables via these IPC Actions to that application currently and trying to migrate this over to an HTTP request within a Finesse workflow.  One thought I had is to concatenate the values of all 10 variables into a single expanded call variable and use that within the body of the HTTP request.  But, I'm not sure of any size limitation in doing this.  Thoughts?

And, why is there a limit of only 5 per action?

Thanks!
Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160722/c6e2f683/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 7550 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160722/c6e2f683/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8374 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160722/c6e2f683/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 33764 bytes
Desc: image004.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160722/c6e2f683/attachment-0001.jpg>