EventBridge : Need explications about attributes and flow.end topics

Genesys Cloud Applications Architect
1

Hi,
We use an event bridge architecture and all events go to an aws sqs fifo. (all conversations topics)

In Architect : " Changes to participant data will not be available in the cloud until the flow ends."

So, we think, we would received one event from flow.end topic and after one event from attributes topic.
But, after some tests, we have received 4 attributes topics event (each with some key/value additional) and one flow.end topic event after.

It's seems not to fit the definition, can you give some information about this ?

2

Where exactly are you seeing this statement? That's not how participant attributes work as a general concept, but there may be a contextual caveat.

3

screen
screen1877×657 96 KB

4

That is explained in a little more detail here: Set Participant Data action - Genesys Cloud Resource Center

If Set Participant Data Action sets a participant attribute value during a call, then the value set is the value read on subsequent Get Participant Data action calls, even though the value set is not updated in the Cloud until flow termination. For example:

  1. If the flow issues a Get Participant Data action with “Foo” as the attribute name, the Cloud returns “Hello”, so that variable bound to “Foo” in the Get Participant Data action is set to “Hello”.
  2. The flow then issues a Set Participant Data action with “Foo” as the attribute name and “Goodbye” as the value.
  3. The flow then repeats issuing a Get Participant Data action with “Foo” as the attribute name, the Cloud returns “Hello” as before, since updates made via Set Participant Data are queued and only sent to the cloud just prior to termination. However in this case, the variable bound to “Foo” is set to “Goodbye” because Get Participant Data uses any queued-for-update values before it uses what the cloud returns.

The context of that statement is for attributes you set using the Set Participant Data action. Architect does some caching during execution for efficiency. Participant attributes may be updated by other things (i.e. other parts of the Genesys Cloud backend) during the flow, which will trigger updates at that time and not be subject to the caching of your set statements done internally within the flow.

5

Is the attribute name hardcoded values in the flow?
If the attribute name exceeds 20kb we are not storing that Particpant data?
Im asking this based on the IVR flow screenshot

6

You define your own participant attribute names. Please make a new post or reply in the other one if you have questions about the limits; let's not hijack someone else's post into a 3rd post about the same thing.

7

I understand this logic in the flow in genesys cloud, caching datas for efficiency.
But i don't understand why in AWS Bridge (outside GCX) we have all attributes modifications especially if it's caching objects in GCX

8

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.