Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Caller Location Timezone set on the SLA definition for [incident_task] table is not working - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Caller Location Timezone set on the SLA definition for [incident_task] table is not working
KB0824760

Caller Location Timezone set on the SLA definition for [incident_task] table is not working


1254 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Caller's Location's Timezone set on the SLA definition for incident_task table is not working:

                           

Cause

There is no caller field existing on the Incident Task table, it is only available in the Incident table.

The system timezone is set on the Task SLA record, but the expectation would be the incident's caller's location's timezone to be set on the Task SLA record, as the Caller field has been configured on the [incident_task] table by dot walking incident.caller.

Review the 'SLATimezone' Script Include /sys_script_include.do?sys_id=e35516289f3200008f88ed93ee4bcc66 , which has the function to determine which field should be considered the Caller field:
                         


For HR records this should be the [opened_for] field, and the code sets this for the non-scoped HR tables only, not for the scoped HR tables. It will default to the [opened_by] field which could cause an incorrect timezone to be used:

                  switch (task_type) {
                  case 'incident':
                  return task.caller_id;
                  case 'incident_task':
                  return task.incident.caller_id;


Resolution

Modify the above script include to include the following lines of code:

case 'incident_task':
return task.incident.caller_id;


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.