URL String gone for reports?
Posted: Mon Oct 29, 2012 6:54 pm
VERSION: 2.6-373a
BUILD: 120810-1018
Install VIcibox Server
Hi all,
I noticed since the 2.6 update that the String no longer appears for the reports. (I assume to eliminate the issue of long strings for the browsers). But is there still a way to generate it easily or view it somewhere?
Reason is that I used to be able to send my managers, tech, etc. a link and say something akin to "look at the calls on these DIDs, too many drops." But now it doesn't make the links. I have over 900 TF numbers so I would say daily I send about 3-5 of those types of emails. But now I have to list the DIDs the date range, etc. for them so they can then go generate it themselves. It was also very easy to bookmark a report link when I started a new campaign and wanted to track it.
I did figure out that I can still create the strings by adding the DID record number (example below), but that is obviously very tedious.
http://192.168.1.2/vicidial/AST_DIDstat ... %5B%5D=234
Was just curious if someone had a similar issue and a work-around?
BUILD: 120810-1018
Install VIcibox Server
Hi all,
I noticed since the 2.6 update that the String no longer appears for the reports. (I assume to eliminate the issue of long strings for the browsers). But is there still a way to generate it easily or view it somewhere?
Reason is that I used to be able to send my managers, tech, etc. a link and say something akin to "look at the calls on these DIDs, too many drops." But now it doesn't make the links. I have over 900 TF numbers so I would say daily I send about 3-5 of those types of emails. But now I have to list the DIDs the date range, etc. for them so they can then go generate it themselves. It was also very easy to bookmark a report link when I started a new campaign and wanted to track it.
I did figure out that I can still create the strings by adding the DID record number (example below), but that is obviously very tedious.
http://192.168.1.2/vicidial/AST_DIDstat ... %5B%5D=234
Was just curious if someone had a similar issue and a work-around?