web client: Work log is not honoring maximum # of transaction OU setting

[Kathy Lussier]

The work log in the web client isn't honoring the maximum number of actions library setting. For example, when testing on webby, I set the Maximum Actions Logged OU setting to 2 and the Maximum Patrons Logged OU setting to 2.

When I retrieve the work log, I see six transactions listed in the most-recently logged actions and five transactions in the most recently affected patrons (see attached screenshot.)

[Galen Charlton (gmc)]

I could not reproduce this problem when testing against a master instance today. Kathy, are you still seeing this issue?

[Kathy Lussier (klussier)]

Sorry for the delayed response! I was still getting a large number of entries in my Work Log, but, after clearing out the log entries from my local storage and performing several transactions, the Work Log did start honoring the OU setting. I'm guessing my experience was based on entries stored in local storage back before the OU setting was being consulted.

I'll set this to Invalid. Thanks Galen!

[Andrea Neiman (aneiman)]

I'm reopening this one, because I am seeing it in the webclient in 3.2.2. Yes, I was able to force the new setting to be honored by clearing local storage; however, having to clear local storage to force the new OU setting value to be honored is not an ideal way of things.

[Terran McCanna (tmccanna)]

Confirming the behavior that Andrea reported in comment #4 in the web client as of 3.7 beta.