Description
The Queue object holds data specific to the unreleased DirectRouting feature. Previously this feature was thought to be needed to hold data related to specific flowIds connected to the queue. These were housed in DirectRoutingMediaSettings and DirectRoutingCallMediaSettings (because call had an additional voicemail related one). They are not needed anymore and are being removed, as well as DirectRoutingCallMediaSettings since all media types have the same settings at this point.
Change Category
API
Change Context
Fields and objects being removed:
- Queue->DirectRouting->DirectRoutingCallMediaSettings and its specific field voicemailFlowId
- The fields enabled and inboundFlowId from Queue->DirectRouting->DirectRoutingMediaSettings
Field being added:
- useAgentAddressOutbound into Queue->DirectRouting->DirectRoutingMediaSettings
Objects this effects by name directly or through containing or through inheritance:
- Queue
- QueueRequest
- CreateQueueRequest
- QueueEntityListing
- UserQueue
- UserQueueEntityListing
Change Impact
No action needed; the properties being removed have never been populated for any customers despite appearing in the API documentation.
Date of Change
immediate
Impacted APIs
Directly through Queue object:
- GET /api/v2/routing/queues/{queueId}
- PUT /api/v2/routing/queues/{queueId}
- POST /api/v2/routing/queues
Indirectly through QueueEntityListing object which holds Queue Objects:
- GET /api/v2/routing/queues/divisionviews/all
- GET api/v2/routing/queues
Directly though UserQueue object that extends from Queue:
- PATCH api/v2/users/{userId}/queues/{queueId}
Indirectly through UserQueueEntityListing object which holds UserQueue Objects which extend from Queue object:
- GET api/v2/routing/queues/me
- GET api/v2/users/{userId}/queues
- PATCH api/v2/users/{userId}/queues
References
[AS-2730]