Time worked field timer not working when field is read-only in Australia release (works in Zurich)

HarshaSeetha
Tera Contributor

Hi,


I’m facing an issue with the Time Worked field on the Incident form and would appreciate your help.

 

What I have done:

  • I brought the Time worked field onto the Incident form.
  • Then, I configured the Time Worked field to be read-only(using UI Policy) on the Incident table.

Issue:

  • When the field is marked as read-only, the timer inside the Time Worked field stops working (it does not count time) in the Australia release Patch 2 instance.

HarshaSeetha_0-1782296988800.png

 

Observation:

  • I tested the exact same configuration in a Zurich release Patch 2 instance, and there the timer continues to work correctly, even when the field is read-only.

HarshaSeetha_1-1782296901323.png

 

So,

  • Is there any known limitation or behavior change in the Australia release regarding the Time Worked field timer?
  • Is there a recommended way to make the timer work while keeping the Time worked field read-only?
  • Are there any scripts, UI policies, or configurations that could fix this?

Has anyone come across this ? Any suggestions to fix or work around, this would be really helpful.

 

Thanks in advance!

6 REPLIES 6

Hi @HarshaSeetha 

 

Did you check if you have any  UI policy to make that field ReadOnly.

 

https://www.servicenow.com/community/developer-forum/disable-edit-on-time-worked-field/m-p/1454206

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Hi @Tanushree Maiti ,
Yes, I checked, UI Policy is making the Time Worked field read-only, and that is expected for my requirement.
My need is for the timer to run even when the time worked field is read-only.

  • In Zurich, the timer works fine even in read-only
  • In Australia, it stops working when read-only