@azure-rest/communication-job-router

Azure Communication Services Job Router REST client library for JavaScript

This package contains a JavaScript SDK for Azure Communication Services Job Router. Read more about Azure Communication Services here

Please rely heavily on our REST client docs to use this library

Key links:

• Source code
• Package (NPM)
• Samples

Getting started

Currently supported environments

• LTS versions of Node.js

Prerequisites

• You must have an Azure subscription to use this package.

Have an ACS Resource

Create an ACS resource in the Azure Portal or use an existing resource.

Install the @azure-rest/communication-job-router package

Install the Job Router REST client library for JavaScript with npm:

npm install @azure-rest/communication-job-router

Create and authenticate an AzureCommunicationRoutingServiceClient

To use an Azure Active Directory (AAD) token credential, provide an instance of the desired credential type obtained from the @azure/identity library.

To authenticate with AAD, you must first npm install @azure/identity

After setup, you can choose which type of credential from @azure/identity to use. As an example, DefaultAzureCredential can be used to authenticate the client.

Set the values of the client ID, tenant ID, and client secret of the AAD application as environment variables: AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET

Tutorial: Route jobs to workers using the Azure Communication Services Job Router SDK

In this tutorial, you will learn:

• How to create a queue.
• How to create workers and assign them to a queue.
• How to route jobs to workers.
• How to subscribe to and handle Job Router events.
• How to complete and close jobs.

Start a NodeJS Express server

In a shell (cmd, PowerShell, Bash, etc.) create a folder called RouterQuickStart and inside this folder execute npx express-generator. This will generate a simple Express project that will listen on port 3000.

Example

mkdir RouterQuickStart
cd RouterQuickStart
npx express-generator
npm install
DEBUG=routerquickstart:* npm start

Install the Azure ACS Job Router SDK

In the RouterQuickStart folder, install the ACS Job Router SDK by executing npm install @azure-rest/communication-job-router --save.

Routing Jobs

Construct an AzureCommunicationRoutingServiceClient

First we need to construct an AzureCommunicationRoutingServiceClient.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

Create a Distribution Policy

This policy determines which workers will receive job offers as jobs are distributed off their queues.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const id = "distribution-policy-123";
const result = await routerClient
  .path("/routing/distributionPolicies/{distributionPolicyId}", id)
  .patch({
    contentType: "application/merge-patch+json",
    body: {
      name: "distribution-policy-123",
      mode: {
        kind: "longestIdle",
        minConcurrentOffers: 1,
        maxConcurrentOffers: 5,
        bypassSelectors: false,
      },
      offerExpiresAfterSeconds: 120,
    },
  });

Create a Queue

This queue offers jobs to workers according to our previously created distribution policy.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const distributionPolicyId = "distribution-policy-123";
const queueId = "queue-123";
const result = await routerClient.path("/routing/queues/{queueId}", queueId).patch({
  contentType: "application/merge-patch+json",
  body: {
    distributionPolicyId: distributionPolicyId,
    name: "Main",
  },
});

Create Workers

These workers are assigned to our previously created "Sales" queue and have some labels.

• setting availableForOffers to true means these workers are ready to accept job offers.
• refer to our labels documentation to better understand labels and label selectors.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const id = "router-worker-123";
const result = await routerClient.path("/routing/workers/{workerId}", id).patch({
  contentType: "application/merge-patch+json",
  body: {
    capacity: 100,
    queues: ["MainQueue", "SecondaryQueue"],
    labels: {},
    channels: [
      {
        channelId: "CustomChatChannel",
        capacityCostPerJob: 10,
      },
      {
        channelId: "CustomVoiceChannel",
        capacityCostPerJob: 100,
      },
    ],
  },
});

Job Lifecycle

Refer to our job lifecycle documentation to better understand the lifecycle of a job.

Create a Job

We can create a job with the following:

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const queueId = "queue-123";
const jobId = "router-job-123";
const result = await routerClient.path("/routing/jobs/{jobId}", jobId).patch({
  contentType: "application/merge-patch+json",
  body: {
    channelId: "ChatChannel",
    queueId: queueId,
    channelReference: "abc",
    priority: 2,
    labels: {},
  },
});

(Optional) Create a Job With a Classification Policy

Create a Classification Policy

This policy classifies jobs upon creation.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const classificationPolicyId = "classification-policy-123";

const result = await routerClient
  .path("/routing/classificationPolicies/{classificationPolicyId}", classificationPolicyId)
  .patch({
    contentType: "application/merge-patch+json",
    body: {
      name: "test-policy",
      fallbackQueueId: "queue-123",
      queueSelectorAttachments: [
        {
          kind: "conditional",
          queueSelectors: [
            {
              key: "foo",
              labelOperator: "equal",
              value: { default: 10 },
            },
          ],
          condition: {
            kind: "direct-map-rule",
          },
        },
      ],
      prioritizationRule: {
        kind: "static",
        value: { default: 2 },
      },
    },
  });

• Refer to our classification concepts documentation to better understand queue selectors and worker selectors.
• Refer to our rules documentation to better understand prioritization rules.

Create and classify a job

This job will be classified with our previously created classification policy. It also has a label.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const jobId = "router-job-123";
const classificationPolicyId = "classification-policy-123";
const job = await routerClient.path("/routing/jobs/{jobId}", jobId).patch({
  contentType: "application/merge-patch+json",
  body: {
    channelReference: "66e4362e-aad5-4d71-bb51-448672ebf492",
    channelId: "voice",
    classificationPolicyId: classificationPolicyId,
    labels: {
      department: "xbox",
    },
  },
});

Events

Job Router events are delivered via Azure Event Grid. Refer to our Azure Event Grid documentation to better understand Azure Event Grid.

In the previous example:

• The job gets enqueued to the “Sales" queue.
• A worker is selected to handle the job, a job offer is issued to that worker, and a RouterWorkerOfferIssued event is sent via Azure Event Grid.

Example RouterWorkerOfferIssued JSON shape:

{
  "id": "1027db4a-17fe-4a7f-ae67-276c3120a29f",
  "topic": "/subscriptions/{subscription-id}/resourceGroups/{group-name}/providers/Microsoft.Communication/communicationServices/{communication-services-resource-name}",
  "subject": "worker/{worker-id}/job/{job-id}",
  "data": {
    "workerId": "w100",
    "jobId": "7f1df17b-570b-4ae5-9cf5-fe6ff64cc712",
    "channelReference": "test-abc",
    "channelId": "FooVoiceChannelId",
    "queueId": "625fec06-ab81-4e60-b780-f364ed96ade1",
    "offerId": "525fec06-ab81-4e60-b780-f364ed96ade1",
    "offerTimeUtc": "2023-08-17T02:43:30.3847144Z",
    "expiryTimeUtc": "2023-08-17T02:44:30.3847674Z",
    "jobPriority": 5,
    "jobLabels": {
      "Locale": "en-us",
      "Segment": "Enterprise",
      "Token": "FooToken"
    },
    "jobTags": {
      "Locale": "en-us",
      "Segment": "Enterprise",
      "Token": "FooToken"
    }
  },
  "eventType": "Microsoft.Communication.RouterWorkerOfferIssued",
  "dataVersion": "1.0",
  "metadataVersion": "1",
  "eventTime": "2023-08-17T00:55:25.1736293Z"
}

Subscribing to Events

One way to subscribe to ACS Job Router events is through the Azure Portal.

1. Navigate to your ACS resource in the Azure Portal and open the “Events” blade.
2. Add an event subscription for the “RouterWorkerOfferIssued” event.
3. Select an appropriate means to receive the event (e.g. Webhook, Azure Functions, Service Bus).

Refer to our "subscribe to Job Router events" documentation to better understand subscribing to Job Router events.

app.post('/event', (req, res) => {
    req.body.forEach(eventGridEvent => {
        // Deserialize the event data into the appropriate type
        if (eventGridEvent.eventType === "Microsoft.EventGrid.SubscriptionValidationEvent") {
            res.send({ validationResponse: eventGridEvent.data.validationCode });
        } else if (eventGridEvent.eventType === "Microsoft.Azure.CommunicationServices.RouterWorkerOfferIssued") {
           // RouterWorkerOfferIssued handling logic;
        } else if ...
    });
    ...
});

Accept or Decline the Job Offer

Once you receive a RouterWorkerOfferIssued event you can accept or decline the job offer.

• workerId - Id of the worker accepting or declining the job offer.
• offerId - Id of the offer being accepted or declined.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const workerId = "router-worker-123";
const offerId = "offer-id";

// Accept the job offer
const acceptResponse = await routerClient
  .path("/routing/workers/{workerId}/offers/{offerId}:accept", workerId, offerId)
  .post();
// or decline the job offer
const declineResponse = await routerClient
  .path("/routing/workers/{workerId}/offers/{offerId}:decline", workerId, offerId)
  .post();

Complete the Job

The assignmentId received from the previous step's response is required to complete the job. Completing the job puts it in the wrap-up phase of its lifecycle.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const workerId = "router-worker-123";
const jobId = "job-id";
const assignmentId = "assignment-id";

const completeJob = await routerClient
  .path("/routing/jobs/{jobId}/assignments/{assignmentId}:complete", jobId, assignmentId)
  .post({
    body: {
      note: `Job has been completed by ${workerId} at ${new Date()}`,
    },
  });

Close the Job

Once the worker has completed the wrap-up phase of the job we can close the job and attach a note to it for future reference.

import JobRouterClient from "@azure-rest/communication-job-router";

const connectionString =
  "endpoint=https://<YOUR_ACS>.communication.azure.com/;accesskey=<YOUR_ACCESS_KEY>";
const routerClient = JobRouterClient(connectionString);

const workerId = "router-worker-123";
const jobId = "job-id";
const assignmentId = "assignment-id";

const closeJob = await routerClient
  .path("/routing/jobs/{jobId}/assignments/{assignmentId}:close", jobId, assignmentId)
  .post({
    body: {
      note: `Job has been closed by ${workerId} at ${new Date()}`,
    },
  });

Troubleshooting

Logging

Enabling logging may help uncover useful information about failures. In order to see a log of HTTP requests and responses, set the AZURE_LOG_LEVEL environment variable to info. Alternatively, logging can be enabled at runtime by calling setLogLevel in the @azure/logger:

import { setLogLevel } from "@azure/logger";

setLogLevel("info");

For more detailed instructions on how to enable logs, you can look at the @azure/logger package docs.