Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0007881 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Openbravo ERP] A. Platform | major | have not tried | 2009-02-28 04:50 | 2009-05-22 19:33 | |||||||
Reporter | fisher | View Status | public | |||||||||
Assigned To | iciordia | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0007881: Configurable Composite search help link to multi data source of the field | |||||||||||
Description | Currently the user can use the standard search screen for certain field with linked lookup table, such as product, vendor and customer, but the user can not change the search screen(selection criteria fields) easily, and one field only associate with one search screen/one data source, but actually some times for the same field, e.g product, different users in different window need search the product by different selection criteria from different data source, in most of the cases, users search the product via the product master, but when in production related window, it is desirable to search the product via Bill of material definition. most of the users will search the customer via customer master,but it is also desirable to search the customer via sales transaction history and customer credit/payment history. | |||||||||||
Proposed Solution | 1. create table and corresponding window managing the search help definition 1.1 single search help( source table/view, input parameter/field, output parameter/field 1.2 composite search help( composite search help, single search help) 1.3 link the application element/reference item to the corresponding single or composite help 2.handle the search help definition via a general search help engine, make sure for composite search help, there are multi tab sheets available for user to switch to different search option(selection criteria from different data source) | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ![]() ![]() ![]() | |||||||||||
![]() |
|
![]() |
|
(0014642) fisher (reporter) 2009-03-16 07:18 |
Some screen shot provided, hopefully it can give you some ideas how to implement this function in OB |
![]() |
|||
Date Modified | Username | Field | Change |
2009-02-28 04:50 | fisher | New Issue | |
2009-02-28 04:50 | fisher | Assigned To | => rafaroda |
2009-03-03 12:25 | rafaroda | Assigned To | rafaroda => pjuvara |
2009-03-16 07:15 | fisher | File Added: CollectiveSearchHelpDefinition.JPG | |
2009-03-16 07:16 | fisher | File Added: CollectiveSearchHelpElementaryHelp.JPG | |
2009-03-16 07:16 | fisher | File Added: CollectiveSearchHelpInAction.JPG | |
2009-03-16 07:18 | fisher | Note Added: 0014642 | |
2009-05-22 19:33 | pjuvara | Assigned To | pjuvara => iciordia |
Copyright © 2000 - 2009 MantisBT Group |