Financials Production Release 2018.11.08

Change Category	Change Summary	Change Description	Change Type	Change ID
Services	Do not allow Contracts & Grants Invoice to be created if total will be negative	Previously, Contracts & Grants Invoices could be created for negative total amounts. With this change, the total must be greater than zero for the invoice to be successfully created. An error message will appear on the screen when attempting to create a Contracts & Grants Invoice with a negative amount, and also in the Contracts & Grants Invoice Error Log.	Improvement	FINP-4281
Services	Prevent the actual completion date on Milestone Schedules from being later than today	We modified the Milestone Schedule to prevent future actual completion dates.	Improvement	FINP-4236
Services	Add new permissions that give authorized users the ability to edit existing milestone actual and estimated completion dates and predetermined billing scheduled date	We added the following permissions to control who can edit specific fields on milestone and predetermined billing schedules. Roles that can only edit the date fields, can also add new milestones/bills within a schedule. We will be fixing that in a future release and recommend that the second set of permissions below not be assigned until that issue is resolved. Assign the following permissions to the role that can edit, copy and create new to maintain current behavior: * FINP-4129-P1 - modify milestone number * FINP-4129-P2 - modify milestone description * FINP-4129-P3 - modify milestone amount * FINP-4129-P4 - modify PDBS bill number * FINP-4129-P5 - modify PDBS bill description * FINP-4129-P6 - modify PDBS bill estimated amount * FINP-4129-P7 - create new, edit and copy milestone schedules * FINP-4129-P9 - initiate Milestone Schedule * FINP-4129-P10 - create new, edit and copy predetermined billing schedules * FINP-4129-P12 - initiate Predetermined Billing Schedule Assign the following permissions to the role that can only edit the milestone and pdbs date fields - we recommend not assigning until the ability to create new milestones/bills within a schedule is prevented. * FINP-4129-P8 - edit existing Milestone records * FINP-4129-P9 - initiate Milestone Schedule * FINP-4129-P11 - edit existing PDBS records * FINP-4129-P12 - initiate Predetermined Billing Schedule	Improvement	FINP-3380
General Support	Instrument Type Code character limit field needs to match the table	We fixed an issue where the system allowed a user to put in ten characters in the field but the table only takes four.	Bug	FINP-4274
General Support	Fix duplicate error messages on Intra-Account Adjustment (IAA) document	Error message when adding accounting lines to Intra-Account Adjustment (IAA) documents were displaying twice. This change ensures this message is not duplicated.	Bug	FINP-4195
General Support	Billing Frequency and Invoicing Option defaults to blank on new awards	New awards now default to having blank billing frequency and invoicing options.	Bug	FINP-4145
General Support	Upgrade to Rice 2.6.3	We upgraded to Rice 2.6.3 which included: # Oracle SQL fix for Stuck Documents job # Library upgrades: dependency-check, jackson, ehcache, jetty, javax.ws.rs-api, bcprov and spring # Added a suppression for CVE-2018-1270. Unused spring framework functionality # Remove duplicate dependencies from pom.xml # Added ignored test classifer (rice-krad-data) # New demo keystore	Improvement	FINP-4072
Incremental Refactor	Update syntax in purap spring files	We updated the specified spring files to use p syntax. This syntax is more modern and concise and can enable the IDE to help you by pointing out properties that are available or problems if you have a typo in a key or ref you think exists. This update is similar to the update in FINP-3858. There should be no functional impact for this commit. The diff contains a lot of changes. By isolating this update we are attempting to make it easier to ignore these non-functional changes.	Improvement	FINP-4223
Incremental Refactor	Update syntax in ld spring files	We updated the specified spring files to use p syntax. This syntax is more modern and concise and can enable the IDE to help you by pointing out properties that are available or problems if you have a typo in a key or ref you think exists. This update is similar to the update in FINP-3858. There should be no functional impact for this commit. The diff contains a lot of changes. By isolating this update we are attempting to make it easier to ignore these non-functional changes.	Improvement	FINP-4222
Incremental Refactor	Update syntax in kns spring files	We updated the specified spring files to use p syntax. This syntax is more modern and concise and can enable the IDE to help you by pointing out properties that are available or problems if you have a typo in a key or ref you think exists. This update is similar to the update in FINP-3858. There should be no functional impact for this commit. The diff contains a lot of changes. By isolating this update we are attempting to make it easier to ignore these non-functional changes.	Improvement	FINP-4221
Incremental Refactor	Update syntax in ec spring files	We updated the specified spring files to use p syntax. This syntax is more modern and concise and can enable the IDE to help you by pointing out properties that are available or problems if you have a typo in a key or ref you think exists. This update is similar to the update in FINP-3858. There should be no functional impact for this commit. The diff contains a lot of changes. By isolating this update we are attempting to make it easier to ignore these non-functional changes.	Improvement	FINP-4219
Lookup Refactor Improvements	Edit and Copy links display on the refactored look ups for users who don't have permission to create or modify records	The old lookups use the Initiate Document and the Create / Maintain Records permissions to determine who has access to take action. The new lookups will use the Create / Maintain Record permissions to determine if the user has access. To address the immediate problem, we modified the new lookups to also use the Initiate Document permission if a Create / Maintain Record permission doesn't exist. Once we have refactored all the lookups and the Maintenance Document framework to use the Create / Maintain Record permission, we will remove the Initiate Document permission from the Maintenance Lookup and Document frameworks. NOTE: The fallback initiate document permission was removed in the 6/20/2019 release with FINP-5034.  Create / maintain record permissions will need to be created for refactored lookups.   https://kuali-financials.zendesk.com/hc/en-us/articles/360038741793-Refactored-Lookups-and-Create-Maintain-Records-permission	Bug	FINP-4302
Lookup Refactor - Similar to Account Type	A few Accounts Receivable lookups have been updated to the new refactored framework	The following Accounts Receivable lookups have been updated to the refactored lookup framework: Collection Activity Type, Customer Address Type, Customer Type, Method of Invoice Transmission, and Payment Medium.	Improvement	FINP-3772
Design Improvements	Improve visual alignment	Improvements to the test environment indicator bar.	Improvement	FINP-4209