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

[SUP-43] Expense class does not appear on order when using order template Created: 02/Jul/21  Updated: 27/Jul/21  Resolved: 26/Jul/21

Status: Closed
Project: Support
Components: None
Affects versions: None
Fix versions: None
Parent: Create, close, cancel, Purchase Orders

Type: Bug Priority: P2
Reporter: Molly Driscoll Assignee: Mikita Siadykh
Resolution: Duplicate Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File Bug with order template.webm    
Sprint:
Development Team: Thunderjet
Release: R2 2021 Bugfix
Affected Institution:
MI State University/Library of Michigan, TAMU
Epic Link: Create, close, cancel, Purchase Orders

 Description   

Overview: When using an order template, the expense class does not appear in the PO line, whether or not it is filled in as part of the template. It only appears after the PO line is saved. If the order template did not have an expense class filled in, this could present a workflow issue when trying to open the order.

Steps to Reproduce:

  1. Log into https://folio-snapshot.dev.folio.org/
  2. Make sure a budget on a fund has expense classes associated.
  3. Create an order template using that fund in the fund distribution accordion and selecting the appropriate expense class.
  4. Create an order using the template.
  5. Add a PO line to that order.

Expected Results: The PO line will contain the fund distribution with the expense class field filled in according to the template.

Actual Results: The fund code appears, but the expense class field does not appear. It appears after save, but you need to edit the PO line to change the expense class (or add one if your template did not have one in it already).

Additional Information: Reported by Michigan State (Iris HF #1) and replicated on Snapshot - see video.
URL:
Interested parties: Molly Driscoll Kay Granskog davidos2



 Comments   
Comment by Anya [ 06/Jul/21 ]

Support: Dennis Bridges this might become more of a P2 ... 

Comment by Dennis Bridges [ 06/Jul/21 ]

Anya we have now resolved this for the Juniper release. See UISACQCOMP-39 for more detail. If there is any expectation that this would be resolved in a hot fix release please let me know ASAP as I would need to have it approved this week. thx!

 

Comment by Anya [ 06/Jul/21 ]

Molly Driscoll// egerman see Dennis Bridges's message 

 

Comment by Molly Driscoll [ 08/Jul/21 ]

Anya & Dennis Bridges, I have contacted the library and asked them to get back to me no later than EOD tomorrow. Thanks for the update!

Comment by Molly Driscoll [ 08/Jul/21 ]

Dennis Bridges, MI State can wait until Juniper for this. Thank you!

Comment by Mikita Siadykh [ 21/Jul/21 ]

Dennis Bridges double checked, this issue has been fixed in scope of UISACQCOMP-39 and waiting deployment on juniper bugfest env

Comment by Dennis Bridges [ 26/Jul/21 ]

Closing as duplicate, UISACQCOMP-39 has passed testing in bugfest-juniper

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