[OFBIZ-7655] Use 'conditionFields' instead of 'andCondition' in Lookup screen

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Trunk
• Fix Version/s: 16.11.01
• Component/s: party, product
• Labels: andCondition autocompletion conditionFields lookup
• Assignee: Nicolas Malin
• Reporter: Montalbano Florian
• Created: 28/Jun/16 08:17
• Updated: 28/Jun/16 16:15
• Resolved: 28/Jun/16 16:15

Description

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.

Issue Links

• incorporates: OFBIZ-7576 auto-completer does not work to search Contact Party Id

Sub-Tasks

• Use 'conditionField' in LookupCustomerName: Closed
• Use 'conditionFields' in LookupContact: Closed
• Use 'conditionFields' in LookupInternalOrganization: Closed
• Use 'conditionFields' in LookupVirtualProduct: Closed