Id / GUID unique across Genesys Cloud Regions / Orgs?

Hi,

Org Id is unique across all Genesys Regions. How about other Ids / GUIDs ? Are they unique across all Genesys Regions / Orgs as well or what is their scope (say just with in Org or given region)?

  • Division Id
  • Queue Id
  • User Id
  • OAuth Client Id
  • Interaction Id
    etc?

In Premium Example App's config.js, there is a clientID defined, which is used to access information from Genesys. Does clientID work across all Genesys Orgs? Guess it should, else app cannot be generic.
Assuming this ClientID must different from typical OAuth Client we create in a Org (one automatically created by Genesys for each Genesys Org?)

Is there any documentation which explains this? Just want to make sure, we get our design right when we store this data.

Thanks!

GUIDs aren't a Genesys thing. GUIDs are pretty much unique globally across all products,
Sure it is somewhat dependent on the algorithm creating the GUID, but with all the standard methods, the odds of creating a duplicate is so vanishingly small it might as well be 0.

Professor Google says:
"How unique is a GUID? 128-bits is big enough and the generation algorithm is unique enough that if 1,000,000,000 GUIDs per second were generated for 1 year the probability of a duplicate would be only 50% . Or if every human on Earth generated 600,000,000 GUIDs there would only be a 50% probability of a duplicate."

Thanks for your inputs @Anton_Vroon, but if Genesys can confirm the Id of all Genesys Entities are indeed UID/GUID would be helpful.

I believe that you can safely assume that any ID that you get that looks like a GUID (say 9c9b1bfd-41bd-4a61-9ee6-75d7e7ff8ece), is a GUID.

However to your original question, OAuth clients can exist across Orgs, I'm not actually sure about across regions. You can read about seeing your authorized Oauth clients and configure them here:

--Jason

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.