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

Claim returned-2.8: Do not allow "actions" to be made on fees/fines for items that are "Claimed returned"

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      UNAM
    • Release:
      R2 2021

      Description

      Purpose
      To not allow actions (e.g. payments, waives, refunds, transfers or cancellations due to error) to take place against fees/fines for items that have a status of "Claimed returned."

      Scenarios

      1. Scenario
        Given Fee/Fine History displaying
        When fee/fine for item and Item status in Item Record = "Claimed returned"
        Then gray out ellipsis options Pay, Waive, Refund, Transfer and Error (leaving Loan details)
      2. Scenario
        Given Fee/Fine History displaying and one row checked
        When fee/fine for item and Item status in Item Record = "Claimed returned"
        Then gray out buttons Pay, Waive, Refund and Transfer (leaving New fee/fine)
      3. Scenario
        Given Fee/Fine History displaying and multiple rows checked
        When fee(s)/fine(s) for item(s) and one or more items has Item status in Item Record = "Claimed returned"
        Then mark the claimed returned fee(s)/fine(s) to be deselected before the user is allowed to continue (as we do now when a closed fee/fine is selected with non-closed fees/fines within the Fee/Fine History "All" tab)
      4. Scenario
        Given Fee/Fine Details displaying
        When fee/fine for item and Item status in Item Record = "Claimed returned"
        Then gray out buttons Pay, Waive, Refund, Transfer and Error

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ccruzg@dgb.unam.mx Christian Cruz Garrido
                Reporter:
                hollyolepm Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases