Ticket #2044 (new defect)

Opened 10 years ago

Last modified 10 years ago

Bad handling of out of range requests

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.4.10
Component: CPSDashboards Version: TRUNK
Severity: normal Keywords: batching pages


In case the user requests a page of results that falls out of the range of the existing ones, a tabular widget will return an empty page, with the message that there is no result, which is plain wrong.

This can happen for instance if the very same user triggers a batch action on the last page, whose effect is to remove the listed items from the results (workflow transition, removal, etc.)

The tabular should instead automatically switch to the actual last page, and in case of utter confusion, get back to the first page.

Change History

comment:1 Changed 10 years ago by gracinet

[53920] provides a fix for catalog tabular widgets with doctests for the lucene case (more complicated because of native batching and non-transactionality).

Should be extended to other sub tabular types and tested in each case for acceptance in 3.4 branch.

comment:2 Changed 10 years ago by gracinet

Lucene catalog has side effects on the passed query arguments. Namely, boolean insertion operator is lost, this can for instance flip from exclusion (NOT) to inclusion (AND which is default).

Done first in the branch where I need it [53931] and forward-ported to trunk [53936]

comment:3 Changed 10 years ago by gracinet

  • Milestone changed from CPS 3.4.9 to CPS 3.4.10

Too fresh to go in 3.4.9

Note: See TracTickets for help on using tickets.