Project:
| View Revisions: Issue #33478 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0033478: implicit filters not applied in updated instances with grid configuration | ||
| Revision | 2016-07-14 12:52 by alostale | ||
| Description | Instances updated from a previous release that had "Grid Configuration" preferences with transactional filters applied, do not apply transactional filters when fetching data though in the UI the message informing the transactional filter is applied is seen. The problem is caused because old grid configuration saved in their state whereClause as string and now the code expects it to be a boolean filterClause:\" ( e.updated > @transactionalRange@ or e.processed = 'N' ) \" |
||
| Revision | 2016-07-14 12:40 by alostale | ||
| Description | Instances updated from a previous release that had "Grid Configuration" preferences with transactional filters applied, do not apply transactional filters when fetching data though in the UI the message informing the transactional filter is applied is seen. | ||
| Revision | 2016-07-14 12:34 by alostale | ||
| Description | Under certain (still undefined) circumstances, transactional implicit filters are displayed as applied in UI, though they are not actually applied in backend filtering. This behavior has been observed in external module development, but not in OB3 distribution. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |