Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why new templates still use hardcoded variable? #19

Open
mpirrone opened this issue Apr 11, 2023 · 0 comments
Open

Why new templates still use hardcoded variable? #19

mpirrone opened this issue Apr 11, 2023 · 0 comments

Comments

@mpirrone
Copy link

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
Screenshot 2023-04-11 at 11 46 14
Screenshot 2023-04-11 at 11 47 44
Screenshot 2023-04-11 at 11 47 58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant