[
https://issues.apache.org/jira/browse/OFBIZ-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525351#comment-14525351
]
Forrest Rae commented on OFBIZ-6323:
------------------------------------
This thing operates in two different modes. When you're adding an item to a
quote, if you type two characters in to the productId field of the search form,
a javascript event will fire that calls LookupProductPrice view with an
"ajaxLookup" set to true. This condition gets checked in the LookupDecorator,
and if true, calls back to the fail-widget, which decorates the response as
ajax. Now, if you click the little box to the right of the productId field,
you're presented with a full search form where you can select from the
different available critera, including the different productPriceType(s). I
hope that makes sense.
> LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than
> all the price types
> -------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-6323
> URL: https://issues.apache.org/jira/browse/OFBIZ-6323
> Project: OFBiz
> Issue Type: Bug
> Components: product
> Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk,
> 14.12.01
> Reporter: Forrest Rae
> Attachments: OFBIZ-6323.patch
>
>
> The LookUpProductPrice ajaxLookup leverages the same LookupDecorator screen
> that is used for more advanced product queries. The results of the request
> display all the different price types configured for a product This is
> confusing for the user when adding an item to a quote. The attached patch
> adds additional conditionalFields to the search criteria.
> I've searched the code base for areas where this change might adversely
> affect usability and didn't see any cases of that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
