Web Client: Payment Screen Has to be Refreshed for Multiple Payments

[Shula Link]

In v.3.0.2:

In the current XUL client, if a patron is paying a fine in multiple parts (i.e., has a fine forgiveness card from a SRP event and is paying the rest in cash), the two transactions can be done one after another.

In the web client, the screen must be refreshed before a second transaction can be processed.

[Laura Sachjen (sachjenl)]

Just tested this on a current master sandbox and I am able to apply multiple payments without refreshing.

[John Amundson (jamundson)]

I've confirmed this bug because I can duplicate this in 3.0.8. However it doesn't happen every time, and I think the bug is actually something else.

We have noticed sometimes grids will become entirely highlighted when a single entry is checked. We have seen this most often on the Bills screen. I am not sure what causes this problem, but it usually only happens after making a payment:

1. Check the appropriate bill(s) and make a payment.
2. Check the bill(s) again to make a second payment. Do all the bills "check" if you only check one? If so, trying to submit a second payment fails. This is what I am referring to as the "all bills checked" problem where uchecking/checking any bill will uncheck/check them all and not allow you to do anything else with them. However, if the bills check as desired, a second payment can be made.

When the "all bills checked" problem happens, it can be temporarily fixed by reloading the page. At that point, another payment can be submitted.

I have found that if I simply reset my columns on the bills screen and save them, then the "all bills checked" problem goes away. At least for awhile.

I'd be interested in knowing for those you cannot submit multiple payments, if you, too are experiencing the "all bills checked" problem.

[John Amundson (jamundson)]

See https://bugs.launchpad.net/evergreen/+bug/1780283 for more on workflow described in my previous comment.

[John Amundson (jamundson)]

I have a feeling this may be fixed as of 3.0.12. See related bug: https://bugs.launchpad.net/evergreen/+bug/1776917

[Terran McCanna (tmccanna)]

Fixed re bug 1776917