rhuss
commented
7 years ago Latest UX design:
Closed jimmidyson closed 6 years ago
rhuss
commented
7 years ago Latest UX design:
rhuss
commented
7 years ago See also the design proposal at https://github.com/syndesisio/syndesis-project/blob/master/design-proposals/002-filter-data.md
kahboom
commented
7 years ago Ty Roland, submitting a PR for review today.
On Tue, Jun 27, 2017 at 3:23 AM Roland Huß notifications@github.com wrote:
See also the design proposal at https://github.com/syndesisio/syndesis-project/blob/master/design-proposals/002-filter-data.md
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis-project/issues/2#issuecomment-311275273, or mute the thread https://github.com/notifications/unsubscribe-auth/ADqplriWcGdveD6vw4kdhQ5LGcN32Na3ks5sIK3mgaJpZM4NrW_R .
-- Regards,
Rachel Yordán Senior Software Engineer Red Hat, Inc. | Middleware ryordan@redhat.com
rhuss
commented
7 years ago It's grooming Tuesday :) : what is the state of this story ? What needs still to be done ?
@iocanel @kahboom A short summary of the current state of the filtering story would be awesome (plus a list of missing tasks / blocker / etc.)
kahboom
commented
7 years ago Apologies for this, will update the WIP PR this morning now that I won't be traveling until next month. :)
@iocanel Is the API part ready? If not I'll just finish up the UI part today, whatever is missing for it.
iocanel
commented
7 years ago The api part is ready, but the pull request is pending review!
On Tue, Jul 11, 2017 at 2:11 PM, Rachel Yordán notifications@github.com wrote:
Apologies for this, will update the WIP PR this morning now that I won't be traveling until next month. :)
@iocanel Is the API part ready? If not I'll just finish up the UI part today, whatever is missing for it.
On Tue, Jul 11, 2017 at 4:24 AM Roland Huß notifications@github.com wrote:
It's grooming Tuesday :) : what is the state of this story ? What needs still to be done ?
@iocanel https://github.com/iocanel @kahboom https://github.com/kahboom A short summary of the current state of the filtering story would be awesome (plus a list of missing tasks / blocker / etc.)
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis-project/issues/2#issuecomment- 314371108, or mute the thread https://github.com/notifications/unsubscribe- auth/ADqplpqNcjyKOoWgvlyPw_5JBjAV3CMfks5sMzEkgaJpZM4NrW_R .
-- Regards,
Rachel Yordán Senior Software Engineer Red Hat, Inc. | Middleware ryordan@redhat.com
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis-project/issues/2#issuecomment-314411696, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYiWMyoJh1gffmkAcJO4jEBPWi-otvEks5sM1hxgaJpZM4NrW_R .
-- Ioannis Canellos
Blog: http://iocanel.blogspot.com http://iocanel.blogspot.com/ Twitter: iocanel
kahboom
commented
7 years ago Thanks @iocanel !
kahboom
commented
7 years ago @rhuss - Created the issue for the REST repository like we discussed yesterday here: https://github.com/syndesisio/syndesis-rest/issues/428
As a citizen user, I would like to restrict the data that flows through an integration to match a specific set of criteria. For example, I may have an integration that is triggered every time a tweet mentions my account, but I only want to process tweets that contain the text "Syndesis".
When adding a filter, I want to be able to specify three things:
When specifying the target, I want the iPaaS to provide a sensible default without requiring any data input (e.g. Twitter connection would set default to Status.Text). If I'm not interested in the default, I will type the field name into the input box for target, but I would appreciate text completion based on the known set of data fields. Finally, an option to have a visual list of available fields and choosing one by clicking on it would be great.
When specifying the operation, I want the following options:
The data used for filter value should be completely open-ended. A single line should be sufficient as more advanced filters should really use the expert view.
I should be able to specify multiple filter expressions in a single step. Each filter expression should appear on its own line. Evaluation of multiple filter expressions are either all AND or all OR, never a mix of AND/OR.