Invoice approved but no voucher created

Description

Overview: An invoice appears to be approved and paid successful but does not have approval date or voucher created etc.

Steps to Reproduce: Unknown - files and logs attached

  1. Log into Cornell production environment

  2. TBD

Expected Results: Invoices have vouchers and needed approval information populated. If voucher is not created invoices are NOT approved

Actual Results: Invoice are approved and paid but do not have the appropriate data and voucher records generated

Additional Information: logs attached
URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

7

Checklist

hide

TestRail: Results

Activity

Show:

Dennis BridgesSeptember 27, 2021 at 2:31 PM

 That issues was released with Juniper. I was going to wait and see if the library continued to encounter this issue after the upgrade. However, I can resolved this in the mean time and open it again if the problem persists. thx

Debra HowellSeptember 27, 2021 at 2:23 PM

FROM SUPPORT SIG: https://folio-org.atlassian.net/browse/MODINVOICE-294 is now closed. Does that resolve this bug?

Dennis BridgesAugust 30, 2021 at 5:12 PM

 the only way we've been able to reproduce the result is by directly using the APIs. We have created a separate story in  to add new logic that will make it impossible to use the APIs to directly pay an invoice. That should prevent this from occurring in any circumstance.

That said, we have not been able to confirm that this is what is happening in the customer instance (ie. that we have correctly reproduced the issue) so I'm thinking this issue should remain open in the mean time and be resolved when we can confirm it is no longer occurring in their instance. Also, to my knowledge it is only intermittently affecting 1 institution at the moment so I'm not sure it can be considered a P1?

 should the priority of this issue be lowered? It is without doubt a problem that these invoices can't be deleted but it seems they can be recreated and processed. As mentioned this can not be reproduced elsewhere and is not occurring consistently in the customer instance. We have yet to establish a pattern here...

I recommend we keep this open until  is resolved. We then close this issue and if somehow it is still occurring in their instance we will need to open a new bug. However, this is actually occurring in the Cornell instance it should be blocked by this change. Blocking it should make it much easier to pin point the origin.

Debra HowellAugust 30, 2021 at 2:22 PM

FROM SUPPORT SIG:  What should the Support SIG do with this ticket? Is it still a BUG?

Mikita SiadykhAugust 19, 2021 at 2:44 PM

moved to blocked as we can't reproduce and additional info is required

Won't Do

Details

Assignee

Reporter

Priority

Sprint

Development Team

Thunderjet

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 5, 2021 at 4:40 PM
Updated December 6, 2023 at 10:52 PM
Resolved September 27, 2021 at 2:31 PM
TestRail: Cases
TestRail: Runs