Set Participant Data with NOT_SET

[Adrian_Santamaria]

Hello

I've seen that setting a participant data with a NOT_SET value has different behavior depending on the flow type.

For example, in Inbound Call Flows, the attribute is not set at all (which makes sense, to me):

However, in Inbound Message Flows, it sets them as empty strings:

I do not know why this happens, but we have discovered it the hard way, when a logic that had always worked in inbound call flows started to give errors in message flows....

[Adrian_Santamaria]

Have you been able to take a look at this?

[Kevin_Walsh]

Hi Adrian,

I think either is considered valid, given that Architect has a "IsNotSetOrEmpty" Function.

Regards,

Kevin

[Adrian_Santamaria]

Still, a null value is different than an empty string. There can be cases where that difference could matter. Also, having different behaviors in voice and text flows is highly inconsistent, making things less reusable.