Add recording capability #35
Open
+30,388
−135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… interaction to be stored in Interaction Recorder when it's disconnected
Added record field to original post request
Checking if recording request is OK
Added StopRecording method
Added code to stop recording and save recording location to an attribute
Adding StopRecording method
Return false if StopRecording failed
|
Please resolve conflicts before we can merge! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This code adds mutliple configuration parameters as well as a new binding to handle a Vidyo Replay server and be able to start Vidyo recordings.
Since Generic Objects are completely ignored by Interaction Recorder, this code starts a screen recording when the agent picks up the interaction in order to tag it when the GO disconnects and include the link to play the Vidyo recording
A couple of handlers are required and need to be published for this matter.
The new configuration parameters are:
New binding to point to the replay server
HasReplayServer: true if the replay binding should be used. False otherwise.
I have also updated the Postman collection for testing purposes.