FR ADEMPIERE 72 Improvements in VLookup and Info Windows

From ADempiere
Revision as of 04:57, 7 April 2012 by MJMcKay (Talk)

Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.

{Note|This page is incomplete} Feature Request: https://adempiere.atlassian.net/browse/ADEMPIERE-72

Introduction

While the VLookup fields and info windows function, there are many inconsistencies in how they operate. This improvement will attempt to solve some of these inconsistencies and make the swing and ZK behave in an identical fashion.

The inconsistencies include the following:

  • The VLookup fields that cause info windows to open use searches that are different than those performed by the info windows. For example, in GardenWorld, in a Product field on a sales order, entering %Tree will open an info window with only one entry for a Plum Tree. If there is only one entry, the Product field (a VLookup) should have selected that record. Having the info window open with only one gives the user the impression that that is only "Tree" in the product list. In the database there are three entries that match the query performed by the VLookup.
  • If the VLookup field has a record defined and there are more than one identifier column set in the underlying table (in other words, the field displays something like Value_Name), the info window opened when the search button is pressed will not find the record.
  • If the info window is opened from a menu, clicking return will close it unespectedly.
  • Although the table of search results are read-only, every cell in the table is selectable.
  • Multi Selection is difficult to use for selected more than a few rows. Keyboard navigation is difficult and each row must be selected by mouse click.

Changes will include:

  • direct link via the record ID for fields that already have record information saved. The info windows will now be able to display details about that record without any ambiguity in how the record ID is displayed. With this link, the info buttons can remain active on fields where the document is closed and the field.
  • the info windows will be more responsive to and selective of the context in which they were opened and will gather search criteria in an intelligent fashion.
  • an info entry will be added to the popup menu for certain VLookup fields that do not have a search button.
  • A system configuration entry will allow the user to select the default wild card positions as none, beginning, end or both. The default will be end.
  • A system configuration entry will allow the user to set the default behavior to auto query on changes to search criteria. A check box will be added to the info panel to allow the user to override the system config. The default is to not auto query if the system config setting isn't specified.
  • In the info windows, VLookup fields will replace text search fields where this makes sense.
  • zoom capabilities will be added where these don't exist.
  • Where the current info window queries result in multiple lines for each ID, the queries will be simplified to return single results by either, dynamically removing columns from the table where these columns cause the duplication, or by moving the information to a pane below the table. This will mostly affect the Info Product and Info BPartner windows. The Info Product window will have dynamic columns for warehouse quantities which will appear only when a warehouse is selected. Similarly, the price information will only appear if a price list is selected. For the Info BPartner window, the contact and location information will be moved to a pane below the main table.
  • For the Info Product window the following will be added:
    • A check box to select only stocked items
    • A search field for product categories
    • The PAttributeSetInstance button will be changed to a VPattributeSetInstance field so that the ASI criteria can be seen. This will allow products to be searched by attribute.

The changes will be generated in two stages - Swing first and then ZK.


=== Overview ===


==== Purpose ====

 
==== Scope ====


==== References ====


=== Design Considerations ===


==== Assumptions ====


==== Dependencies ====


==== Constraints ====


=== Glossary ===


=== Functional Requirements ===


==== User roles & profiles ====


==== Business process definition ====


==== User stories ====


==== Functional requirements based on business processes ====


==== User Interface Mockups ====


=== Technical Requirements ===


=== Non-Functional Requirements ===


=== Open Discussion Items ===


=== Closed Discussion Items ===




=== Overview ===


==== Purpose ====

 
==== Scope ====


==== References ====


=== Design Considerations ===


==== Assumptions ====


==== Dependencies ====


==== Constraints ====


=== Glossary ===


=== Functional Requirements ===


==== User roles & profiles ====


==== Business process definition ====


==== User stories ====


==== Functional requirements based on business processes ====


==== User Interface Mockups ====


=== Technical Requirements ===


=== Non-Functional Requirements ===


=== Open Discussion Items ===


=== Closed Discussion Items ===


[[Category:Functional_Specification]]
[[Category:Branch_GlobalQSS_361]]