Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.7.1.GA
-
Create a rule with the following condition:
We then add the "any of the following" after the first 2 conditions such as:
After realizing that the "any of the following" should have been selected BEFORE the other null checks, we move it 2 levels up using the yellow arrow, which leads to the following:
At this point, the rule looks fine, but if we look at the corresponding DRL, the OR is not added:
If we had selected the "any of the following" statement BEFORE the other 2 checks, the DRL looks like the following:
So, it seems like moving the "any of the following" statement is ignored when moving it up and thus is not replacing the AND with an OR.
If the replacement is not possible, then moving up this Multiple Field Constraint should not be possible.
Create a rule with the following condition: We then add the "any of the following" after the first 2 conditions such as: After realizing that the "any of the following" should have been selected BEFORE the other null checks, we move it 2 levels up using the yellow arrow, which leads to the following: At this point, the rule looks fine, but if we look at the corresponding DRL, the OR is not added: If we had selected the "any of the following" statement BEFORE the other 2 checks, the DRL looks like the following: So, it seems like moving the "any of the following" statement is ignored when moving it up and thus is not replacing the AND with an OR. If the replacement is not possible, then moving up this Multiple Field Constraint should not be possible.
Description
When editing a guided rule, if the "any of the following" statement if selected in the condition and is moved up in the list of conditions, it is not correctly taken into account.
