[rules-users] Guvnor 5.5 bug - when the advanced enum feature is used, the selected value is not saved in special condition

Michael Anstis michael.anstis at gmail.com
Wed Sep 25 12:48:12 EDT 2013


Well fix in 6.x to be honest; so unless your repository is a git one the
JCR (for <=5.5) would be less helpful.

Just be sure to include details of the model, enum definitions and rules.

Thanks,


On 25 September 2013 17:25, Sean Su <sean.x.su at gmail.com> wrote:

> Do you need a guvnor repository to reproduce this or just some description
> of the issue? I think I can build a simple version of rules for the case.
>
> Sean
>
>
> On Tue, Sep 24, 2013 at 1:54 PM, Michael Anstis <michael.anstis at gmail.com>wrote:
>
>> Can you please raise a JIRA at https://issues.jboss.org/browse/GUVNOR
>>
>> Thanks
>>
>>
>> On 24 September 2013 18:29, Sean Su <sean.x.su at gmail.com> wrote:
>>
>>> Also just tested and confirmed that this is happening when I save the
>>> rule twice in the row - first save seems fine; do nothing and save the rule
>>> one more time, the selection in the last drop down is gone!
>>>
>>>
>>> On Tue, Sep 24, 2013 at 1:23 PM, Sean Su <sean.x.su at gmail.com> wrote:
>>>
>>>> When there are 3 drop downs, one determines the values of the other,
>>>> the selection in the last drop down is not saved when changing the rules
>>>> twice in the row.
>>>>
>>>> For example: I have the following statement:
>>>>
>>>> in fact [field1] [field2][field3]
>>>>
>>>> each of the field is presented as a drop down by using the advanced
>>>> ENUM feature - 1 determines the values in 2 and the selection of 2
>>>> determines the value of 3.
>>>>
>>>> After the value in field3 is selected, I can move on and make the
>>>> changes in the rule. When the first change occurred, Guvnor remembers the
>>>> values being selected in all 3 fields. But when another change is make, the
>>>> selected value in the last field (field3) will be forgotten. Please note
>>>> this is only happening to the last field. I did not go further and make the
>>>> statement contain more than 3 drop downs.
>>>>
>>>> I have tested this several times and am confident this is a bug in the
>>>> 5.5 final version.
>>>>
>>>> Thanks
>>>>
>>>> Sean
>>>>
>>>
>>>
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-users
>>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20130925/7eb0855c/attachment.html 


More information about the rules-users mailing list