Routing API
By integrating these prebuilt API Rules into AppBase, users can easily harness the Genesys Conversation API's full potential. These rules might include predefined request and response formats, authentication mechanisms, error handling procedures, and other essential components that are essential for successful API communication.
GEN_findQueues
This rule finds Genesys queues by name.
Input Params:
- QueueName (Required): Queue name in Genesys
Output Params:
- ErrorCode
- ErrorMessage
- Queues: JSON list of queues.
Methods in Extensions
Before executing these methods, you should init auth token:
using DCM.GenesysHelper.Services;
string pureCloudUrl = ConfigurationManager.AppSettings.Get("PURECLOUD_URL");
string clientId = ConfigurationManager.AppSettings.Get("PURECLOUD_CLIENTID");
string clientSecretId = ConfigurationManager.AppSettings.Get("PURECLOUD_CLIENTSERCRETID");
int regionHost = DcmConvertHelper.SafeObjectToInt(ConfigurationManager.AppSettings.Get("PURECLOUD_REGIONHOST"));
AuthService authService = new AuthService();
authService.SetAuthToken(pureCloudUrl, clientId, clientSecretId, (PureCloudRegionHosts)regionHost);
How to get debug enabled flag. Debug data will be available in Conversation History (if we have ConversationId) or the system monitor.
string result = request.AsString("GEN_ADVANCED_LOGGING");
bool isDebugEnabled = result == "1";
Method | Definitions |
---|---|
DCM.GenesysHelper.Services.RoutingService.GetQueueId | Description: Returns the QueueId by queue name. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetQueues | Description: Searches all Genesys Queues, that are the "work baskets" for Genesys Conversations. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetUsersInQueue | Description: Returns list of all Users that are members of a queue. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetUserQueues | Description: Returns all Queues the User is a member of. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetWrapupCodes | Description: Wrap-Up Codes are like Resolution Codes on a Conversation Session. Every Queue has a list of available Wrap Up Codes. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetWrapupCodes | Description: This API should return all Wrap-Up Codes for a specific Queue. It can do a search by ID or by an exact match of the Queue Name. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.CreateWrapupCode | Description: This API should create a Wrap-Up Code. This is a unique requirement for one of our customers. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.AddWraUpCodesToQueue (DCM 7.2+) | Description: Add up to 100 wrap-up codes to a queue. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetSkills | Description: Searches all Skills. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetUserSkills | Description: Returns all Routing Skills a User has. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.RoutingService.GetQueueEstimatedWaitTime | Description: Returns the estimated time it would take a Conversation in a queue to be handled by an agent. If "QueueId" is provided, it estimates the wait time for a new Conversation. If "ConversationId" is provided, it will estimate the wait time for that specific Conversation. Input:
Output:
Example:
CODE
|
DCM.GenesysHelper.Services.RoutingService.UpdateConversationPriority | Description: Changes the priority value of a Conversation. The "priority" value is an integer between -25000000 and 25000000. Input:
Output:
Example:
CODE
|