Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015776 | Openbravo ERP | A. Platform | public | 2011-01-26 01:54 | 2022-02-01 08:08 |
| Reporter | johnfandl | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | pi | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0015776: Button to "Create Basic QueryList Widget" when on a "Detail Tab" | ||||
| Description | Querylist Widgets are great, but are a bit tedious to specify. They are most useful to see master/detail information from the perspective of an attribute at the detail level, e.g. "show me all Open PO Lines for a specific Product". | ||||
| Steps To Reproduce | It would be really great if the system would provide a button that would appear when any "detailed" level of a master/detail screen was selected. This button would be called "Create Basic Querylist Widget". This is not a generic query generator, it is much more basic--for use by someone who does not know about tables and joins. | ||||
| Proposed Solution | The Create Querylist Widget Button would by rendered for roles that have the authority to create a Widget. Pressing this button would: 1. Render a modal form with the fields of the current selected detailed tab, and all parent tabs on the screen 2. Allow the user to select the desired fields 3. Allow the user to optionally select one of the previously-selected fields for sorting (with choice of ascending or descending) 4. Require the user to enter a name for the Query list When the user presses the button to 'Create Querylist Widget', the system generates the HQL (with the necessary joins), and inserts the required rows to create the querylist widget. This is very simple, since we are not allowing any calculated expressions or anything else fancy. If the user wants to get a developer to modify the generated querylist after the fact (to add a where clause, calculated expressions, additional joins, etc.), that is fine. The point is to empower end users with a way to simply point at data that they want to see "query widgetized", and the detailed screens are the perfect place from which to do that--since that is where you are saying to yourself "If only I could see ALL of the detailed rows across the headers for a certain product or business partner or user, or whatever." This feature would really put power into the end user hands. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-01-26 01:54 | johnfandl | New Issue | |||
| 2011-01-26 01:54 | johnfandl | Assigned To | => alostale | ||
| 2011-01-26 01:54 | johnfandl | Modules | => Core | ||
| 2017-04-10 14:39 | alostale | Assigned To | alostale => platform | ||
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base | ||
| There are no notes attached to this issue. |