- Earned Value: On Level of Effort (LOE) and Earned as Spent (EAS) EVT work packages, Dash360 was improperly calculating earned value for successive reporting periods. It was duplicating some months of values across months. This has been corrected.
- Estimating → Cost Estimating Form: If you have Contingency setup in the Registry only at the WP level, then the Labor, Non-Labor or Travel listings no longer have Contingency in their column chooser.
- Admin → Projects → Edit Project → Lock Project: When you lock a project, that project should not be allowed to be changed. There were a couple of areas that still allowed changes including Notebook Categories, Adding a Rateset / Rate or importing data. The system has been updated to not allow anything to be changed if it is attached to a locked project.
- Estimating → Cost Estimating Reports → Cost Summary Report: Added the Cost Class field into the column chooser. Also fixed a bug where a bad error message would appear if you selected a cost class that had no resource assignments. Now, the system tells you there are no Resource Assignments in that cost class.
- Estimating → Staffing Plan Report: The Excel export sometimes would not download all data if the data in the first column was the same in the export. This has been corrected so that all data now downloads properly.
- Estimating → Cost Estimating Form / Earned Value Reporting Periods: Dates in these two sections were sorting based on the text of the date instead of sorting by the year first. This has been corrected.
- Admin → Codes: When deleting a Format 1030 code that was attached to Resource Calculations, the system would throw an ugly error. Now, it tells the Admin how many places this code is used and makes you confirm if you want to still delete it. If you select yes, then the code is deleted.
- Admin → Projects → Variance Thresholds: The Add a Threshold button could sometimes get hidden so the user could not add or edit a threshold. This has been fixed.
- Risk Register: On small screen, the filter box for the Risk Register Table section did not always appear on top of the data grid. This kept the user from being able to properly select data.
- Dashboard Designer: Added the % Complete field to the Schedule datasource so it can be used in dashboards.
- Schedule: Changed the default system view for the Schedule to be grouped by WBS and then by Work Package and then sorted ascending by Start Date.
- Import Schedule: The Uncertainty Classes fields are no longer required in the Schedule import.
- Admin → Projects: When changing a WBS code, the WBS Dictionary entries were not being updated to the new code. This has been fixed.
- CMB-S4 / Berkley SAML integration was broken by the .NET 6 upgrade. It has now been corrected.
- Schedule: When using the Add a Milestone or Task form in the Schedule, it now follows these business rules:
- If you enter a % complete, then the Start Date must be on or before the current schedule status update date (i.e. data date). Otherwise, the system needs to throw an error.
- If a % complete < 100%, then there must be an Expected Finish Date later than the current schedule status date.
- If an activity was scheduled to finish by the data date and did not, a Revised Expected Finish is required.
- If an activity was scheduled to start by data date and did not, a Revised Expected Start and Expected Finish is required.
- If an activity is 100% Complete, an Actual Start and Actual Finish must be provided. The Actual Start and Finish dates must be on or before the current data date.
- If an activity has an Actual Start Date on or before the data date, then the %Complete needs to be greater than 0.