When I put a filter on eg the project list and filter it works OK.
When I click Show all it works OK.
When I click next page the filter is reapplied.
Is that normal behaviour in v13.3. with IE, FF and Chrome or is it just this system?
If the app services performing in this cluster do not have the Distributed checkbox enabled on their application properties pages in the CSA, that would definitely be something to consider. Just do not also check / use the Cache Distributed checkbox, it would not be needed/beneficial here.
If the load balancer 'sticky sessions' settings are rigid and reliable enough, then the overhead on the Clarity applications for enabling the Distributed checkbox are sometimes not worth the tradeoff of the occasional lost filter - and in fact within the OnDemand environments, they currently do not use this setting for that reason. With the Distributed box enabled, at the top and tail of every page request (or web 'hit') to Clarity, it will read and write the current state of the filters to the database.
The overhead is therefore brought from the contention to the table used for this, as all users in the system for each page they navigate to will be doing a lot of write activity and databases can only tolerate this for so much concurrency at a time.
It would however likely solve your current configuration issue until the LB configuration can be checked into for why it is doing so much round-robin activity for your session.
It worked for me with a 13.3 sandbox I have here - I used a manually entered filter first, then tried a saved/named filter second, as I wasn't sure which type you tried but I had the same results with both (using IE in my case, though your results seemed browser independent).
The "you don't have sticky sessions enabled on your load balancer" scenario could explain the same symptoms.
(but if you are not using multiple apps and a load balancer, then its obviously not that, so just ignore me )
I did wonder about the load balance scenario, and it is something that should also be influenced only if sticky sessions isn't enabled AND the Distributed checkbox on the Clarity apps is unchecked, otherwise filter information is supposed to be persisted to the database between each click and able to be re-read again even if you are switched app servers from one request to the next.
I found this intriguing to say the least. When I clicked Show All in a 184.108.40.2066 environment this morning and then clicked the next page triangle, I got that bug where the filter was re-applied. I went to a 14.3 instance to verify this behavior does not appear in the pending future release (Eltz). Then I began scouring the 13.3.x patch announcements and resolved defects and our internal DB trying to find the specific resolved issue in the 13.3 to 14.1/14.2 timeframe. I did not see this issue noted. The closest I could find was:
CLRT-73810 (S4) - Project Instance Rights-when you select next page, the filter criteria is blanked out.
Steps to Reproduce:
1. Log in to CA Clarity PPM and navigate to the project’s list from Home.
2. Select a project.
3. From Properties, under Access to this project click on Resource.
4. Click Add.
5. The Access Rights are spread across 3 pages and the total number of results is 46.
6. Select the filter as *a* for Access Rights, the total number of pages are 3 and the number of results are 41.
7. Click on the next page arrow.
8. On the 2nd page, the filter mentioned for access right is cleared and the total number of results displaying is 46 instead of 41 shown in the 1st page.
Then I tried another 13.3 instance and could not duplicate the new alleged bug. Show All and next page did not revert to the applied filter. I cleared my browser cache and even my Java 8 cache but could not repeat this bug on any 13.3 instance. (Chrome/Win 7/Java 8). So are you still seeing this and able to repeat this?
Thank you guys for the plentiful responses. These were my steps on that system
Then show all
and click next page
No problem on community sandbox which is Version 220.127.116.11 Patch 04.21 and not 13.3 as I thought.
Will have to verify in the office whether or not a load balancer is used with the 13.3 system.
There are load balancers with the 13.2 systems, but they do not have this problem.
Did experience something in the area of CLRT-73810
After step 6 clicked Show all and all were shown.
Clicked next page and the filter was applied again.
To get rid of that have to apply show all a couple to times and then Clarity believes that I really mean it.
if you hit clear and then filter do you get the same result?
Will have to try that.
Don't need that on the two 13.2 systems or any other I've used.
No filter, move OK to the next page as expected
Filter for f, works OK
Show all works OK
Click Next page filter is reaplied, less than one page of results so next page is not available
No click Show all twice.
No problem to move from one page to the next.
Conclusion: Can repeat at will, and there is a work around.
Previously experienced on other lists as well.
I still cannot reproduce, but acknowledge that you can. It does have a workaround, but it would be good to follow-up at some future point to narrow this down. I filed an internal request for a bit of additional regression testing here. I cannot reproduce in 13.3, 14.1, 14.2, or 14.3 so this may be a peripheral issue that becomes obsolete as customers especially SaaS customers move to 14.2, 14.3, or a future 14.x release. To track this for now, CLRT-78897 has been filed. Thanks again for bringing this to our attention.
It is one specific system with one specific version and it is with load balancer. So I not convinced that Clarity is the only explanation.
Thanks nick_darlington, checking Distributed on both app servers seems to have done the trick.
Just an epilogue to this: the situation which I find most inconvenient is adding rights when you first filter and then get several pages select some from the first page and click Add and Select more. Takes some ingeniuity to get to the next page.
If you are an admin and you know what you are doing, just bypass the load balancer - just go straight to any app-server in the browser, then you will never get "switched" between apps and everything will behave.
(not much use for a user, since other functionality would be compromised)
OR ; fix your load balancer of course!
Going directly to the app server does not work if you have SSO and two stage authentication.
Retrieving data ...