Cause:
Consequence:
Value fields using dependent enumerations for constraints in a Guided Rule are not updated when user switches the value it depends on.
Workaround (if any):
After switching the value depended upon, remove the last input element of the problematic constraint and re-add it.
Result:
For an enumeration like
'A.a' : ['a','b','c']
'A.b[a=b]' : ['b1','b2']
and rule containing
'There is an A with:
(field) a equal to (value) b
(field) b equal to (value) b1'
if user switches value of field a to a or c (and vice-versa), the input box for value for field b is disabled instead of correctly updated. This input box then must be removed and re-added to make it work again.
DescriptionZuzana Krejčová
2014-01-06 16:02:41 UTC
Created attachment 846155[details]
screenshot - disabled drop down instead of input field
Description of problem:
Enumeration is as follows:
'A.a' : ['a','b','c']
'A.b[a=b]' : ['b1','b2']
In the Guided rule editor, I first add the 'There is an A with:' condition, then add the 'a' field constraint with 'b' as the value, after that I add the 'b' field constraint and choose from the enum drop down.
If I change the 'a' constraint value, the drop down for 'b' constraint gets disabled instead of turning into an input field. It stays that way even if I change the first constraint value back to 'b'.
To get the correct input element (after changing first constraint value), you have to remove the disabled drop down and re-add it (Literal value).
When you start with value 'a' or 'c' for the a field constraint, you won't get the drop down box for field b constraint if you change to value 'b' either. The simple input field stays there.
Version-Release number of selected component (if applicable):
BPMS 6.0 ER7
Steps to Reproduce:
1. Create a POJO A with String fields a and b and the above mentioned enumeration.
2. Create a new guided rule, add a new condition - choose fact A.
3. Click the added line, choose restriction on field a, choose 'equal to' operator an Literal value.
4. Choose 'b' as the value.
5. Click the first line again, add restriction on field b, choose the same operator and Literal value again.
6. Choose a value for field b.
7. Change value for field a to 'c'.
Actual results:
Drop down box for field b is disabled, no value visible. Source shows the previously selected dependent value though.
Expected results:
Drop down box for field b changed into simple input field, user can type in the preferred value.
(I think there was a BZ for the same issue for 5.3 but couldn't find it. If anyone stumbles across that, please add a link.)
Created attachment 846155 [details] screenshot - disabled drop down instead of input field Description of problem: Enumeration is as follows: 'A.a' : ['a','b','c'] 'A.b[a=b]' : ['b1','b2'] In the Guided rule editor, I first add the 'There is an A with:' condition, then add the 'a' field constraint with 'b' as the value, after that I add the 'b' field constraint and choose from the enum drop down. If I change the 'a' constraint value, the drop down for 'b' constraint gets disabled instead of turning into an input field. It stays that way even if I change the first constraint value back to 'b'. To get the correct input element (after changing first constraint value), you have to remove the disabled drop down and re-add it (Literal value). When you start with value 'a' or 'c' for the a field constraint, you won't get the drop down box for field b constraint if you change to value 'b' either. The simple input field stays there. Version-Release number of selected component (if applicable): BPMS 6.0 ER7 Steps to Reproduce: 1. Create a POJO A with String fields a and b and the above mentioned enumeration. 2. Create a new guided rule, add a new condition - choose fact A. 3. Click the added line, choose restriction on field a, choose 'equal to' operator an Literal value. 4. Choose 'b' as the value. 5. Click the first line again, add restriction on field b, choose the same operator and Literal value again. 6. Choose a value for field b. 7. Change value for field a to 'c'. Actual results: Drop down box for field b is disabled, no value visible. Source shows the previously selected dependent value though. Expected results: Drop down box for field b changed into simple input field, user can type in the preferred value. (I think there was a BZ for the same issue for 5.3 but couldn't find it. If anyone stumbles across that, please add a link.)