[
https://issues.apache.org/jira/browse/OFBIZ-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706645#action_12706645
]
Scott Gray commented on OFBIZ-863:
----------------------------------
ModelForm currently handles use-when fields by evaluating the use-when
expressions in reverse order and rendering the first one that evaluates to
true. This follows the pattern of regular duplicate fields where the last one
defined is that one that gets rendered.
Since a field without a use-when is basically just a use-when that always
evaluates to true, I believe the bug is simply that fields without a use-when
aren't taken into account when evaluating which use-when field to render. That
is the issue I intend on fixing today, if anyone sees a problem with that
please let me know.
> A form cannot override a parent form's field if the field contains the
> useWhen attribute
> ----------------------------------------------------------------------------------------
>
> Key: OFBIZ-863
> URL: https://issues.apache.org/jira/browse/OFBIZ-863
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Scott Gray
> Assignee: Scott Gray
> Priority: Minor
>
> When a form definition extends another form it is unable to override a parent
> field if that field contains a useWhen condition. So when the parent field's
> useWhen condition is true, both the child and parent field end up in the
> generated form.
> For an example of the problem see
> https://issues.apache.org/jira/browse/OFBIZ-753
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
