Loading...
Loading...
Loading...
Configure Genesys Cloud work automation together with ServiceNow HR Agent Workspace to route HR cases to the right agents. This setup lets you define how HR cases are distributed based on queue assignment, routing logic, and agent capacity, so the appropriate agents receive HR case workitems automatically and efficiently. HR case routing requires the HR application package, cross-scope privileges, and restricted caller access approvals, since the HR tables are owned by the sn_hr_core application scope rather than a shared scope.
The configuration uses Genesys Cloud work automation to receive and route ServiceNow HR workitems, and includes Genesys Cloud custom attributes, a workbin, a worktype, and routing queues, along with ServiceNow service channel and external queue setup.
To process HR cases routed from ServiceNow, add work automation in Genesys Cloud. A basic configuration of work automation involves creating custom attributes for work automation, creating workbins, and defining worktypes.
Add the following three attributes in the schema that defines your workitem for routing task-based items from ServiceNow:
sn_document_id_textsn_document_table_textsn_work_item_id_text| Attributes | Field Type | Length of the field |
|---|---|---|
| Small Text Field | Minimum Length: 0 Maximum Length: 100 |
| Small Text Field | Minimum Length: 0 Maximum Length: 100 |
| Small Text Field | Minimum Length: 0 Maximum Length: 100 |
Workbins are asynchronous storage areas that belong to a division. Workitems are stored in the workbins.
The case details that must be processed and routed to the correct queue or agent are defined in the worktype.
You can modify the following settings of the worktype:
sn_document_id_text, sn_document_table_text, and sn_work_item_id_text.You require a worktype Id for setting the external routing of a queue in ServiceNow. To get the worktype Id in Genesys Cloud:
https://<Genesys_Cloud_region>.com/directory/#/admin/worktypes/37a4152c-xxxx-42a3-91e1-xxxxa930473a/summary
For more information, see Defining a worktype.
Create a queue that will receive the routed HR workitem or verify that an existing queue is ready for use. Ensure that the queue has:
For more information, see Create and configure queues.
Set up and activate the service channel for HR work assignment in ServiceNow. For more information, see Create or configure a service channel.
Configure the presence states with the service channel created for HR work assignment. From the ServiceNow workspace, navigate to Advanced Work Assignment > Presence States. For all the presence states that are used by the agents who receive HR work, ensure to add the service channel created for HR work assignment.
agent.offline error when attempting to assign the workitem.For more information, see Create presence states in ServiceNow.
Before you create external queues in ServiceNow, create and configure queues in Genesys Cloud.
With the setup of Unified Experience from Genesys and ServiceNow integration, administrators must create queues in ServiceNow that are externally routed to Genesys Cloud. When you create a queue in ServiceNow, select the External option and enter the following information:
This setup links ServiceNow assignment behavior with Genesys Cloud work automation routing.
Create the required sys_scope_privilege records so that the Genesys application scope can read HR tables.
| Source scope | Target scope | Operation | Type | Target |
|---|---|---|---|---|
| x_inics_genesys | sn_hr_core | read | Table | sn_hr_core_case |
| x_inics_genesys | sn_hr_core | read | Table | sn_hr_core_case_operations |
| x_inics_genesys | sn_hr_core | read | Table | sn_hr_core_task |
The HR tables are not made available to all application scopes and hence these records are required.
Create or approve the required sys_restricted_caller_access records for HR case routing.
Source record
| Source scope | Target scope | Status |
|---|---|---|
| x_inics_genesys | sn_hr_core | Allowed |
| Genesys integration scope | HR core scope | Approved for read access |
Target record
| Operation | Target scope | Owning scope | Status |
|---|---|---|---|
| read | Scope-level access | sn_hr_core | Allowed |
| read | sn_hr_core_case_operations | sn_hr_core | Allowed |
| read | short_description | sn_hr_core | Allowed |
| read | description | sn_hr_core | Allowed |
| read | number | sn_hr_core | Allowed |
For more information, see About Unified Experience from Genesys and ServiceNow.
Get user feedback about articles.