[jira] Assigned: (OFBIZ-1134) Inconsistent treatment of null search parameters

["Jacopo Cappellato (JIRA)" <ji...@apache.org>]

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

Jacopo Cappellato reassigned OFBIZ-1134:
----------------------------------------

    Assignee: Jacopo Cappellato

> Inconsistent treatment of null search parameters
> ------------------------------------------------
>
>                 Key: OFBIZ-1134
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1134
>             Project: OFBiz
>          Issue Type: Bug
>          Components: order
>    Affects Versions: SVN trunk
>            Reporter: Iain Fogg
>            Assignee: Jacopo Cappellato
>             Fix For: SVN trunk
>
>
> Prelude:
> To easily observe this problem, you need to modify a form definition. In applications/order/webapp/ordermgr/requirement/RequirementForms.xml to allow the facilityId field to accept an empty value by changing <drop-down allow-empty="true">.
> Assumption:
> + Your list of approved requirements include some with and without a value for facilityId.
> Scenario:
> + In the OrderMgr application, go to the "Requirements" screen and select "Approved Product Requirements".
> + By default, the Supplier field will be empty, and the form displays all requirements for all suppliers, irrespective of facilityId.
> + Select a Supplier (preferrably one with some requirements with a facilityId and some without), leave the facilityId empty, do the lookup, and the result is an empty list. Select a valid facilityId, do the lookup, and it returns the list of requirements for than supplier that have the relevant facilityId.
> + Clear the facilityId AND the Supplier, do the lookup, and you get the full list of approved requirements.
> For some reason, the application correctly interprets an empty facilityId as DON'T CARE when there Supplier is empty, but is doing something else when a Supplier is selected.
> Note: I observe this problem because I am testing on a snapshot of a production database that include requirements that may or may not have the facilityId field populated. In fact, the reason I have lots of requirements without a facilityId is because these are being generated by the Requirement Method Enum related secas. (Not sure if that is important but thought I'd mention it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.