Integration interfaces
The following changes have been made in the RESTful and integration interfaces.
RESTful Monitoring Interface (RMI)
The resource /queueGroups now supports the following values defined in SC:
-
queueLength
-
falseAttemptTime
RESTful Contact Management Interface (CMI)
GET /cmi/chats/{id} now supports delivery status for conversational messaging chats: 1=Sent, 2=Delivered, and 3=Read.
RESTful Contact Management Interface (CMI) and RESTful Monitoring Interface (RMI)
The /contact resource supports searching and showing internal notes (hasRemarks) and a transcript if the recording has one.
Communication Panel Third-Party Extension Messaging API
You can now query picklist content by using the new picklist command. The list returned is the same the user sees in Communication Panel's Picklist.
Event-driven integration (EDI) framework
Queue for outgoing queue calls
Previously, EDI sent contact.queue as null for all outgoing queue calls. Now contact.queue has a value when the calling agent has a queue's extension number configured as the caller number.
Maximum number of triggered integrations
The maximum number of triggered integrations was three. Now integrations with endpoint URL edi://echo are excluded from the calculation. This means you can have at most three integrations with an endpoint URL starting https:// and any number of edi://echo integrations triggered for the same conversations.
When specifying the format for a JSON request value, you can now manipulate strings by:
-
indexing, which makes it possible to refer to individual characters in a string
-
slicing, which means extracting a substring
-
reversing
-
find/replace, which also supports using regular expressions
