![]() ![]() |
#1
|
|||
|
|||
![]()
Has anyone been able to create "custom" reports out of the IPOCC?
|
#2
|
||||
|
||||
![]()
Do you review this manual ?
IP Office Contact Center – Reporting Task Based Guide |
#3
|
|||
|
|||
![]()
I'm looking into Custom Reports myself. Within Avaya CCC we had the option of creating Custom Reports with Crystal Reports and with Avaya CCR through MS Report Builder 3.0. I understand how "custom" reporting works through the Avaya IPO CC interface. I am running 9.1 and need to be able to create statistics with custom formulas and indicators. What can be done to achieve this?
|
#4
|
|||
|
|||
![]()
The way to use customers tools is to create a report with requested counters an export in cvs. Then import the cvs into customers tool for further handling. There is no direct interface in the database.
|
#5
|
|||
|
|||
![]()
Wow, that sucks! Anyone at least knows how to change the default headers within the tables so I can put a name instead of the abbreviated variable name? For example: totNewCon, just so I can change it to Answered.
|
#6
|
|||
|
|||
![]() Quote:
As for something like Crystal Reports, Qlikview, etc, the reporting engine is driven by the tr schema in the Postgres dbase, so you could probably connect to it with the Postgres ODBC driver and extract info. **NOTE: I have no idea if this would be sanctioned by Avaya or what it might do to future service requests.** |
#7
|
|||
|
|||
![]()
Excellent! I saw the option but was hesitant. If now I know that the original labels are kept, so nothing else goes missing, I'll do that. Thanks for the reply!
|
#8
|
|||
|
|||
![]()
You can reach the Transaction database tables directly from a customers tools (like MS reporting), but you have to write all the queries, there are no predefined.
Check Avaya IP Office Contact Center Feature Description.pdf chapter 8. This will describe the different level of transaction table. With the postgre admin user you can create readonly user for reporting. NOTE: to connect to postgreSQL you need 32bit version of ODBC driver. The 64bit version will never connect! |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|