You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wondering why the ResolveConversation does not have conversationID as Output Variable (which is then hardcoded inside Queue Task). Same for Queue Task: Why it does not have a queueID as Output Variable while it is hardcoded in the PIQ and EWT node as $(queue).
We noticed the same in previous Flow release (before ResolveConversation). conversationID is used in some nodes but it is properly filled only by CreateConversation. Egain, this is not logic.
Key variables should be visible as Node output, and not as hardcoded names. Not doing this is going to break one of the key/nice features of Webex Connect flow builder, where each node is feeding the next in the chain.
This could also take to issues in the future: If someone change by mistake the Node config, there is no reference to the original variable used.
Thank you
The text was updated successfully, but these errors were encountered:
Hello
wondering why the ResolveConversation does not have conversationID as Output Variable (which is then hardcoded inside Queue Task). Same for Queue Task: Why it does not have a queueID as Output Variable while it is hardcoded in the PIQ and EWT node as $(queue).
We noticed the same in previous Flow release (before ResolveConversation). conversationID is used in some nodes but it is properly filled only by CreateConversation. Egain, this is not logic.
Key variables should be visible as Node output, and not as hardcoded names. Not doing this is going to break one of the key/nice features of Webex Connect flow builder, where each node is feeding the next in the chain.
This could also take to issues in the future: If someone change by mistake the Node config, there is no reference to the original variable used.
Thank you
The text was updated successfully, but these errors were encountered: