Friday, July 3, 2009

Query Component Save bug

In the same application bellow i try the Save... button

Since i usally want to query employees with salary >3000 i set that value and i save search:

But when i run that saved search i dont get the result, the value of criterion is lost:

So i thought ok it doesn't save values, lets see advanced search:
I use advanced search and add Salary again with same value.
I save criteria and now it saves both criterion and value:

So it doesnt save criteria values that have bind variable.
Yet i wouldnt know how to explain this to an end user...
Is this a bug?
No? since it has a workaround?
Dont use bind variables in criteria?


  1. Tell end-user that he should be proud, because he works with Enterprise #1 system.

    My regards,