Update Charge Manual Fee/Fine to set default Fee/Fine Owner for user

Description

The Charge Manual Fee/Fine page has a Fee/Fine Owner field that represents who the fee/fine being charged will belong to. In most cases it is the "place" (Fee/Fine Owner) the patron is standing in front of or has called/emailed. Currently the user must select the Fee/Fine Owner when they open the Charge Manual Fee/Fine page (as shown in attached file ChargeManualFF.JPG). The intent was to populate the Fee/Fine Owner with a default value for the user rather than require that the user select the Fee/Fine Owner every time. We now have a way to do this.

In the User Information app there is a new section called "Service Points" (as shown in attached file UserInformation.JPG). Users that work at the library will be associated with one or more service points. One of the Service Points may be designated as Service Point Preference (as shown in attached file ServicePoints.png).

The Service Point Preference or single Service Point provided will be used to convert the current User's Service Point to a Fee/Fine Owner, using the Fee/Fine Owner table. The Fee/Fine Ower will be pre-populated in the Charge Manual Fee/Fine page when the user opens it up.

How to determine default Fee/Fine Owner for user:
1) If user has no Service Points designated (no preference or service points), open Charge Manual Fees/Fines without a default Fee/Fine Owner selected (like it is now).
2) If user has a Service Point Preference selected (see attachment Service Point example -two SPs with preference.jpg), convert the Service Point Preference to a Fee/Fine Owner using the Fee/Fine Owner Table. If an error occurs, open Charge Manual Fees/Fines without a default Fee/Fine Owner selected (like it is now).
3) If the user doesn't have a Service Point Preference, but does have one Service Point listed (see attachment Service Point example - one SP no preference.jpg), convert the single Service Point to a Fee/Fine Owner using the Fee/Fine Owner Table. If an error occurs, open Charge Manual Fees/Fines without a default Fee/Fine Owner selected (like it is now).
4) If the user doesn't have a Service Point Preference, but does have two Service Points listed (see attachment Service Point example - two SPs no preference.jpg), convert both Service Points to a Fee/Fine Owner using the Fee/Fine Owner Table. If they convert to the same Fee/Fine Owner, use that Fee/Fine Owner. If not, or if an error occurs, open Charge Manual Fees/Fines without a default Fee/Fine Owner selected (like it is now).
5) If the user doesn't have a Service Point Preference, but has more than 2 Service Points listed, open Charge Manual Fees/Fines without a default Fee/Fine Owner selected (like it is now).

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Holly MistlebauerJanuary 10, 2019 at 7:15 PM

Congrats! All of the tests have passed, as shown in attachment UIU-610 Test Plan_2019-01-10.xlsx. This works perfectly! Thanks much...

Holly MistlebauerDecember 12, 2018 at 9:51 PM

This change has passed Holly's initial test for the Q4 2018 release--it will need to be tested again after the Q4 manual test environment is available on December 21.

Holly MistlebauerDecember 12, 2018 at 9:49 PM

Holly tested this on http://folio-snapshot.aws.indexdata.com/ using the attached test plan (see https://folio-org.atlassian.net/browse/UIU-610#icft=UIU-610 Test Plan.xlsx). There were 15 test cases in total--13 passed and 2 failed. The 2 test cases that failed are actually the same problem and aren't important enough to hold up the implementation of this feature. Holly has created a new Bug issue for this problem: https://folio-org.atlassian.net/browse/UIU-771#icft=UIU-771 (Default fee/fine owner being identified when user has no associated service points). You can read about the details of the error in the JIRA issues.

Holly MistlebauerNovember 16, 2018 at 5:10 PM

Holly tested this on http://folio-snapshot.aws.indexdata.com/

When I press the Charge fee/fine button on the User Information page (see attached screen print Step1.jpg), I get an error (see attached screen print Error.jpg).

This error has stopped me from testing this issue further.

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Development Team

UNAM

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 24, 2018 at 6:21 PM
Updated December 3, 2020 at 8:48 PM
Resolved January 10, 2019 at 7:16 PM
TestRail: Cases
TestRail: Runs

Flag notifications