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.

Sign up for GitHub

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

Jump to bottom

[Conditional flow] Collection input data shape handling #6159

Closed
mcada opened this issue Jul 15, 2019 · 1 comment
Closed

[Conditional flow] Collection input data shape handling #6159

mcada opened this issue Jul 15, 2019 · 1 comment
Labels
cat/enhancement Enhancements to existing features and capabilities closed/migrated notif/triage The issue needs triage. Applied automatically to all new issues. prio/p2 The priority of a bug. p1 means low source/qe Raised by QE

Comments

@mcada
Copy link
Contributor

mcada commented Jul 15, 2019 •
edited by heiko-braun

See also https://issues.jboss.org/browse/ENTESB-11461

This is a...


[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

Description

I can not add conditional flow if previous input data shape is a collection.

To create integration database -> split -> conditional flow I have to first create database -> log then add split, delete log and add conditional flow. We could automatically add split step in case of adding conditional flow after collection output data shape.

One of conditional flow feature requirements was that we can add this step anywhere. This is not true atm - we can not add it after a collection unless we first add split step.
@mcada mcada added prio/p2 The priority of a bug. p1 means low cat/enhancement Enhancements to existing features and capabilities labels Jul 15, 2019
@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Jul 15, 2019
@mcada mcada added the source/qe Raised by QE label Jul 15, 2019
@heiko-braun
Copy link
Collaborator

Migrated to https://issues.jboss.org/browse/ENTESB-11461

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cat/enhancement Enhancements to existing features and capabilities closed/migrated notif/triage The issue needs triage. Applied automatically to all new issues. prio/p2 The priority of a bug. p1 means low source/qe Raised by QE
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@heiko-braun @mcada