CME LOOKUPS AND EXPORT TOOLS

[Tony Tillyer]

I've noticed some areas of Genesys CME seriously lacking, from an auidt perspective(!) I've never been able to audit anything (no audit trail) and I've never been able to export anything (in Excel format, etc.) I'm thinking about developing a tool which can do lookups and exports from various areas within CME;

Users, in relation to the applied Applications and Ranks
Users, in relation to the applied Access Groups
Users, in relation to the applied Route Groups
Users, in relation to the applied Reporting Groups
Applications, in relation to Security Permission Groups

etc. etc.. etc...

It would be an MSAccess2K2 dB, utilizing ODBC for SQL7.

Anyone interested in such a tool? Has anyone already built one? Is there already one on the market?

Also, does anyone know the reason why Genesys have not yet developed an audit tool (to show who made what changes in CME,. etc.)?

Thanks,

Tony

[Kevin]

Regarding the audit trail, I believe I heard that G7 CME will have auditing capabilities (please correct me if I am wrong). To what degree, I do not know. I don't know how much you could gather from the confserv logs on debug, but you would have to develop a parser to extract the correct keywords, etc.

Re: exporting/doing lookups, if you spend some time poking around the CME database, you (or a DBA or SQL developer relatively familiar with CME objects) should be able to create some SQL queries that would extract the information desired. I know I have done it for some reports on the LOGIN and STATUS tables, as well as pulling agent and DN information . The hardest part about it is finding the correct relationships for a join just because table A has a dbid column doesn't mean you can join in to the dbid column on table B you might need to join on agent_dbid instead.

[Karl]

Hi there
yes 7 has audit capability. I would suggest downloading it to have a review. I was about to build something myself.

[Chang]

What is an auditing capability?

[Kevin]

Generally, it's the ability to track who made changes to what and when they made changes to it.

It can be as basic as updating the record with the user's name and date attached (so you know when the record was changed by whom) but you do not know what was changed.

It can be as complex as keeping a copy of the prechange record for a period of time (say, 90 days) so that you can compare the current record to any records changed within that time period essentially being able to know what field was changed by whom by what application on which workstation. (Maybe I'm exaggerating a bit, but...)

It can be very useful when something doesn't work right, because you can go back and see what changed recently (my boss tells us that 80% of production problems come from something changing), and possibly change it back.

I'm looking forward to it I think it's a great addition to the platform, especially for larger installations with multiple administrators...

[Vivek]

I have a question: does CME7 work with configserver6.5?