I have a logic when starting the flow get the name of customer from attribute and assign it to a variable.
It works well but when I change the name to empty at the second time, that attribute keeps the old value, it's not updated to empty.
attribute "name" is "abc" => the name variable is "abc" - OK
change "name" to empty and send a message to Genesys => attribute "name" is still "abc" and the name variable is still "abc" - NOT OK
=> I expect it should empty in attribute and variable value
Could you tell me what you are looking to achieve when updating the "name" attribute to empty? Where are you surfacing/referencing "name" after this initial step of the flow?
Firstly, the "name" attribute was defined and it works fine, after that I go to the End of Flow.
Then I change the "name" attribute in the send message to empty. when the message goes to Inbound message flow the second time, the "name" attribute still keeps the old value from the first time.
Hmm, updating to empty should be allowed and reflected upon re-entering the flow. Would you mind opening a Care ticket with the full details of your use case and flow configuration?
I just did a quick test and it seems that custom attributes set to an empty string value are ignored on Genesys Cloud side (even if they are sent properly from Messenger, over Web messaging Guest API) .
Genesys Cloud does not seem to add or to update the attribute value, in the conversation's participant attributes, when its value is an empty string.