Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - thermal_donkey

Pages: [1]
1
Scripting QueueMetrics / Re: Invalid XML-RPC codes in documentation
« on: February 08, 2014, 04:07:34 »
Also, using that new code OkDO.HDRRpt, I get nil back from the client, same as my other issues. Ideas?

2
Scripting QueueMetrics / Re: Invalid XML-RPC codes in documentation
« on: February 07, 2014, 19:07:55 »
On my reports page (after running for them "Today" or something like that) I don't have an IVR Details tab at all. I don't see any of those reports.

3
I'm having problems running the 6.13.1. IV01 - IVR Traversals report through the XMLRPC client, with the code IvrDO.IvrReport. It's also returning nil.

Is it possible there are some reports my QueueMetrics system just isn't set up to run? If so, where could I look to enable them? If not, could someone double check the XML code I need here?

4
Scripting QueueMetrics / XMLRPC code error for Outcomes analysis
« on: February 05, 2014, 06:10:48 »
6.12.6. OU06 - Outcomes per agent gives OutcomesDO.AgentOutcomes as its XMLRPC code in the documentation. Unfortunately, when I send the request, I get nil back. Any ideas what the code should be? Thanks!

5
I'm probably just missing something obvious here. Can anyone explain the headers for the 6.7.4. DD04 - Sales per day analysis to me?
  • Day
  • Conv.
  • QConv.
  • Sales
  • [empty but has a percent sign]
  • [bar graph]
  • QCont.
  • Contacts
  • [empty but has a percent sign]
  • [bar graph]

I'd just like to make sure I know what all those abbreviations stand for. The documentation doesn't go into any detail on them.

6
From what I can gather from the documentation, running the following analyses

6.5.2. AC02 - Detail for answered calls
6.5.3. AC03 - Detail for unanswered calls

requires some submission of the form embedded in the '6.5.1. AC01 - Area code report' analysis, used to set up the parameters by which to restrict results for the aforementioned analyses.

Therefore, it seems less than straightforward, how to run those analyses. Any hints on how to proceed here?

7
Scripting QueueMetrics / Re: Invalid XML-RPC codes in documentation
« on: January 31, 2014, 16:09:00 »
For the '6.1.13. OK13 - Music On Hold by Agent' analysis, I'm passing "OkDO.MOHOk" as the code. The docs give the exact same code for '6.1.14. OK14 - Report Header.'

For the '6.2.5. OD05 - IVR details (full list)' analysis, the given code in the docs is "DetailsDO.CallsIVR," but that returns nothing from the client.

8
Scripting QueueMetrics / Invalid XML-RPC codes in documentation
« on: January 31, 2014, 01:19:18 »
I'm trying to script gathering reports using Ruby and the "xmlrpc/client" library offer therein. However, the following analyses seem to have invalid XML-RPC codes associated in the documentation:

6.1.14. OK14 - Report Header
6.2.5. OD05 - IVR details (full list)

The former's code matches that of `6.1.13. OK13 - Music On Hold by Agent` exactly, so I'm thinking it's just a typo. The latter's code doesn't match any surrounding codes, but when I make a request using the documented code, I get nil back as a response. Can someone hook me up with the correct codes for these analyses? Thanks!

Pages: [1]