Currently conditions are applied using “AND“ logic. This means users have to meet all conditions to be allocated to a cohort the rule is linked to.
Would be nice to be flexible and be able to configure a rule using OR / AND operator per rule.
Ideally to be fully flexible we should be able to configure it's per condition like Condition 1 AND (Condition 2 OR Condition 3). But this will be another level of complexity.
Doing it per rule should be pretty straight forward.
Rough tasks:
[x] new DB field for tool_dynamic_cohorts
[x] form processing
[x] changing logic for condition_manager::build_sql_data
Currently conditions are applied using “AND“ logic. This means users have to meet all conditions to be allocated to a cohort the rule is linked to.
Would be nice to be flexible and be able to configure a rule using OR / AND operator per rule.
Ideally to be fully flexible we should be able to configure it's per condition like Condition 1 AND (Condition 2 OR Condition 3). But this will be another level of complexity.
Doing it per rule should be pretty straight forward.
Rough tasks: