Depending on your level of effort, all of the attendant data is stored in the registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Interactive Intelligence\EIC\Directory Services\Root\<<SITE_NAME>>\Production\<<PRIMARY_CIC_NAME>>\AttendantData
This means that you could write a script to parse the sub paths/keys of the data to return the names/types and any data relevant for the step (audio file played, etc) and then look at the JumpToType/JumpNode keys to determine where the path flows next.
You have a lot of attendant profiles, so it's going to be a balancing act for the level of effort.
The real question I'd ask, as a PureConnect customer potentially looking at cloud solutions, does Genesys pre-sales/sales support not have a tool crafted to do this for you as a sales nicety? Knowing some of the tools that PSO has related to attendant, I can't imagine that there isn't an internal tool they could use to assist you in doing this.
These are just my initial thoughts, hopefully someone else here has already built a script or has a better option for you.
------------------------------
Aaron Lael
State of Utah - comments on this forum reflect my own personal opinions\observations and are separate from any entity I am otherwise involved in.
------------------------------
Original Message:
Sent: 03-08-2022 11:53
From: Katie Dodge
Subject: HELP! Attendant Profiles
I am hoping someone can help or assist!
We are currently documenting all 255 (yes I know it's a lot!) Attendant profiles, in preparation to migrate to Genesys Cloud from a PureConnect platform.
Is there an easy way to document each call tree and all the information within each profile in Attendant, or is this something manually we will have to do? And if it's a manual process, what would be the best way to do this?
All suggestions welcomed!
Thank you in advanced!
#ArchitectureandDesign
#CloudMigration(NEW)
------------------------------
Katie Dodge
North American Bancard
------------------------------