Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-544

CRUD Fee/Fine Transfer Accounts Settings

    XMLWordPrintable

Details

    • UNAM

    Description

      Purpose: Allows Fee/Fine Owner to identify accepted accounts to which fees/fines are transferred. When a fee/fine is transferred, it is zeroed out by FOLIO and given a Payment Status of Transferred fully or Transferred partially, depending on the situation. The "Action" within Fee/Fine Details will display as Transferred fully-<transfer-account-name> or Transferred partially-<transfer-account-name>. For example: "Transferred fully-Bursar", "Transferred partially- State Tax Office", "Transferred fully-Collections", etc. (Note: The transfer feature should not be used for collections unless the balance is actually purchased by the collections agency.)

      DISPLAY SCENARIOS

      1. Scenario
        Given the Fee/fine: Transfer accounts page
        When displayed with no existing fee/fine owners
        Then display page as shown in attached mock-up 4-Fee-Fine-Transfer-Accounts2.jpg)
      2. Scenario
        Given the Fee/fine: Transfer accounts page
        When displayed with existing fee/fine owners
        Then display page as shown in attached mock-up 4-Fee-Fine-Transfer-Accounts.jpg, allowing user to select Fee/Fine Owner to create, view, or modify transfer accounts for

      ADD NEW TRANSFER ACCOUNT

      1. Scenario
        Given the +New button
        When pressed
        Then add a new row on the top line for entering required field Name and optional field Description (as shown in attached mock-up 4-Fee-Fine-Transfer-Accounts.jpg)--the Save button will be inactive until the required field Name has been entered and proven to not be a duplicate
      2. Scenario
        Given the Fee/fine: Transfer accounts page with inserted row
        When Name is skipped
        Then display error "Please fill this in to continue" (in same manner already being used for Payment Methods)--do not progress further until error is fixed or Cancel button is pressed
      3. Scenario
        Given the Fee/fine: Transfer accounts page with inserted row
        When Name is a duplicate
        Then display error "Transfer account already exists" (in same manner already being used for Payment Methods)--do not progress further until error is fixed or Cancel button is pressed
      4. Scenario
        Given Fee/fine: Transfer accounts page with inserted row
        When Name provided and not a duplicate
        Then activate Save button at end of insert row
      5. Scenario
        Given activated Save button at end of insert row
        When pressed
        Then save the new transfer account in the database for the selected fee/fine owner and display it as the first row of the table
      6. Scenario
        Given Cancel button at end of insert row
        When pressed
        Then close row that was to be inserted, leaving user where they were just prior to pressing the +New button

      UPDATE EXISTING TRANSFER ACCOUNT

      1. Scenario
        Given the pencil icon at end of existing row of Fee/fine: Transfer accounts page
        When pressed
        Then open Name and Description fields for editing
      2. Scenario
        Given the Fee/fine: Transfer accounts page with edited row open
        When Name is skipped
        Then display error "Please fill this in to continue" (in same manner already being used for Payment Methods)--do not progress further until error is fixed
      3. Scenario
        Given the Fee/fine: Transfer accounts page with edited row open
        When Name is a duplicate
        Then display error "Transfer account already exists" (in same manner already being used for Payment Methods)--do not progress further until error is fixed
      4. Scenario
        Given Fee/fine: Transfer accounts page with edited row open
        When Name provided and not a duplicate
        Then activate Save button at end of edited row
      5. Scenario
        Given activated Save button at end of edited row
        When pressed
        Then save the updated transfer account data, along with date, time and source, in the database for the selected fee/fine owner and display it in the table
      6. Scenario
        Given Cancel button at end of edited row
        When pressed
        Then close row that was to be inserted, leaving user where they were just prior to pressing the pencil button

      DELETE EXISTING TRANSFER ACCOUNT

      1. Scenario
        Given the garbage can icon on existing row of Fee/fine: Transfer accounts page
        When pressed
        Then display Delete transfer account pop-up (as shown in attached mock-up 4-Fee-Fine-Transfer-Accounts3jpg)
      2. Scenario
        Given the Cancel *button on the *Delete transfer account pop-up
        When pressed
        Then close out the "Delete transfer account" pop-up and go back to the list of transfer accounts as shown before the garbage can icon was selected
      3. Scenario
        Given the Delete button on the Delete transfer account pop-up
        When pressed
        Then delete the selected transfer account from the database, close out the "Delete transfer account" pop-up, and go back to the list of transfer accounts with the deleted one no longer displaying

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases