- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2014 07:08 AM
We have a request to make the time worked field read only to disable edits to the time. I tried making it a read only field, but that removes the timer completely.
Anyone know how to keep the timer running but disable edits to the hours/minutes/seconds fields?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2014 07:48 AM
open ui policy and short desc is "Time worked read only"
Regards,
Harish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2016 01:47 PM
This login is not valid. Can you share the content of the UI Policy instead? I tried a simple one on task.time_worked, Read only = true, but that is not working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2014 07:52 AM
This worked perfectly. Thanks to both of you for your suggestions.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-15-2019 06:02 AM
Using an UI Script with following script:
jQuery("input[data-type='timer'][type='text']").prop('disabled', true);
Looking for the three input fields ( hours, minutes, seconds ) and disable them.
The counter is running, stop button is still there and after save the time is correctly saved.
Thanks Harish Murikinati for never providing the content of your doing.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2019 11:27 AM
I couldn't quite get this working. Where did you call the UI Script?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-09-2019 02:28 PM
Shame on me for saying UI Script.
I wrote the code into a UI Policy in the "Execute if true" field, in my scenario only a specific group of agents should trigger this behavior.
You could also use the code in a Client Script on "onLoad".