Draft:PEC-Hybrid/Current/Admin/About - Revision history

Bgrenon: re

2022-02-10T18:40:40Z

Show changes

Ed.jamer@genesys.com: Text replacement - "CX CX" to "CX"

2021-11-10T14:04:23Z

Text replacement - "CX CX" to "CX"

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

2021-11-09T22:30:07Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud C([^X])" to "Genesys Cloud CX C$1"

2021-11-09T21:39:18Z

Text replacement - "Genesys Cloud C([^X])" to "Genesys Cloud CX C$1"

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud ([^C])" to "Genesys Cloud CX $1"

2021-11-09T21:38:35Z

Text replacement - "Genesys Cloud ([^C])" to "Genesys Cloud CX $1"

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud([^ ])" to "Genesys Cloud CX$1"

2021-11-09T21:35:50Z

Text replacement - "Genesys Cloud([^ ])" to "Genesys Cloud CX$1"

Ed.jamer@genesys.com: Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises"

2021-11-09T21:16:29Z

Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:12:45Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [oO]n-[pP]remises" to "Gxxx Exxx on-premises"

2021-11-09T21:06:58Z

Text replacement - "Genesys Engage [oO]n-[pP]remises" to "Gxxx Exxx on-premises"

Matthew.west@genesys.com at 14:14, April 14, 2021

2021-04-14T14:14:49Z

@@ Line 23: / Line 23: @@
 |structuredtext=Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning.
-To support the different authentication mechanisms in Genesys Cloud CX Integration, you must create a transaction object in Genesys Multicloud CX Configuration Server. Genesys Engage on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
+To support the different authentication mechanisms in Genesys Cloud CX Integration, you must create a transaction object in Genesys Multicloud CX Configuration Server. Genesys Engage on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud CX Common Services and UIs.
-Use Genesys Administrator Extension to manually create all of the Genesys Cloud Common Service–related configuration information in Configuration Server at the Tenant level.
+Use Genesys Administrator Extension to manually create all of the Genesys Cloud CX Common Service–related configuration information in Configuration Server at the Tenant level.
 After you purchase a common cloud service, a Genesys Cloud CX Organization is created for you and you will receive a welcome email to activate your admin accounts with Genesys Cloud CX.
@@ Line 198: / Line 198: @@
 |sectionHeading=Opening Your Network
 |alignment=Vertical
-|structuredtext=You must modify the permissions on our network to permit the Genesys Multicloud CX Components and UIs to access Genesys Cloud Common APIs over your network and into the Internet. To do this, you must create a set of new firewall rules for the Genesys Cloud CX Authentication and Common Services URLs.
+|structuredtext=You must modify the permissions on our network to permit the Genesys Multicloud CX Components and UIs to access Genesys Cloud CX Common APIs over your network and into the Internet. To do this, you must create a set of new firewall rules for the Genesys Cloud CX Authentication and Common Services URLs.
 |Status=No
 }}
 }}

@@ Line 27: / Line 27: @@
 Use Genesys Administrator Extension to manually create all of the Genesys Cloud Common Service–related configuration information in Configuration Server at the Tenant level.
-After you purchase a common cloud service, a Genesys Cloud Organization is created for you and you will receive a welcome email to activate your admin accounts with Genesys Cloud.
+After you purchase a common cloud service, a Genesys Cloud Organization is created for you and you will receive a welcome email to activate your admin accounts with Genesys Cloud CX.
 A '''Genesys Cloud organization''' has been created for you to support your hybrid integration. This organization has been provisioned with the following:
@@ Line 124: / Line 124: @@
 |anchor=TransactionObjHybrid
 |alignment=Vertical
-|structuredtext=A transaction object is needed for Genesys components to authenticate with Genesys Cloud.
+|structuredtext=A transaction object is needed for Genesys components to authenticate with Genesys Cloud CX.
 <ol>
 <li>Create a transaction object (and alias) of type '''list''' named '''hybrid_integration''' in the '''Transaction''' folder of the '''Environment''' tenant.
@@ Line 185: / Line 185: @@
 </ul>
 </li>
-<li>For the Agent Pacing Service, create the following Object options in the '''ewt''' section for the pacing engine to connect to Genesys Cloud:
+<li>For the Agent Pacing Service, create the following Object options in the '''ewt''' section for the pacing engine to connect to Genesys Cloud CX:
 <ul>
 <li>'''client_id''': The Client Credential Grant Client ID that you created in step 1c of the Genesys Cloud Provisioning section.</li>

@@ Line 3: / Line 3: @@
 |DisplayName=Provisioning Genesys Multicloud CX Hybrid Integrations
 |TocName=Provisioning
-|Context=This article describes the essential provisioning steps to enable a hybrid integration between Gxxx Exxx on-premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
+|Context=This article describes the essential provisioning steps to enable a hybrid integration between Genesys Engage on-premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 13: / Line 13: @@
 *{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Predictive Engagement)
-**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Gxxx Exxx on-premises.
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
 **{{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
@@ Line 23: / Line 23: @@
 |structuredtext=Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning.
-To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Multicloud CX Configuration Server. Gxxx Exxx on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
+To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Multicloud CX Configuration Server. Genesys Engage on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
 Use Genesys Administrator Extension to manually create all of the Genesys Cloud Common Service–related configuration information in Configuration Server at the Tenant level.

@@ Line 3: / Line 3: @@
 |DisplayName=Provisioning Genesys Engage Hybrid Integrations
 |TocName=Provisioning
-|Context=This article describes the essential provisioning steps to enable a hybrid integration between Genesys Engage On-Premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
+|Context=This article describes the essential provisioning steps to enable a hybrid integration between Gxxx Exxx on-premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 13: / Line 13: @@
 *{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Predictive Engagement)
-**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Gxxx Exxx on-premises.
 **{{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
@@ Line 23: / Line 23: @@
 |structuredtext=Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning.
-To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Engage Configuration Server. Genesys Engage On-Premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
+To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Engage Configuration Server. Gxxx Exxx on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
 Use Genesys Administrator Extension to manually create all of the Genesys Cloud Common Service–related configuration information in Configuration Server at the Tenant level.

@@ Line 36: / Line 36: @@
 *A default '''AI Agent''' role (if required by your integration) that provides agent access to AI services, such as Genesys Predictive Engagement.
-As an administrator, you may access your Genesys Cloud organization by logging in at https://login.mypurecloud.com (or a [https://developer.mypurecloud.com/api/rest/index.html region specific login] URL;  The Genesys Cloud welcome email directs you to the appropriate application URL for your region) with the credentials you set when you activate your Genesys Cloud account from the welcome email you received.
+As an administrator, you may access your Genesys Cloud organization by logging in at https://login.mypurecloud.com (or a [https://developer.genesys.cloud/api/rest/index.html region specific login] URL;  The Genesys Cloud welcome email directs you to the appropriate application URL for your region) with the credentials you set when you activate your Genesys Cloud account from the welcome email you received.
-Upon activation of your Genesys Cloud account, perform the steps in the Genesys Cloud Provisioning Steps section below using the Genesys Cloud Admin UI or the [https://developer.mypurecloud.com/api/rest/v2/ Genesys Cloud API].
+Upon activation of your Genesys Cloud account, perform the steps in the Genesys Cloud Provisioning Steps section below using the Genesys Cloud Admin UI or the [https://developer.genesys.cloud/api/rest/v2/ Genesys Cloud API].
-With the credentials provided in the Welcome email, you can log in to the '''Genesys Cloud Admin''' UI for [https://developer.mypurecloud.com/api/rest/index.html your region] to perform the provisioning steps described in the next section.
+With the credentials provided in the Welcome email, you can log in to the '''Genesys Cloud Admin''' UI for [https://developer.genesys.cloud/api/rest/index.html your region] to perform the provisioning steps described in the next section.
 #In the '''Genesys Cloud Admin''' UI, select '''Account Settings'''.
@@ Line 56: / Line 56: @@
 <li><p>For each Genesys Engage Service that uses a common service you must create an OAuth client to allow for better control and monitoring of the components using the Genesys Cloud Services and for different rate limiting per client. (This does not mean that if you have ''n'' number of components on premises that are associated with one another, they cannot share a given client id.)</p>
 <p>Genesys recommends that you consult architecture before performing this step.</p>
-<p>Login to your [https://developer.mypurecloud.com/api/rest/index.html Genesys Cloud Region], then follow these steps:</p>
+<p>Login to your [https://developer.genesys.cloud/api/rest/index.html Genesys Cloud Region], then follow these steps:</p>
 <ol type="a">
 <li>Create a Client Credential OAuth Client that is to based on the specific services you are using, such as the [https://all.docs.genesys.com/ATC/Current/PacingServiceDeployment/ProvisioningArticle Pacing Service]. It is required to create the Genesys Cloud Genesys Engage Identity Provider (IDP). In your Genesys Cloud Region, create a Client Credential Grant. Open '''Integrations''', select '''OAuth''', and enter '''PureEnagage Client Credentials''' as the App name in the '''Client Details''' tab. Select the '''Client Credentials''' grant type.<br>
@@ Line 67: / Line 67: @@
 [[File:Hybrid_Client_Credential_OAuth_Grant.png|500px]]
 </li>
-<li>Or using the API, reference [https://developer.mypurecloud.com/api/rest/v2/oauth/ these endpoints].</li>
+<li>Or using the API, reference [https://developer.genesys.cloud/api/rest/v2/oauth/ these endpoints].</li>
 <li>Copy the client ID and Secret for later use.</li>
 </ul>
@@ Line 93: / Line 93: @@
 Save the cert.pem (public key) and key.pem (private key) for use in the creation of the Transaction object described in the next section.
 </li>
-<li>Create a Genesys Engage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.mypurecloud.com/developer-tools/#/api-explorer Genesys Cloud Developer Tools], [https://developer.mypurecloud.com/api/rest/client-libraries/ SDKs], or [https://developer.mypurecloud.com/api/rest/v2/identityprovider/ Platform APIs].<br>
+<li>Create a Genesys Engage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.genesys.cloud/developer-tools/#/api-explorer Genesys Cloud Developer Tools], [https://developer.genesys.cloud/api/rest/client-libraries/ SDKs], or [https://developer.genesys.cloud/api/rest/v2/identityprovider/ Platform APIs].<br>
 Sample Request:<br>
 <source lang="text">
@@ Line 144: / Line 144: @@
 <li>'''default_agent_role_name''': The default Genesys Cloud agent role name for an '''AI Agent'''. This will always be '''employee'''. </li>
 <li>'''default_admin_role_name''': The default Genesys Cloud admin role name. This is '''admin'''.</li>
-<li>'''base_auth_url''': The base auth URL that can be used for any Genesys Cloud service; for example: '''base_auth_url''' should be <nowiki>https://[region_host]/oauth/token</nowiki> (for example: <nowiki>"https://login.mypurecloud.com/oauth/token"</nowiki>). <nowiki>[region_host]</nowiki> is the authentication-based FQDN for the region; the regions are listed on [https://developer.mypurecloud.com/api/rest/ this page].</li>
+<li>'''base_auth_url''': The base auth URL that can be used for any Genesys Cloud service; for example: '''base_auth_url''' should be <nowiki>https://[region_host]/oauth/token</nowiki> (for example: <nowiki>"https://login.mypurecloud.com/oauth/token"</nowiki>). <nowiki>[region_host]</nowiki> is the authentication-based FQDN for the region; the regions are listed on [https://developer.genesys.cloud/api/rest/ this page].</li>
-<li>'''base_service_url''': The base URL that can be used for any Genesys Cloud service; for example: '''base_service_url''' should be <nowiki>https://[region_host]/api/</nowiki>. <nowiki>[region_host]</nowiki> should be the API-based FQDN for the region; the regions are listed on [https://developer.mypurecloud.com/api/rest/ this page]. The rest of the URL is Genesys Cloud service and version specific; for example: '''...v2/conversations'''. The '''base_service_url''' and the service specific portion is combined in your component code.</li>
+<li>'''base_service_url''': The base URL that can be used for any Genesys Cloud service; for example: '''base_service_url''' should be <nowiki>https://[region_host]/api/</nowiki>. <nowiki>[region_host]</nowiki> should be the API-based FQDN for the region; the regions are listed on [https://developer.genesys.cloud/api/rest/ this page]. The rest of the URL is Genesys Cloud service and version specific; for example: '''...v2/conversations'''. The '''base_service_url''' and the service specific portion is combined in your component code.</li>
 <li>'''organization_domain_suffix''': Create this option in the Annex of the "hybrid_integration" transaction object. If the username of the agent in the Genesys Engage system is not defined as an email address, this option is appended to the Genesys Cloud organization short name for this tenant ('''organization_sname''') to generate a username with valid email format. A valid value is a string representing a valid DNS top-domain. The default value is '''com'''.</li>
 </ul>