search cancel

New UX Timesheets able to be created Prior to 'Hire Date'

book

Article ID: 134206

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

In the New User Experience (UX), if a user clicks on a timesheet for a time period, then a date of hire is added, they are able to create / edit any timesheet starting from the time period the timesheet they first clicked on and any future timesheets even if they are prior to their date of hire. 

STEPS TO REPRODUCE

  1. Create a new user in Clarity (ensure they have Timesheets - Navigate access at the global level and Resource - Enter Time access at the instance level to their account
  2. Ensure the user is Open for Time Entry with track mode of PPM
  3. Log in to the New UX as the user created in step 1
  4. Click on the Timesheets icon and click on the time period of May 27 - Jun 2 (2019) for Resource A
  5. Log in as an Administrator and change the hire date for Resource A to 6/17/19
  6. Log in as Resource A again and click on the May 27 - Jun 2 time period in the New UX

Expected Results: User gets the below error when trying to access any timesheet prior to June 16.

com.niku.union.odf.exception.ODFValidationException: TMA-0906: Resource xxx, xxx starts on XX/XX/XX. Creating a timesheet requires an existing, active, resource who is open for time entry and has a time track mode set.

Actual Results: In New UX user can see all timesheets and can open and able to edit timesheets for May 27 - June 2, June 3 - June 9, and June 10 - Jun 16 (should only be able to edit timesheets starting from their hire date (June 17 to Jun 23)

Notes:

  • The user does not have to create the timesheet for the issue to happen, only access the time period the timesheet belongs to
  • In Classic Clarity, you cannot see the timesheets for time periods prior to the hire date. (If a hire date is mid time period, by design in Classic, the user is able to add time for any days in that time period even if prior to the hire date)

Environment

Component : CA PPM SAAS TIME MANAGEMENT

Resolution

DE49826 resolved in 15.7.

  • As part of this fix, a user will not be able to submit the Timesheet if it contains any entry prior to their hire date. (This is an extra check added which impacts users with a hire date that is mid time period, and this Modern UX behavior is different then Classic functionality mentioned in the Notes section above). 

Workaround:

When a user is created, add a hire date in the future as a placeholder (at least one timesheet period in advance) to prevent anyone from being able to click on the timesheets.