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

ASF subversion and git services commented on OFBIZ-11418:
---------------------------------------------------------

Commit 08a371d0471a506e663c879f30299f424fc70921 in ofbiz-framework's branch 
refs/heads/trunk from Daniel Watford
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=08a371d ]

Improved: Use FlexibleStringExpander in form widget lookup field field
target parameters

(OFBIZ-11418)

Changed target-parameter attribute of the form widget's Lookup field to
use the FlexibleStringExpander type rather than String. This has been
done to allow reference to other form fields which may have had their
parameter-name attribute set to a FlexibleStringExpander expression.


> Use FlexibleStringExpander in form widget lookup field field target parameters
> ------------------------------------------------------------------------------
>
>                 Key: OFBIZ-11418
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11418
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Daniel Watford
>            Assignee: Jacques Le Roux
>            Priority: Major
>              Labels: patch-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> OFBIZ-11330 added use of FlexibleStringExpander when generating the 
> parameter-name for a Form Widget Field.
> The form widget's Lookup field makes use of a target-parameter attribute to 
> determine the input fields which should be read from when making a lookup 
> request.
> Since we can now generate field parameter names from FlexibleStringExpander 
> expressions it seems appropriate to be able to populate the target-parameter 
> with the same expressions. Not doing so means that we can potentially 
> generate parameter names that cannot be referenced by a lookup field.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to