Skip to content

Conversation

@rsarika
Copy link
Contributor

@rsarika rsarika commented Oct 9, 2025

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7183

This pull request addresses

Implemented the Multi-Party Conference feature supporting more than three participants, along with the Conference Transfer functionality.

Conference Transfer Behavior:

An agent can initiate a transfer only during a consultation.

Scenario 1: If Agent A1 and Agent A2 are on a consultation while the customer is on hold, upon transfer, A1 leaves and A2 takes ownership of the call.

Scenario 2: If Agent A1 and Agent A3 are on a consultation while the customer and Agent A2 are already in the main conference, upon transfer, A1 leaves, A2 becomes the new owner, and A3 joins the main conference with A2 and the customer.

by making the following changes

Added new buttons for Conference and Exit Conference and added handling of those buttons

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link
    < ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document

@rsarika rsarika added the validated Indicates that the PR is ready for actions label Oct 14, 2025
@rsarika rsarika changed the title feat: multi conference feat(cc-widgets): multi party conference Oct 14, 2025
@rsarika rsarika added validated Indicates that the PR is ready for actions and removed validated Indicates that the PR is ready for actions labels Oct 14, 2025
@aws-amplify-us-east-2
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-539.d1b38q61t1z947.amplifyapp.com

@rsarika rsarika added the run_e2e Add this label to run E2E test for meeting and CC widgets label Oct 27, 2025
Copy link
Contributor

@adhmenon adhmenon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have not reviewed tests but core code is looking good. Flows are all fine.
Have few doubts - but other than that, let us test once more and then the PR should be alright.

Copy link
Contributor

@rarajes2 rarajes2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have done first round of review, will require multiple rounds of review as the changes are big.

onDialNumberSelect: ((dialNumber: string, allowParticipantsToInteract: boolean) => void) | undefined,
onEntryPointSelect:
| ((entryPointId: string, entryPointName: string, allowParticipantsToInteract: boolean) => void)
| undefined
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the ? with variable instead of defining type undefined like this. Applicable everywhere

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@rsarika rsarika requested a review from rarajes2 November 6, 2025 05:21
@rsarika rsarika dismissed Shreyas281299’s stale review November 6, 2025 05:26

as rajesh and adhwaith reviewing this now.

Copy link
Contributor

@rarajes2 rarajes2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few minor comments, rest looks good to me. We should create a ticket for corner cases that we are going to handle in next ticket.

Please address last few comments and create JIRA before merging the PR.

@rsarika rsarika merged commit f2a23d4 into webex:ccwidgets Nov 11, 2025
8 checks passed
github-actions bot pushed a commit that referenced this pull request Nov 11, 2025
# [1.28.0-ccwidgets.123](v1.28.0-ccwidgets.122...v1.28.0-ccwidgets.123) (2025-11-11)

### Features

* **cc-widgets:** multi party conference ([#539](#539)) ([f2a23d4](f2a23d4))
@mkesavan13
Copy link
Contributor

🎉 This PR is included in version 1.28.0-ccwidgets.123 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @ccwidgets validated Indicates that the PR is ready for actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants