You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2016/06/28 10:05:57 UTC
[jira] [Commented] (OFBIZ-7655) Use 'conditionFields' instead of
'andCondition' in Lookup screen
[ https://issues.apache.org/jira/browse/OFBIZ-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352725#comment-15352725 ]
Jacques Le Roux commented on OFBIZ-7655:
----------------------------------------
Florian, in simple cases like that you don't need to create subtasks, a simple patch would do it ;)
> 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)