CRUD Fee/Fine Overdue Fine Policies

To see how this JIRA issue integrates with the other overdue fine JIRA issues please see the diagram at https://drive.google.com/file/d/1XSWA3SLDU4wIVjtazjXJHUWLbd1O5zZj/view?usp=sharing

Purpose: Allow staff member to create/review/update/delete an overdue fine policy to be associated with a loan policy by the Circulation Rules Editor.

SCENARIOS

1. Scenario
Given Settings ==> Circulation
When displayed
Display in new format as show by attached screen mock-up 1-with-headings.png, adding Overdue fine policies for this user story (and Lost item fee policies for future user story)

2. Scenario
Given Settings ==> Circulation ==> Overdue fine policies
When no Overdue fine policies exist
Then display blank list of existing Overdue fine policies as show in attached mock-up 1-with-headings.png, with option for adding a new one

3. Scenario
Given Overdue fine policies
When New button selected
Then open New overdue fines policy page as shown in attached mock-ups 2-new-overdue-fines.png and 3-overdue-fines-save.png, using defaults as shown in mock-up
Validation

• Overdue fine policy name is a required field and must be unique for the institution
• If Overdue fine is not entered, set it to 0
• Overdue fine must be = 0 or > 0
• If Overdue fine > 0 then interval must be selected
• Maximum overdue fine must be > 0 if Overdue fine > 0
• If Overdue recall fine is not entered, set it to 0
• Overdue recall fine must be = 0 or > 0
• If Overdue recall fine > 0 then interval must be selected
• Maximum overdue fine must be > 0 if Overdue recall fine > 0

Save & close button should remain grayed out until all validation has been passed

4. Scenario
Given New overdue fine policies
When Save & close button selected
Then save entered data and display success toast as shown in attached mock-up 4-with-policy.png

5. Scenario
Given Settings ==> Circulation ==> Overdue fine policies
When one or more Overdue fine policies exists
Then display list of existing Overdue fine policies as show in attached mock-up 1-with-headings2.png, with option for adding a new one

6. Scenario
Given the Overdue fine policies list
When one is selected to view
Then display details of policy per attached mock-up 5-view-policy.png

7. Scenario
Given the viewed Overdue fine policy
When Edit button is pressed
Then present full-screen version of Overdue fine policy for editing, as shown in attached mock-up 6-overdue-fines-edit.png
Save & close button is grayed out until a field is edited and validation is complete

8. Scenario
Given the Edit - <Overdue fine policy name> page (as shown in attached mock-up 6-overdue-fines-edit.png)
When Cancel option is selected
Then reset fields to original values and close out page, going back to previous page

9. Scenario
Given the Edit - <Overdue fine policy name> page (as shown in attached mock-up 6-overdue-fines-edit.png)
When Delete option is selected
Then display Confirm deletion modal (as shown in attached mock-up 7-overdue-fine-delete-confirm.png)

9b. Scenario
Given the Confirm deletion modal (as shown in attached mock-up 7-overdue-fine-delete-confirm.png)
When Cancel button pressed
Then close out Confirm deletion modal and display Edit - <Overdue fines policy name> page again

9c. Scenario
Given the Confirm deletion modal (as shown in attached mock-up 7-overdue-fine-delete-confirm.png)
When Confirm button pressed
Then delete policy, close out page, going back to previous page, and display success toast as shown in attached mock-up 8-policy-delete-success.png

10. Scenario
Given Edit - <Overdue fine policy name>
When changes made and validated
Then Save & close button becomes active

11. Scenario
Given Edit - <Overdue fine policy name>
When Save & close button pressed
Then save changes and close out page, going back to previous page, and display success toast as shown in attached mock-up 9-policy-update-success.jpg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DESCRIPTION

The purpose of this user story is to allow a staff member to associate an overdue fine policy with a loan policy in the circulation rules editor. The circulation rules editor requires that each policy type be present, so even libraries that do not charge overdue fines will need one overdue fine policy set to 0 that is used by all circulation rules.

The first step in this task to to change the design of the Settings ==> Circulation section of FOLIO as shown in the attached screen mock-up 1-with-headings2.png. This section was getting very crowded and the designer decided to organize it. The "Fee'fine" section with two options is new. This user story focus on "Overdue fine policies" only.

The functionality of "Overdue fine policies" is very similar to the other policies within the "Circulation" section. We need to be able to create new policies, review existing policies, update existing policies, and delete unneeded policies, as shown in the attached screen mock-ups.

The field validation is as follows:

• Overdue fine policy name is a required field and must be unique for the institution
• If Overdue fine is not entered, set it to 0
• Overdue fine must be = 0 or > 0
• If Overdue fine > 0 then interval must be selected
• Maximum overdue fine must be > 0 if Overdue fine > 0
• If Overdue recall fine is not entered, set it to 0
• Overdue recall fine must be = 0 or > 0
• If Overdue recall fine > 0 then interval must be selected
• Maximum overdue fine must be > 0 if Overdue recall fine > 0

After adding a new "Overdue fine policy" or updating/deleting an existing "Overdue fine policy", a "success toast" should be displayed. Prior to deleting an "Overdue fine policy" a confirmation modal should be displayed. (Mock-ups are attached.)

Please see Holly with any questions or comments. Thanks!