Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: zwerg82 on August 28, 2018, 08:31:35 PM
-
Hi all,
has anybody already deployed CX Insights yet?
If so, can you share your experiences with it compared to GI2?
Thx
-
Genesys CX Insights 9.0 User's Guide, release notes was published just yesterday.
Deployment guide not yet, so need to wait a little more.
As far as I know it should be announcement about GCXI GA in closest time.
-
Is it a complete new solution or still based around a BO universe?
Sent from my Redmi Note 3 using Tapatalk
-
Nothing common with SAP BO. Its bassed on MicroStrategy 10.10
-
Damn...new DB map? Is it any good? Easier to handle?
Enviado de meu E6633 usando o Tapatalk
-
Deployment guide is available quiet some time. Just search for it, it’s not listed. (Customer Experience Insights)
It’s Microstrategy and based on Docker/Kubernetes. In addition it’s only supporting PostgreSQL for now.
That’s a little bit frustrating as if you use Oracle as the main db due to Linux deployments you now have to manage Postgres in addition. If you want to use speechminer as well you have MSSQL.
Gesendet von iPhone mit Tapatalk
-
What is default password for GCXI administrator?
Or let's say where is published in official technical docs? Can't find it.
-
There isn't any default password. You have to setup this manually during loading configuration and variables into Kubernetes. Password is specified in gcxi.properties file, in line:
MSTR_PASSWORD=[ToBeChanged: MSTR_PASSWORD]
https://docs.genesys.com/Documentation/GCXI/9.0.0/Dep/GCXIInstallProd, section Procedure: Enter database information in the properties file
-
Oh, it is new BI tool. Genesys provide you the images to run. so it is fast in term of deployment.
-
Hi there,
I'm new and I hope I'm right here o n this board.
I use CX-Insight 9.0.011 and have some question about Data Access Restriction.
In the dokumentation (Deploymentguide für CX-Insights) they show an example of how to use RPT and RPT_ORG. This works well.
They talk about RPT_ORG and RPT_LOB too, but there are no examples.
Has anyone had any experience with it?
Thanks for your answer
Stefan
-
You can refer GI2 deployment guide, they are having additional few more line for that.
eg.. otherwise, you may consider using your BI tool filter out those value.
eg
Custom Data Access Restrictions
You can customize integrated data access restrictions by configuring the following Data Access Visibility (DAV)
attributes, which are available on each object’s Annex tab:
• ORG (Organizational Role)
• GEO (Geographic Location)
• LOB (Line of Business)
You restrict access to data by defining values on the Annex tab, as follows:
• For each Person: BI login, plus one or more DAV attributes
• For each contact center group: one or more DAV attributes
As long as a user has at least one DAV attribute that matches a group, then that user
can see data from that group. For example:
• Agent Group1 has the following annex value: RPT_GEO=Daly City
• Agent Group2 has the following annex value: RPT_GEO=San Francisco
• Agent SuperVisor1 has the following annex value: RPT_GEO=Daly City
• Agent SuperVisor2 has the following annex value: RPT_GEO=San Francisco
• When Agent SuperVisor1 runs a report, the report contains data from Agent Group1, but not data from Agent Group2.
The reverse is true for Agent_Supervisor2.
....
-
Thanks ynlyst ,
Yes, that's the same as in the CX Insights deployment-guide. I think , genesys has made a copy of that toppic :D
As I found out:
The different RPT_xxx entries are for the Agentgroup (in this case)
A teamleader use only the annex "RPT" and either a "RPT_ORG" or "RPT_GEO" or "RPT_LOB", but [b]not [/b]two or all of them.
with that, you can make some difference between the Teamlaeders (as described in the example) or , for example a Supervisor.
Like This:
Team A:
RPT_ORG WEST_COAST
RPT_GEO LosAngeles
TEAM B:
RPT_ORG WEST_COAST
RPT_GEO San Francisco
Teamleader_A:
RPT "usernameA"
RPT_GEO LosAngeles
Teamleader_B:
RPT "usernameB"
RPT_GEO SanFrancisco
Until here it was known but new with the added RPT_ORG in the teams-annex
And now: New example
Supervisor WestCoast
RPT "SupervisorName"
RPT_ORG "WEST_COAST"
so you can make different access hierarchies.
The Teamleader only see his teams,
the supervisor can see both teams
Greetings.