[jira] [Comment Edited] (OFBIZ-7655) Use 'conditionFields' instead of 'andCondition' in Lookup screen

["Jacques Le Roux (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352829#comment-15352829 ] 

Jacques Le Roux edited comment on OFBIZ-7655 at 6/28/16 11:39 AM:
------------------------------------------------------------------

In this case, only one patch for all the screens is enough. Because the chanes are simple and similar, easy review and test, and less "paperwork".


was (Author: jacques.le.roux):
Only one patch for all the screens is enough

> Use 'conditionFields' instead of 'andCondition' in Lookup screen
> ----------------------------------------------------------------
>
>                 Key: OFBIZ-7655
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7655
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party, product
>    Affects Versions: Trunk
>            Reporter: Montalbano Florian
>            Priority: Minor
>              Labels: andCondition, autocompletion, conditionFields, lookup
>
> In order to improve a little the readibility, we can replace the use of direct call of groovy in Lookup screen for the autocompletion parameters. Instead, we can use the field 'conditionFields', which is a map key/value, to declare those parameters.
> This is a main task and a sub task will be created for each lookup involved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)