Create, close, cancel, Purchase Orders (UXPROD-1141)

[UIOR-723] Multiple PO lines created when 'Save & Open' used on POL with fund distribution and no budget Created: 29/Apr/21  Updated: 31/May/21  Resolved: 31/May/21

Status: Closed
Project: ui-orders
Components: None
Affects versions: None
Fix versions: 2.4.0
Parent: Create, close, cancel, Purchase Orders

Type: Bug Priority: P3
Reporter: Molly Driscoll Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word Iris Bugfest Repro on Order Bug.docx     PNG File image-2021-05-31-11-32-40-203.png    
Issue links:
Defines
defines UXPROD-2630 Thunderjet - R2 Enhancements/Bugfixes Closed
Sprint: ACQ Sprint 115
Story Points: 2
Development Team: Thunderjet
Release: R2 2021
Affected Institution:
MI State University/Library of Michigan
Tester Assignee: Dennis Bridges
Epic Link: Create, close, cancel, Purchase Orders

 Description   

Overview: A library is using the setting to allow for 'save & open order'. They add a PO line with a fund distribution then click 'save & open order'. If the fund does not have a current budget, they receive an error message that the purchase order has not been opened because "One or more fund distribution(s) on this order can not be encumbered, because there is no current budget." Adjusting the fund distribution to a fund code with a current budget produces the same results. Hitting 'save & close' is the only way to save the POL. However, this creates a separate POL for each time you tried to save & open, each with the fund code that was attempted prior to each save.

Steps to Reproduce:

  1. Log into https://bugfest-iris.folio.ebsco.com/ as a user with admin permissions.
  2. Make sure that 'save & open' is configured to be on in order settings.
  3. Create a new fund. Do not create a current budget for the fund. 
  4. Create a new order.
  5. Add a PO line. Make sure that you apply a fund distribution with the fund that you created in step 3.
  6. Click Save & open order.

Expected Results:

  1. Receive an error that there is no budget.
  2. Change the fund code to one with a current budget.
  3. Click 'save & open order' again and receive a toast message that the order was opened.
  4. One POL is created with the fund code for the fund with a current budget.

Actual Results:

  1. Receive an error that there is no budget.
  2. Change the fund code to one with a current budget.
  3. Receive another error message that "The Purchase order - XXXX has not been opened. One or more fund distribution(s) on this order can not be encumbered, because there is no current budget." - Repeats on each subsequent attempt.
  4. Click 'save & close' to at least save the POL.
  5. See that there are multiple POL created on the order, each with a different fund code.

It seems that even after changing the fund in the fund distribution dropdown, the original fund UUID is still being called.

Additional Information:

Reproduced on Mich State/Lib of Michigan Test Tenant, Bugfest Honeysuckle, and Bugfest Iris. Screenshots of errors and results attached.

Interested parties: Kay Granskog



 Comments   
Comment by Kelly Drake [ 29/Apr/21 ]

Molly Driscoll - if this only occurring in the Iris Bugfest environment or are you also seeing this in goldenrod?

Comment by Molly Driscoll [ 29/Apr/21 ]

Kelly Drake, I was able to reproduce on the Michigan State/LoMichigan test tenant (Honeysuckle Hotfix #3), Honeysuckle Bugfest, and Iris Bugfest. I did not go back as far as Goldenrod. Is that needed?

Comment by Kelly Drake [ 29/Apr/21 ]

Hi Molly Driscoll  Goldenrod testing is not needed - I lost track of our releases.  

Comment by Molly Driscoll [ 29/Apr/21 ]

Kelly Drake, no worries – it's been that kind of week! Thanks for the follow-up!

Comment by Dennis Bridges [ 29/Apr/21 ]

Thanks I have set the priority to P3. This is more a usability issue than a bug. The POL is being created properly but the order can't be opened as they have not setup their funds correctly. The system saves the POL and refreshes the POL create form.

Also this is only possible if the "Save and Open POL" setting is turned on for the orders app.

Comment by Molly Driscoll [ 29/Apr/21 ]

Hi Dennis Bridges, what qualifies as a refresh in this scenario? It appears all of the information entered originally on the POL is retained on subsequent lines. The only thing that changes is fund code. However, even though the fund code appears to be changed on the POL, the same fund UUID is called on each subsequent attempt, which produces the continued red "toast" that there is no budget on the fund. That seems buggy to me. If it helps for me to record a video to better demo this behavior, please let me know!

Comment by Dennis Bridges [ 29/Apr/21 ]

Molly Driscoll that is very true the data is not cleaned out of the form which is definitely more misleading. I have left this as a bug and we will address it asap.

Comment by Molly Driscoll [ 29/Apr/21 ]

Thank you, Dennis!

Comment by Anya [ 03/May/21 ]

Support: - checking in - is reads as if you all have this in hand - please correct our assumption... Dennis Bridges will this be fixed for juniper. 

Comment by Dennis Bridges [ 03/May/21 ]

Yes, thanks Anya. This has been assigned to our R2 bug fix feature.

Comment by Debra Howell [ 10/May/21 ]

From SUPPORT SIG: Dennis Bridges please set the Release value for this to R2 2021 if it will be in Juniper. Thanks!

Comment by Mikita Siadykh [ 31/May/21 ]

Dennis Bridges tested on testing env, please review

Comment by Dennis Bridges [ 31/May/21 ]

Mikita Siadykh This is nearly complete and seems to be working well. It is a little slow too process when clicking save and open but I assume that is just the testing environment.

The only issue is that we don't see the actual error message of why it could not save. As per the description, if possible we want to show the 'One or more fund distribution(s) on this order can not be encumbered, because there is no current budget'. This was the user knows what to fix. Is it possible to show that error without BE work?

Comment by Mikita Siadykh [ 31/May/21 ]

Dennis Bridges expected result doesn't say anything about it   - the first step that is already implemented 

actually we show this information in the second message when we know the reason, so in your case it's smth unexpected (from what I see it's 500 generic error) we show generic message. it was implemented long time ago

Comment by Dennis Bridges [ 31/May/21 ]

Test successful in FOLIO-testing. I was able to get the error successfully so there must have been more than one issue. thx!

Generated at Thu Feb 08 22:21:42 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.