[Regression] Omnichannel On hold Queue #21240
Merged
Conversation
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
…events - Returning chat to the queue - Forwarding chats - Closing chats
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.
Proposed changes (including videos or screenshots)
NOTE: This PR is to be merged after PR #20945 since it's built on top of it
Here we're handling following events which were getting impacted by this new on-hold feature
For each of the above events, we're making sure that recent changes to Routing mechanism for on-hold feature isn't changing the existing behaviour of these events.
Additionally we're making sure that if any of the above events are triggered from a chat which is already On Hold, then we cleanup all the OnHold chat related properties.
Issue(s)
Steps to test or reproduce
Further comments