Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0055032
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2024-03-21 19:252025-03-27 12:04
ReportervmromanosView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionduplicateFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0055032: Multi selector Filter Expression behaves as HQL Where Clause

DescriptionA filter expression should create a default filter when opening the selector that can be removed by the user. This is how it works in Tabs, for example.

However, for OBUISEL_Multi Selector Reference, the Filter Expression does properly filter the dataset by default, but then it's impossible to remove this filter to see the other records.
Steps To ReproduceAs system admin, search any existing OBUISEL_Multi Selector Reference.
Go to Defined Selector tab.
Enter any filter expression, for example: "e.parentRefInventory is null"

As a normal user, open the selector and check the default expression is properly applied. [OK]
However, it is impossible to remove it, so it actually behaves as a where clause for the query. [WRONG]
Proposed SolutionImplement the Filter Expression behavior like we have in Tabs.

Nice to Have: like in Tabs, Create a new translatable "Filter Name" field to write a description about the filter.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0177418)
hgbot (developer)
2025-03-27 12:04

Issue exported to Jira: https://openbravo.atlassian.net/browse/RM-24150 [^]

- Issue History
Date Modified Username Field Change
2024-03-21 19:25 vmromanos New Issue
2024-03-21 19:25 vmromanos Assigned To => Triage Platform Base
2024-03-21 19:25 vmromanos OBNetwork customer => No
2024-03-21 19:25 vmromanos Modules => Core
2024-03-21 19:25 vmromanos Triggers an Emergency Pack => No
2025-03-27 12:04 hgbot Note Added: 0177418
2025-03-27 12:04 hgbot Status new => closed
2025-03-27 12:04 hgbot Resolution open => duplicate


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker