Genesys Cloud - Developer Community!

 

 

 

 

 

 

 

 

 

 

 

 

 

 

#EmbeddableFramework

------------------------------
Katsuya Watabe
------------------------------

Hi Katsuya,

I haven't implemented this exact scenario myself, but from what I found, it does not look like custom participant attributes can be added directly inside the Interaction.updateState transfer call.

The likely approach would be:

1. Update the participant data/attributes on the active interaction first via API
2. Wait for that update to complete
3. Then trigger the blindTransfer / consultTransfer

This thread looks relevant for updating participant data via API:

https://community.genesys.com/discussion/manually-add-participant-data-to-an-active-interaction-via-the-api

Also worth noting that participant data updates may propagate asynchronously, so timing could matter before triggering the transfer:

https://community.genesys.com/discussion/participant-data-updates-via-the-api-performance-guarantee

Hopefully someone from the community or Genesys can add more or confirm the intended approach.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Original Message:
Sent: 04-26-2026 00:08
From: Katsuya Watabe
Subject: Is it possible to set participant attributes during blind/consult transfer via Interaction.updateState?

Hi,

 

I am implementing a CRM integration using the Genesys Cloud Embeddable Framework (Web softphone).

 

In framework.js, I have enabled customInteractionAttributes and allowed a custom attribute:

 

customInteractionAttributes: [

  "PT_TransferContext"

]

 

Using PureCloud.Interaction.updateState with action "blindTransfer" or "consultTransfer",

the transfer itself works correctly.

 

What I am trying to achieve is:

- At transfer time, set a participant attribute (e.g. PT_TransferContext)

- Have that value available on the receiving agent side via the screenPop event

 

Observations so far:

 

1. Interaction.updateState

   - blindTransfer / consultTransfer only support participantContext

     (transferTarget / transferTargetType)

   - There does not appear to be a way to attach participant attributes here

 

2. PureCloud.addTransferContext

   - Seems to work only when the Transfer window is open

   - If the Transfer Workspace checkbox is not selected, attributes are not propagated

   - There does not appear to be a way to:

     - open the Transfer window programmatically

     - force-enable the Transfer Workspace checkbox

 

3. In a UI-based test:

   - When the Transfer window is manually opened

   - and addTransferContext is called while it is open

   - attributes are propagated correctly and appear in screenPop

   - but without the UI, the same call has no effect

 

Given this behavior, my question is:

 

Is there any supported way to set participant attributes that appear in screenPop

when executing blindTransfer / consultTransfer via Interaction.updateState,

without relying on the Transfer UI?

 

If not, is this behavior intentional by design?

 

Any clarification on the recommended or intended approach would be appreciated.

 

Thanks.

#EmbeddableFramework

------------------------------
Katsuya Watabe
------------------------------