| Change Category | Change Summary | Change Description | Change Type | Change ID |
| General Support | Project code description is displaying instead of the project code name when the project code is looked up and returned to the accounting line | We fixed accounting lines on several documents to display the Project Code Name instead of the Project Code Description when Project Code is returned to the document from a lookup. This fix was contributed by University of California Irvine. | Bug | FINP-3690 |
| General Support | If the user populates either Billing Frequency or Invoicing Option on an Award, then both are required. | We added validation to require both Billing Frequency and Invoicing Option fields on an Award if either field is populated. If an Award is setup for Contracts & Grants Billing, both pieces of data are needed. | Bug | FINP-4100 |
| General Support | Error when running upcomingMilestoneNotificationJob in an Oracle environment | The MilestoneDaoOjb class was using java.util.Date to query the database, which produces a date conversion error when used with Oracle databases. We replaced that usage with the correct usage of java.sql.Date. We also implemented a checkstyle rule that doesn't allow java.util.Date to be imported in classes in a dataaccess package (with a small number of exceptions that we plan to eliminate over time). | Bug | FINP-4091 |
| Services | Error when viewing Milestone or Predetermined Billing Schedule inquiry from a Contracts & Grants Invoice | We fixed the inquiry links for Milestone and Predetermined Billing Schedules on Contracts & Grants Invoice documents. | Bug | FINP-4149 |
| Services | Milestone and Predetermined Billing Schedule validation that total scheduled does not exceed the award total should not include inactive rows | In Milestone and Predetermined Billing Schedules, we excluded inactive rows from the validation which confirms that schedules do not exceed the award total amount. | Bug | FINP-4109 |
| Incremental Refactor | Updated dropdowns | In an effort to decrease the front-end's reliance on bootstrap we have migrated the dropdown components in the header to react based components. | Improvement | FINP-4028 |
| Incremental Refactor | Refactor VendorCreditMemoInitTabReferenceNumberValidation to eliminate bitwise xor | The validate method in VendorCreditMemoInitTabReferenceNumberValidation made use of the bitwise xor operator (^) which is not commonly used and could be confusing. We replaced the logic with something more straightforward. | Improvement | FINP-3557 |
| Lookup Refactor Improvements | Unable to access Batch File Lookup from Batch Schedule | We fixed the Batch File Lookup link from Batch Schedule. | Bug | FINP-4113 |
| Lookup Refactor Improvements | Use consistent HTML IDs for control elements on new lookup page | We added consistent HTML IDs on all control elements in the new lookup pages to better support 3rd party AFT (automated functional testing). | Improvement | FINP-4106 |
| Lookup Refactor Improvements | Improve the layout engine for new lookup framework | We improved the layout engine for the new lookup framework to allow search criteria supported by radio buttons to display on the same row as other fields. | Improvement | FINP-4104 |
| Lookup Refactor Improvements | Use <label> element for datepicker labels on lookup pages for a11y | On date pickers in new lookup pages, we updated the input labels to be HTML <label> elements rather than <div> elements to improve accessibility. | Improvement | FINP-4045 |
| New Tools & Testing | Refactor some kfs-fp tests | We removed the KualiTestBase dependency from some FP tests and cleaned up some old comments and commented out code in a couple FP tests. | Improvement | FINP-4115 |
Comments
0 comments
Please sign in to leave a comment.