Sv translation | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
The chat report export is a REST service that exports chat sessions from jtel to an external system. The report export can be initiated manually by agents in the chat session, using the Report Export button:
The configuration of the report export is performed in the Chat Connector configuration, on the REST tab. Phase 1 - Token PostPhase 1 is used to acquire an access token for the operation.
URLThis is the URL to which the post request to acquire the token should be sent. HeaderThis part specifies the headers which should be sent with the request. Any necessary headers can be specified here. BodyThis part specifies the body which should be sent with the request. Any necessary body can be specified here. Phase 2 - Report Export PostThe second phase posts the PDF report containing the chat session to the backend system. Any data can be specified in the body. URLThis is the URL to which the report post should be sent. HeaderSpecify any headers required here. The token retrieved in the first step can be specified, for example, with $tokenResponse.body.JSON.access_token BodySpecify the body of the post request here. The XML template can be inserted into the body as base64 coded data using the variable $xmlTemplate.encoded.base64 Xml TemplateThis template can contain any data, which will be base 64 coded into the body when the variable $xmlTemplate.encoded.base64is used. VariablesThe following variables are provided, which can be used in either of the requests:
|
Sv translation | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|