Update POL Cost detail accordion
Description
Environment
Potential Workaround
Attachments
- 08 Apr 2021, 01:08 PM
- 01 Oct 2020, 08:12 AM
- 29 Sep 2020, 07:39 PM
- 29 Sep 2020, 07:39 PM
- 29 Sep 2020, 05:13 PM
- 14 Sep 2020, 04:48 PM
- 14 Sep 2020, 04:47 PM
- 14 Sep 2020, 04:45 PM
- 14 Sep 2020, 04:42 PM
blocks
defines
Checklist
hideTestRail: Results
Activity
Aliaksei Chumakou April 12, 2021 at 3:47 PM
@Alexander Soto I see your point, thanks. However, it's not related to that particular ticket or changes related to it. What do you think if it's a good idea to create a separate bug-ticket to fix the label?
Alexander Soto April 12, 2021 at 2:48 PM
Hi @Aliaksei Chumakou. I think that the label displayed is wrong because this order is not either "Print/Electronic Mix" or "physical" is an electronic resource package then why showed up the "physical unit price" label instead of the "electronic unit price"? I understood that it appearing because of the ispackage=true field but although it is a package, it is not a physical resource but an electronic one. I think to solve this issue is only to delete the first part of the label where appears "physical" and to leave "unit price" only. In that way, you could leave on this field both information of price for physical and electronic and is not confusing for the end-user
Aliaksei Chumakou April 8, 2021 at 3:38 PMEdited
@Alexander Soto it looks like expected behavior. Your line has isPackage=true and orderFormat isn't 'P/E Mix'. The label is displayed basing on these fields values. Do you think it's wrong?
BTW, I don't think it's connected to this ticket, because it was done a year ago in scope of https://folio-org.atlassian.net/browse/UIOR-503#icft=UIOR-503
Alexander Soto April 8, 2021 at 1:09 PMEdited
I saw that this case closed; however, I have seen the following display issue:
I have an electronic poLines with the following information: { "id": "ac28ba72-f01c-4ab6-b10c-a4bed11eeba3","checkinItems": false, "acquisitionMethod": "Purchase At Vendor System","alerts": [], "claims": [], "collection": false, "contributors": [], "cost": { "listUnitPriceElectronic": 24731.27, "currency": "GBP", "discountType": "percentage", "quantityElectronic": 1, "poLineEstimatedPrice": 24731.27 },
note that in the listUnitpriceElectronic field a price has been included, but in the poLines the information is displaying on "physical unit price"
please check on Iris: https://bugfest-iris.folio.ebsco.com/orders/view/1bc97897-3c38-4a04-ae9d-d9913f76ec4c/po-line/edit/ac28ba72-f01c-4ab6-b10c-a4bed11eeba3?query=1006154232021
Dennis Bridges October 5, 2020 at 2:49 PM
testing successful in FOLIO-testing
Purpose: Improve the usability of the fields in the cost details accordion on the Purchase order line.
User story statement(s):
As an ordering librarian
I want to see cost details with price and quantity next to each other and with consistent labeling
so that it is easy for me to understand what fields I need to populate in order to represent the cost of what I am ordering.
Scenarios:
Scenario: :check_mark:
Given User is creating/editing a POL
When when inputing cost details
Then the order of fields is as follows: (See screenshot)
Physical unit price
Quantity physical
Currency
Additional cost
Electronic unit price (Current label "Unit price of electronic" must change)
Quantity electronic
Discount
Type
Estimated price
Scenario: :check_mark:
Given the user has created a POL with cost details
When the user is viewing the cost details accordion in the view pane
Then the fields appear the same order described above (See screenshot 2)
Scenario: :check_mark:
Given User is creating/editing a PO template
When when inputing cost details at POL
Then the order of fields is as follows: (See screenshot 3)
Physical unit price
Quantity physical
Currency
Additional cost
Electronic unit price (Current label "Unit price of electronic" must change)
Quantity electronic
Discount
Type
Estimated price
Scenario: :check_mark:
Given the user has created a PO template with cost details
When the user is viewing the cost details accordion in the template view screen
Then the fields appear the same order described above (See screenshot 4)