Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: EDOC-170
Table of Contents
maxLevel3

...

Overview

There are three different integrations between Genesys Cloud and eMite - Application, Data, and Users.

  • The Application Integrationdescribes the configuration of eMite as an App within Genesys Cloud and shared user authentication for SSO functionality.

  • The Data Integration describes the configuration of OAuth credentials within Genesys Cloud for access to Genesys Cloud APIs and Notification Service.

  • The Users Integration describes the configuration of Genesys Cloud groups for shared permissions and data visibility within eMite.

...

Custom Application Configuration

Note

This guide is intended for a Genesys Cloud Administrator and requires Admin privileges within Genesys Cloud.

Tip

Integration Checkpoint

All configuration items configured below must be sent to eMite using the Genesys Cloud Integration Details Form.

...

Generic Integration Information

Genesys Cloud Region

Your Genesys Cloud region will determine the URLs used in the integrations between eMite and Genesys Cloud. If you do not know your region, please refer to your login URL to determine the corresponding region, as below:

Login Domain

Region Name

Region Code

login.mypurecloud.com.au

Asia Pacific (Sydney)

au

login.mypurecloud.jp

Asia Pacific (Tokyo)

jp

login.mypurecloud.ie

EMEA (Dublin)

eu

login.mypurecloud.de

EMEA (Frankfurt)

eucentral

login.euw2.pure.cloud

EMEA (London)

uk

login.mypurecloud.com

Americas (US East)

useast

login.usw2.pure.cloud

Americas (US West)

uswest

login.cac1.pure.cloud

Canada (Central Canada)

cndCanada (Central Canada)

cnd

login.mec1.pure.cloud

Middle East (UAE)

me

Organization Short Name

The Organization short name is stored in the Account settings. It is a unique name which is used to identify the Genesys Cloud organization.

...

Tip

Generic Integration Checkpoint

These details can now be sent to eMite:

  • Organization Short Name

  • Application Redirect URL

...

Application Integration

The following processes are required to create an application integration within Genesys Cloud for eMite:

  • Genesys Cloud user group for application access

  • Application link in Genesys Cloud Apps menu

  • OAuth Client for SSO Authentication

...

Create Access Group

1. Select Admin from Genesys Cloud main menu.

...

5. Input the name of each user that you want to add to the group in the Add User field.

6. Click Save.

...

Create Custom Client Application

1. Select Admin from Genesys Cloud main menu.

...

  • Application URL: This will be in the format https://<RegionCode>-cloud.emite.com/emite/<organizationShortName>/Auth/OAuthPureCloud?org=<organizationShortName> as defined in General Integration Information above.

  • Application Type: select Standalone

  • Application Category: <blank>

  • Iframe Sandbox Options: allow-scripts, allow-same-origin, allow-forms, allow-modals, allow-popups, allow-downloads

  • Group Filtering: Add the emite_Access group created above

9. Click Save.

...

Create OAuth Client

1. Select Admin from Genesys Cloud main menu.

...

Tip

Application Integration Checkpoint

These details can now be sent to eMite:

  • emite_SSO OAuth Client ID

  • emite_SSO OAuth Client Secret

...

Data Integration

The following processes are required for data integration between Genesys Cloud and eMite:

  • Genesys Cloud Role for OAuth permissions

  • OAuth Client for API Polls (Historical data)

  • OAuth Client for Notification Subscription (Real-time data)

  • Optional OAuth Clients for WFM data

...

Create an eMite Adapter Role

1. Log on to Genesys Cloud and select Admin.

...

Note

All Outbound Permissions listed must be selected, even if your organization does not use outbound campaigns.

#

Type

Permission Name

Permission Level

1

Analytics

Conversation Detail

View

2

Analytics

Conversation Aggregate

View

3

Analytics

Conversation properties

All Permissions

4

Analytics

Evaluation Aggregate

View

5

Analytics

Queue Observation

View

6

Analytics

User Aggregate

View

7

Analytics

User Detail

View

8

Analytics

User observation

View

9

Analytics

Flow Aggregate

View

10

Analytics

Survey Aggregate

View

11

Conversation

Communication

View

12

Architect

Flow

View

13

Authorization

Grant

View

10

14

Directory

User

View

11

15

Directory

User profile

View

12

16

External Contacts

Contact

View

17

Outbound

Campaign sequence

View

13

18

Outbound

Campaign

View

14

19

Outbound

Contact list

View

15

20

Outbound

Contact

View

16

21

Outbound

Response set

View

17

22

Outbound

Wrap up code mapping

View

18

23

Routing

Queue

View

19

24

Routing

Queue

Join

20

25

Routing

Queue

Search

21

26

Routing

Wrap up code

View

22

27

Quality

Evaluation Form

View

23

28

Quality

Evaluation

View

29

Quality

Survey

View

24

30

WFM

Agent

View

25

31

WFM

Agent

Edit

26

32

WFM

Historical Adherence

View

27

33

WFM

Realtime Adherence

View

28

34

WFM

Adhoc Forecast

View

29

35

WFM

Agent Schedule

View

30

36

WFM

Intraday

View

31

37

WFM

Agent Schedule Notification

View

32

38

WFM

Activity Code

View

33

39

WFM

Management Unit

View

34

40

WFM

Management Unit

Edit

41

WFM

Time Off Request

View

7. Add the newly created eMite Data Integration role to yourself.

...

Note

Unless you have assigned the role to yourself, you will not be able to assign it to any OAuth later in the process.

...

Create OAuth Client for API Integration (Historical Data)

1. Select Admin from the Genesys Cloud main menu.

...

Tip

Data Integration Checkpoint

These details can now be sent to eMite:

  • emite_APIdata OAuth Client ID

  • emite_APIdata OAuth Client Secret

...

OAuth Client for Genesys Cloud Channel Subscription (Real-time data)

1. Select Admin from the Genesys Cloud main menu.

...

Tip

Data Integration Checkpoint

These details can now be sent to eMite:

  • emite_RealtimeData OAuth Client ID

  • emite_RealtimeData OAuth Client Secret

...

OPTIONAL: OAuth Clients for Genesys Cloud WFM

These additional OAuth Clients are only required if your Organization is using Genesys Cloud WFM.

...

  1. One additional OAuth for API Integration (i.e. Historical) - named emite_WFMLookback

  2. One additional OAuth for Channel Subscription (i.e. Real-time) - named emite_WFMActivity

...

User Integration

Create Groups

1. Select Admin from Genesys Cloud main menu.

...

Note: Users that are added to the _DashboardCreator group will be able to create, edit, and share additional wallboards and dashboards in eMite.

...

Assign Users to Groups

1. Select Admin from Genesys Cloud main menu.

...

Tip

User Integration Checkpoint

All configuration items configured above must be sent to eMite using the Genesys Cloud Integration Details Form.

  • Full names for all emite groups created

...

Assign eMite Roles and Permissions

The eMite application onboards data for every agent in your Genesys Cloud Organization. It utilizes a data onboarding license which is tracked using the integration > emiteApps > View Genesys Cloud permission.
This means that every agent that eMite collects data for must have the integration > emiteApps > View permission assigned, no matter how many users actually access the eMite dashboards.

...

...

Integration Checkpoint

Tip

Integration Checkpoint

All configuration items configured above must be sent to eMite using the Genesys Cloud Integration Details Form.