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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux closed OFBIZ-7655.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Upcoming Branch

Thanks All,

Completed: At revision: 1750543  

I found 2 remaining occurrences, this fixes them in one shoot, as I suggested

> 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
>            Assignee: Nicolas Malin
>            Priority: Minor
>              Labels: andCondition, autocompletion, conditionFields, lookup
>             Fix For: Upcoming Branch
>
>
> 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)