Timesheet validation issue with days marked as Non-workdays
search cancel

Timesheet validation issue with days marked as Non-workdays

book

Article ID: 278377

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Steps to reproduce:

1. Create a new Timesheet validation in the Modern UX:
    a. Modern UX -> Administration -> Timesheets -> New Rule
    b. Populate Rule Name
    c. Populate Error Message
    d. Against "Time Entry Error Conditions":
        i. Choose 'Sum of Entries' -> Add Condition -> Daily Sum
        ii. Set the condition as "Is Less Than" 8
    e. Click on Create
2. Change a workday to a non-workday:
    a. Classic UI -> Home -> Resources
    b. Choose a resource. Click on it
    c. Navigate to the "Calendar" tab
    d. Choose a date. Use the checkbox within that date and set the checkbox to true. Click on "Make Non-Workday" button
3. Verify if the resource from step 2 is enabled for Timesheeting:
    a. Navigate to Classic UI -> Home -> Resources -> Click on the Resource -> Properties -> Settings
    b. Verify:
        i. Track Mode = PPM
        ii. Open for Time Entry = True
4. Verify that this resource is assigned to a Task in a Project. If not assigned already, then:
    a. Classic UI -> Home -> Projects -> Create a Project -> Add the resource from step 2 under 'Team' tab
    b. Create a Task under 'Tasks' tab
    c. Assign the resource to the Task created above (Click on the task -> Add resource -> Assign)
5. Check the functioning of the validation:
    a. Modern UX -> Timesheets
    b. Open the timesheet of the resource from step 2(b)
    c. Add Tasks -> Choose the Project/Task from step 4
    d. Enter 9 hours on all workdays except for the date used in step 2(d)
    e. Submit

Expected Results: Validation defined in Step 1 does not trigger.

Actual Results: Validation defined in Step 1 does not let the timesheet to be submitted.

Environment

Version: 16.2.0.

Cause

DE79381

Resolution

DE79381 is fixed in version 16.2.1.

Additional Information

Workaround:

Use the "Is Between" operator instead of "Is Less Than" in the rule. Provide "0.000001" to "7.999999" as input to it.