This repository was archived by the owner on Jun 30, 2022. It is now read-only.
Pass triggered agent when getting a new room#213
Merged
renatobecker-zz merged 1 commit intodevfrom Apr 11, 2019
Merged
Conversation
diegolmello
approved these changes
Apr 11, 2019
renatobecker-zz
deleted the
pass-current-triggered-agent-to-new-livechat-room
branch
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
When a real agent is used to send triggers messages and a new conversation is started, the same agent needs to be assigned to the new livechat room.
Otherwise, the routing method may get another agent in the queue.
Related to:
RocketChat/Rocket.Chat.js.SDK#73
RocketChat/Rocket.Chat#14103