fix(contact-center): fix bugs listed in CAI-6468#458
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughThe changes introduce enhancements and refactoring across several packages in the contact center application. In the UI, a tooltip is added to the user state selector by wrapping it in a Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
mkesavan13
left a comment
There was a problem hiding this comment.
Could you please add a vidcast by showing the fixes using the PR preview app?
I have added the vidcast link the PR description. |
sreenara
left a comment
There was a problem hiding this comment.
- What was the issue that was causing the state to go to available when you ended a task? It took a few attempts and then got it working.
- Have you tested all of the fixes and controls with only keyboard for accessibility purposes?
- Question about the behavior of the state widget. When we end a call task, why is the state staying in Engaged? An agent should always be able to receive another call right? The digital task should not be blocking another incoming call from coming in?
|
| selectedKey={selectedKey} | ||
| items={sortedItems} | ||
| className={`state-select ${getDropdownClass()}`} | ||
| <TooltipNext |
There was a problem hiding this comment.
Just a question about TooltipNext. How different is this from ToggleTip in the new momentum repo? Are we able to select this tooltip with the keyboard?
There was a problem hiding this comment.
New momentum design tooltip works better with the a11y so, removed the MRV2 and used the new one.
# [1.28.0-ccwidgets.60](v1.28.0-ccwidgets.59...v1.28.0-ccwidgets.60) (2025-05-23) ### Bug Fixes * **contact-center:** fix bugs listed in CAI-6468 ([#458](#458)) ([0873b44](0873b44))
|
🎉 This PR is included in version 1.28.0-ccwidgets.60 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
COMPLETES #< CAI-6468 >
This pull request addresses
There were various bugs which needed to be fixed for the
user-state. List of the issues are shown below[For all of the above, the fix is ideally to prioritize Custom State over the Agent desktop state changes and clear it on Wrapup]
by making the following changes
Updated the code mainly for the following files to fix the above issues
packages/contact-center/cc-components/src/components/UserState/user-state.tsxpackages/contact-center/store/src/storeEventsWrapper.tspackages/contact-center/task/src/helper.tsVidcast - https://app.vidcast.io/share/010ae2cc-1dc4-4b1d-b668-ac42350e9ff3?playerMode=vidcast
RONA Timer - https://app.vidcast.io/share/7a62d0a6-ddb2-469d-8e56-f52ab3519963
Tooltip improvement - https://app.vidcast.io/share/d03463a5-e6be-4995-bb9e-a67ec0695fe3
Change Type
The following scenarios were tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
All the scenarios mentioned in the description were tested.
The GAI Coding Policy And Copyright Annotation Best Practices
Checklist before merging