Hi Ashok,
we have the same requirement: We transfer actual times to SAP, which can consume a lot of time, as SAP throws a lot of errors (wrong ILA, outdated ILA, overbooked ILA, ...). During this time, the "Time Reporting Periods" remain open, as the interface selects the to be transferred/processed periods by this status. So, users ignore the communicated deadline, "adjust" the timesheet. These figures may be picked up, or not. Its always a mess. Additional, we have the challenge, that differen Business Units transfer their Actuals independently - so its not only one "Deadline" and not only one person transferring actuals.
Currently we think of this solution:
-A Job, which revokes the "open for time entry" check of a resource - this undermines editing timesheets even in an open user session
-The job also sets a second checkbox "revoked open for time entry"
-The actuals are processed
-A second job searches for resources with a checked "revoked open for time entry", sets the "Open for Time entry" again and removes the check for "revoked open for time entry".
Positive:
- Jobs can be seperated by OBS for different Business Units
- Logic gurantees, that only revoked Open for time entries are later granted back and not more or less
- No adjustments in critical state of the transfer process
- Single "approved" adjustments or belated time entries are still possible per user, as the "open for time entry" checkbox can be manually set - the users must ask
Negative:
- User can not enter time in a future time period during the actuals processing timeframe (some users tend to enter missed actuals in a future time period)
But we still must check, if all Jobs and the interface pick up users, which are not "open for time entry" - if they are ignored, we may have to look for another solution of customize even more.
But Ill also have a look at your idea: "We can however, use a process to lock timesheet attributes but the button would still remain enable for user to click and then get to know that attributes are not editable." -> how would you select the to be processes timesheets and trigger these processes? I guess, each timesheet needs its own "lock" process, right?
-------------------------------------------
Original Message:
Sent: Aug 05, 2025 07:54 AM
From: Ashok Kumar Modi
Subject: Disabling "Adjust" button in Timesheets workspace For posted timesheets
Hello All,
A customer wants to disable "Adjust" button for the posted timesheet:

As far as I know, we cannot disable a UI button based on condition using Clarity's out of the box functionalities, or can we?
We can however, use a process to lock timesheet attributes but the button would still remain enable for user to click and then get to know that attributes are not editable. Which will be weird.
Since having the ability to adjust a timesheet that is even in the posted state is a feature and customer does not seem to use it, is there a way we can toggle off this feature?
All the suggestions are most welcome.
Regards
-Ashok
-------------------------------------------