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

Link subflows to their parents and give them more meaningful names #41

Open
NTPape opened this issue Jul 21, 2016 · 0 comments
Open

Link subflows to their parents and give them more meaningful names #41

NTPape opened this issue Jul 21, 2016 · 0 comments

Comments

@NTPape
Copy link
Collaborator

NTPape commented Jul 21, 2016

Currently it's almost impossible to find certain subflows in the overview because their name is just a random UUID. The only thing to go for right now is the processor IDs where the data went through which are only available when logging is set to 'all'.

It would be great if they were linked somehow to their parent flows and also have meaningful names, which could for example include the ID of the processor which kicked them off.

Maybe we could also store the used replacements per subflow in the Monitor as well.

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

No branches or pull requests

1 participant