feat(cc-widgets): added-address-book #537

adhmenon · 2025-10-03T13:34:33Z

COMPLETES #< CAI-7147 >

This pull request addresses

Adds addresbook changes in widgets
Also adds entry point list changes with consult-transfer flows
Removes older dial number flow code

by making the following changes

Added code for addressbook changes by updating consult transfer popover and store
NOTE PR is a draft as E2E tests and some snapshot tests still need to be fixed.

Vidcast - https://app.vidcast.io/share/2f481e6b-227a-4652-92e9-0f228b48ca03

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

Received call and tried to consult-transfer via queue, agent, dial number and entrypoint
Reloaed the popover multiple times and tried to cancel consult and end consult
Tried blind transfer for above cases as well

The GAI Coding Policy And Copyright Annotation Best Practices

Checklist before merging

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

aws-amplify-us-east-2 · 2025-10-03T13:41:22Z

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

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

cmullenx

you will need to add props to show/hide consult/transfer to address book and show/hide transfer to entry point based on feature flags that you will receive from our app.

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

packages/contact-center/cc-components/src/components/task/CallControl/call-control.styles.scss

packages/contact-center/cc-components/src/components/task/task.types.ts

...-components/tests/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

packages/contact-center/store/src/storeEventsWrapper.ts

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

feat(cc-widgets): added-basic-playwright-for-address-book

...cc-components/src/components/task/CallControl/CallControlCustom/call-control-custom.utils.ts

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts

rarajes2 · 2025-10-13T08:53:08Z

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts

+          apiParams.search = search;
+        }
+
+        logger?.info(`CC-Components: Loading ${categoryName} - page: ${currentPage}, search: "${search}"`);


Is logger optional? If not, we can remove the null check from here. Applicable everywhere

We can add the context containing the file and method name in the same way we have at all the places. Applicable everywhere

In this case, we want logger to be optional as users need not specify a logger when they use our widgets or SDK...

I will make that change here.

I thought this is our logging which gets uploaded to mats. If that's the case, we can't have this optional. Correct me if I am wrong

I think the rationale behind this was since we use these components in our tests (both unit and e2e) - sometimes we don't provide the logger, hence it was made optional...
Again, I am alright changing it to compulsory but that not sure how it would affect tests.
Perhaps we can discuss this with Shreyas also.

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

packages/contact-center/store/src/storeEventsWrapper.ts

rarajes2 · 2025-10-13T09:17:43Z

packages/contact-center/store/src/storeEventsWrapper.ts

+  getEntryPoints = async (params?: EntryPointSearchParams): Promise<EntryPointListResponse> => {
+    try {
+      const response: EntryPointListResponse = await this.store.cc.getEntryPoints(params);
+      return response;
+    } catch (error) {
+      console.error('Error fetching entry points:', error);
+      return Promise.reject(error);
+    }
+  };


Do we need to create this method? This is just one line logic

Yes, I feel so - we can catch any errors here in this method and it makes it uniform.
I feel we should retain this.

console.error('Error fetching entry points:', error); Please use the logger here and also add proper logging at the top and for the success as well

We can simply throw the error from the catch block instead of calling the promise.reject

Added here as well

rarajes2 · 2025-10-13T09:18:06Z

packages/contact-center/store/src/storeEventsWrapper.ts

+  getAddressBookEntries = async (params?: AddressBookEntrySearchParams): Promise<AddressBookEntriesResponse> => {
+    try {
+      const response: AddressBookEntriesResponse = await this.store.cc.addressBook.getEntries(params ?? {});
+      return response;
+    } catch (error) {
+      console.error('Error fetching address book entries:', error);
+      return Promise.reject(error);
+    }
+  };


As mentioned above, I feel it makes sense to keep it as we cna do error handling and it is uniform.

Same here. Let's improve the logging and error throwing

Added here also.. not sure why it's not showing outdated.. code changes are there in the code tabs.

…ress-book

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts

rarajes2

LGTM

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

Shreyas281299 · 2025-10-15T05:13:30Z

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

+          {renderList(
+            queuesData.map((q) => ({id: q.id, name: q.name})),
+            (item) => handleQueueSelection(item.id, item.name, onQueueSelect, logger)
+          )}


Ideally we want to simplify this all we should see in presentational is

Suggested change

{renderList(

queuesData.map((q) => ({id: q.id, name: q.name})),

(item) => handleQueueSelection(item.id, item.name, onQueueSelect, logger)

)}

{renderList(queuesData)}

We can process the data in utils

As mentioned above - this convolutes things and adds extra complexity to this PR... perhaps we can look at it later on.

...cc-components/src/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

packages/contact-center/cc-components/src/components/task/CallControl/call-control.styles.scss

packages/contact-center/cc-components/src/components/task/task.types.ts

...-components/tests/components/task/CallControl/CallControlCustom/call-control-custom.util.tsx

...-components/tests/components/task/CallControl/CallControlCustom/consult-transfer-popover.tsx

packages/contact-center/cc-components/tests/components/task/CallControl/call-control.tsx

packages/contact-center/store/src/store.types.ts

packages/contact-center/store/tests/storeEventsWrapper.ts

packages/contact-center/task/src/helper.ts

packages/contact-center/task/src/task.types.ts

packages/contact-center/task/tests/helper.ts

packages/contact-center/test-fixtures/src/fixtures.ts

Shreyas281299

Looks good.

# [1.28.0-ccwidgets.118](v1.28.0-ccwidgets.117...v1.28.0-ccwidgets.118) (2025-10-15) ### Features * **cc-widgets:** added-address-book ([#537](#537)) ([0997d10](0997d10))

sreenara · 2025-10-15T14:50:42Z

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

feat(cc-wudgets): added-address-book

ed4d2df

adhmenon added the validated Indicates that the PR is ready for actions label Oct 3, 2025

adhmenon added 3 commits October 3, 2025 19:13

feat(cc-wudgets): added-snaps

976eec0

feat(cc-wudgets): adjusted-queues-method

0422294

feat(cc-wudgets): removed-whitespaces

7f17031

cmullenx reviewed Oct 4, 2025

View reviewed changes

adhmenon added 2 commits October 6, 2025 10:18

feat(cc-wudgets): added-consult-transfer-props

5c16926

feat(cc-wudgets): fixed-styles

975000a

adhmenon commented Oct 7, 2025

View reviewed changes

adhmenon and others added 4 commits October 7, 2025 18:56

feat(cc-widgets): added-basic-playwright-for-address-book

92a1f83

feat(cc-widgets): resolved-comments

87ea791

feat(cc-widgets): moved-hooks

7f3a283

Merge pull request #1 from adhmenon/address-book-playwright

4f1a670

feat(cc-widgets): added-basic-playwright-for-address-book

adhmenon marked this pull request as ready for review October 9, 2025 13:17

adhmenon added the run_e2e Add this label to run E2E test for meeting and CC widgets label Oct 9, 2025

feat(cc-widgets): fixed-styling

63b12ac

rarajes2 reviewed Oct 13, 2025

View reviewed changes

adhmenon added 2 commits October 13, 2025 15:25

feat(cc-widgets): resolved-comments

da59673

Merge branch 'ccwidgets' of https://github.com/webex/widgets into add…

cf5c6a6

…ress-book

adhmenon requested a review from rarajes2 October 13, 2025 10:00

adhmenon added 2 commits October 13, 2025 15:35

feat(cc-widgets): resolved-more-comments

c5b131c

feat(cc-widgets): removed-old-code

8865991

rarajes2 reviewed Oct 13, 2025

View reviewed changes

...mponents/src/components/task/CallControl/CallControlCustom/consult-transfer-popover-hooks.ts Outdated Show resolved Hide resolved

feat(cc-widgets): fixed-logging

f590dd8

adhmenon requested a review from rarajes2 October 14, 2025 04:32

rarajes2 approved these changes Oct 14, 2025

View reviewed changes