The Staffing module aggregation values might not be correct due to calendar exceptions (MSSQL only)
search cancel

The Staffing module aggregation values might not be correct due to calendar exceptions (MSSQL only)

book

Article ID: 270916

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

The Staffing module aggregation values might not be correct due to calendar exceptions (MSSQL only)

STEPS TO REPRODUCE: (This is only reproducible in MSSQL databases)
1. Create a Resource
2. Go to his profile and change the Availability from 8.0 to 8.40
3. Go to his calendar and set the following days as non-working: 1st and 15th of August, 1st of November
4. In Classic UI, Create an application with dates 01.01.23 till 30.12.23
5. Assign the resource above to the application with 15% default allocation
6. In Classic UI, Create a project with dates 02.07.22 till 30.12.23 
7. Assign the same resource with a 100% allocation. If requested, overallocate
8. In Classic UI, Create a project with dates 01.07.23 till 04.01.24 
9. Assign the same resource with a 20% allocation. If requested, overallocate
10. In Classic UI, Create a project with dates 01.05.23 till 31.12.23 
11. Move to Modern UX and set the Unit of Measure to Days (same issue with hours)
12. Assign the same resource to the project in step 10 through the Staff tab
13. Set the Default Allocation % to 0%
14. Populate the allocation values on the Per Periods grid with specific values
15. Go to the Staffing workspace Allocations Timeline and or Staff Grid
16. Look at the Aggregated values and the individual investment values

Expected Results: The aggregated allocation values to be correct and in sync with the investment data.
Actual Results: The aggregated values are not correct for the month of November. The values are off for 1 day due to the calendar exception of the 1st of November

Environment

Clarity 16.x and MSSQL databases only

Cause

This is caused by DE77143

Resolution

This is currently being analyzed by Engineering