NodeJS Escalation API - Bot Context Data Handling

1. The Bot app (the client of the SDK a.k.a. "the app") requests a chat passing in a requestChat that contains the getContextDataSpec property with a value that is a function.

2. The SDK, seeing that the property has been set, calls the corresponding function, passing the id that should be used as the contextId claim within the JWT generated. It also passes a callback function that the app can use to deliver the result.

3. The app generates the context data according to the specification. An example:

{
 "customer": {
   "id": {
     "value": "string",
     "isAsserted": true
   },
   "email": {
     "value": "string",
     "isAsserted": true
   }

 }

}

This object is set as the value of the contextData claim within the JWT payload.

4. The app signs the payload to produce a signed JWT.

5. The signed JWT is set as the value of the contextData property within the contextDataSpec object that is passed to the SDK via the callback function the app was given. Note that if an error occurred, this would be indicated by using a non-null value for the first argument to the callback; in this case no error occurs, so the value is null.

6. Within the SDK callback, the contextData property value, together with the account ID, is wrapped in an object which is then posted to the CafeX Context Data Server at the appropriate time.