Bug Fix Notes
|
Issue |
Description |
|
CAP-6242 | Unable to edit project with single quote |
An issue was found where you were not able to edit the project if the project contained a single quote. This has been resolved. |
|
CAP-6298 | Deleting Matched item Not Re-opening |
An issue was found where deleting the invoice line item that had closed PO item did not re-open the PO item after deletion. This has been resolved. |
|
CAP-6183 | Prevent duplicate invoice number on save |
An issue was found where if the invoice submitter receives duplicate invoices (not assigned to any vendor) in different timestamp, they were able to submit duplicate invoice after setting the vendor on the invoice. This has been resolved. |
|
CAP-6211 | Incorrect product lookup with InvoiceCapture |
An issue was found where the product lookup with invoice capture logic was incorrectly done by looking at the ad-hoc rather than internal catalog only. This has been resolved. |
|
CAP-6217 | Unvoided PL doesn’t show up in submitter’s queue |
An issue was found where the unvoided packing list did not appear back in the submitter’s in-progress queue. This has been resolved. |
|
CAP-5007 | CDim fields disappear after clicking header save |
An issue was found where if the requisition submitter fill out the allocation details with custom dimension values and then decides to edit/save the requisition header section, the selected custom dimension fields would get removed. This has been resolved. |
|
CAP-5725 | Home page - Missing NLA Required Message |
An issue was found where the No Limit Approver Requirement message on the home page was missing when there are no No Limit Approver in the SAF approval chain. This has been resolved. |
|
CAP-5938 | Users with InvoiceStatusReport permission can’t see reporting tab |
An issue was found where if the user with just a Invoice Status Report permission did not have access to the Reporting tab. This has been resolved. |
|
CAP-6198 | Total is not displayed in the vendor email |
An issue was found where the emailed PO did not have the proper PO total amount in the email. This has been resolved. |