Unable to add PO line w/o required payment

Description

Overview:
T3315: Create physical order with payment not required and fully receive to close order as complete
Steps to Reproduce:

  1. Log into bugfest.folio.ebsco.com as sbiondi

  2. Click Orders

  3. Create New PO w/template Demo Orders One-time

  4. Add PO Line with same template (can't select different one at this point); Acquisition Method=Gift, Order Format=Physical Resource, List Unit Price=0 (unable to leave empty), Quantity Physical=4, Vendor Ref Type=Internal, Vendor Ref Number=123, otherwise use template as-is

  5. Click Save
    Expected Results:
    PO line should save, and be able to be received, and PO closed
    Actual Results:
    PO line cannot be saved
    Additional Information:
    Temporarily could not look at/create POs, but bug stopped replicating (image attached).
    Appears other PO lines can be created, so maybe some issue with combination of factors? (Gift, price of 0, etc.)
    Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

6

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges March 13, 2020 at 4:48 PM

I'm closing this as in the current build the order can be saved with payment not required. I have also confirmed that receiving the pieces for that order does complete the order automatically.

Sara Biondi September 24, 2019 at 11:39 AM

The line doesn't save if I have "Payment not required" set. I have experimented with different Acquisition Methods (Gift, Exchange), which doesn't seem to matter.
I wish I could provide a video, but I screencapped the POL as I set it up again this morning to try again. I'm sure I must be making a mistake somewhere if you aren't able to reproduce it, but without creating the line I wasn't able to test closing it.

Dennis Bridges September 23, 2019 at 9:39 PM

Having some trouble reproducing this so I'd like to confirm a few things. Is the line not saving when you Try to set the "payment status" to 'Payment not required'? Or are you referring to not being able to leave the "List unit price" field blank? It was decided by the UX team not to allow the price field to be left blank so the user would need to actively set the cost to 0. This way they are not able to forget to add a cost.

Victoria_Smelova September 23, 2019 at 11:25 AM

, could you review and prioritize, please.

Cannot Reproduce

Details

Assignee

Reporter

Tester Assignee

Priority

Development Team

Thunderjet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 19, 2019 at 12:27 PM
Updated March 13, 2020 at 4:48 PM
Resolved March 13, 2020 at 4:48 PM
TestRail: Cases
TestRail: Runs