Five9 updates for handling state updates on call completion & TimeView render interval#1586
Five9 updates for handling state updates on call completion & TimeView render interval#1586paulfalgout merged 2 commits intodevelopfrom
TimeView render interval#1586Conversation
📝 WalkthroughWalkthroughState updates in Five9 call lifecycle methods ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
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. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the Five9 integration to improve call state management and timer display accuracy. The changes ensure proper cleanup of call-related state when calls end and increase the timer update frequency for better real-time feedback.
Changes:
- Increased timer render interval from 60 seconds to 1 second for more accurate call duration display
- Consolidated multiple
setStatecalls into single object updates in call event handlers - Added explicit cleanup of
callTimeandisTransferredCallstate in thecallFinishedhandler
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| packages/care-ops-five9/five9_views.js | Reduced timer re-render interval from 60 seconds to 1 second for real-time display |
| packages/care-ops-five9/five9_app.js | Refactored state updates to use object syntax and added comprehensive state cleanup in callFinished |
Shortcut Story ID: [sc-65412]
These changes were confirmed to work in Upperline Sandbox.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.