Review this screenshot:
This was adding a nested criteria to the entry event. Note occurrences has [Object] Object in the UI, and clicking on 'add attribute' does nothing.
When looking at how an inclusion rule works:
An inclusion rule works exactly the same as a nested criteria: An inclusion rule starts with 'having any/all of the follwwing [Group] and you can add the 'count query' types of elements to it (which consists of a criteria expression surrounded by a correlated query of 'having {count} of {criteria} between {time window relative to index}'.
However, it looks like the nested criteria (described above having some bugs) and the inclusion rule rendering are distinct things. But they are not. Inclusion rules are the same thing as the nested criteria (which is the GroupCriteriaUI) so there should only be 1 component that provides the UI for group criteria editing, and it should be used in both the Inclusion rule and the Nested Criteria case.
Review this screenshot:
This was adding a nested criteria to the entry event. Note occurrences has [Object] Object in the UI, and clicking on 'add attribute' does nothing.
When looking at how an inclusion rule works:
An inclusion rule works exactly the same as a nested criteria: An inclusion rule starts with 'having any/all of the follwwing [Group] and you can add the 'count query' types of elements to it (which consists of a criteria expression surrounded by a correlated query of 'having {count} of {criteria} between {time window relative to index}'.
However, it looks like the nested criteria (described above having some bugs) and the inclusion rule rendering are distinct things. But they are not. Inclusion rules are the same thing as the nested criteria (which is the GroupCriteriaUI) so there should only be 1 component that provides the UI for group criteria editing, and it should be used in both the Inclusion rule and the Nested Criteria case.