Title: Investment Allocation Job Fails on NPIOs when start/finish date is far out in past/future
Summary of Issue:
This issue occurs when allocation hours are around 100,000 hours which is caused by Non Project Investment Objects (NPIOs) having a Start / Finish date far out in the past / future. The job fails with the following error in the bg-ca.log:
Exception processing InvestmentAllocationJob java.lang.NullPointerException.
Steps to Reproduce:
- Create a Non Project Investment with a Start / Finish date far out in the past / future (example, Finish date of 2085).
- Run the Investment Allocation job.
Note: This typically occurs when a user mistakenly enters a typo in the Finish date (Example, enters a project finish date ending in year 3015 instead of 2015)
Expected result: Job completes successfully.
Actual Result: Job fails with a NullPointerException populated into the bg-ca.log
Move the Start / Finish Dates to be within 1/1/1990 and 1/1/2025
You can run the following query to see if any of your investments fall outside the recommended range:
|select distinct schedule_start, schedule_finish, id from inv_investments|
|where schedule_start <= '01-jan-1990'|
|or schedule_start >= '01-jan-2025'|
|or schedule_finish <= '01-jan-1990'|
|or schedule_finish >= '01-jan-2025'|
Resolved in Clarity 13.3