[jboss-jira] [JBoss JIRA] (DROOLS-5022) Highlight better that expression and graphical collection editor are different

[ https://issues.redhat.com/browse/DROOLS-5022?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-5022: -------------------------------------- Tester: Jozef Marko Description: Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. Suggested solution: - to explain the difference directly in the popup, somewhere close to radio buttons create/define. Note - How it works now: Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" What expression should be to make test pass: (2 in ?) was: Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. Suggested solution: - to explain the difference directly in the popup, somewhere close to radio buttons create/define. Example: [1] !Screenshot from 2020-01-17 13-56-02.png|thumbnail! [2] !Screenshot from 2020-01-17 13-56-10.png|thumbnail! How that works now: Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" What expression should be to make test pass: (2 in ?) Story Points: (was: 2) Labels: UX drools-tools (was: UX UXTeam drools-tools) Affects: Documentation (Ref Guide, User Guide, etc.) -- This message was sent by Atlassian Jira (v7.13.8#713008)