Dear Team,
I've identified a critical system limitation in the work dispatch timesheet entry process:
### Key Observations
- The current dispatch work entry lacks hour validation controls
- Unlike standard timesheet entries, dispatch work allows exceeding the standard 9-hour daily limit
- Once dispatch work is entered, the entry cannot be deleted though it can be made blank or modified.
Please refer the attachment
Hello,
"- The current dispatch work entry lacks hour validation controls"
>What type of control are you talking about?
"- Unlike standard timesheet entries, dispatch work allows exceeding the standard 9-hour daily limit"
> On your capture you can see that you've exceeded the time limit: it's in red, the behavior is the same as before
"-Once dispatch work is entered, the entry cannot be deleted though it can be made blank or modified."
> It's possible to remove the input, just set 0 in the “dispatch work” dialog.
If you'd like to see any improvements to this new feature, please don't hesitate to contact us, so you can finance them.
Have a nice day
Maxca
Hi,Regarding your queries:
What type of control are you talking about?
- We have configured an 8-hour limit in the "Global Parameters" under the "Work Time" tab. However, this setting does not prevent users from entering more hours in the dispatch hour (detailed work entry) on the timesheet.
On your capture you can see that you've exceeded the time limit: it's in red, the behavior is the same as before
- While the system highlights exceeded time limits in red, it does not restrict saving entries when using the dispatch hour feature. Notably, after entering dispatch hours, there is no need to click the save button on the top right of the timesheet, allowing entries to be saved without validation.
It's possible to remove the input, just set 0 in the “dispatch work” dialog
.- Although we can set the dispatch work to zero, the "List of Works" report still displays a row with a zero entry, which may lead to cluttered reports.
Please find the attached screenshots for your reference.
Hello,
We have configured an 8-hour limit in the "Global Parameters" under the "Work Time" tab. However, this setting does not prevent users from entering more hours in the dispatch hour (detailed work entry) on the timesheet
> This parameter has never limited input! You can try in previous versions.It does not limit the number of hours that can be worked to make up for lost time.
"While the system highlights exceeded time limits in red, it does not restrict saving entries when using the dispatch hour feature. Notably, after entering dispatch hours, there is no need to click the save button on the top right of the timesheet, allowing entries to be saved without validation."
> You assume that the number of hours cannot be exceeded, but this is not the case. The red and green colors indicate whether or not you have exceeded the time limit.
"Although we can set the dispatch work to zero, the "List of Works" report still displays a row with a zero entry, which may lead to cluttered reports"
>I've tested it, and I can't reproduce your case where you have 0 hours. So this is a bug, and more information on how to reproduce it and fix it is welcome.
We have configured an 8-hour limit in the "Global Parameters" under the "Work Time" tab. However, this setting does not prevent users from entering more hours in the dispatch hour (detailed work entry) on the timesheet... While the system highlights exceeded time limits in red, it does not restrict saving entries when using the dispatch hour feature.
the number of hours entered in the global settings does not limit the time gap at all. It is only used to calculate deadlines and indicators...
To limit your hours go to the resource screen and fill in the corresponding fields.
Notably, after entering dispatch hours, there is no need to click the save button on the top right of the timesheet, allowing entries to be saved without validation.
indeed, there is no need to click the save. It is an error. Ticket recorded
- Although we can set the dispatch work to zero, the "List of Works" report still displays a row with a zero entry, which may lead to cluttered reports.
We do not reproduce. Have you tried on the demo if you reproduce this problem? No errors in the logs?
It may be useless, but from time to time, we deco, we clear the cache and we reco.
Yes I saw your attachments and it didn't correspond to the right parameter so excess input will be corrected.
Let us know about the report



