34 views

Description

On the Service Portal's System Status page, the dates do not display correctly if the date format has changed to "dd.MM.yyyy". The System status page should show the last 5 days, even if the date format has been changed.

Activating the Task-Outage Relationship plugin in early Helsinki causes Service Portal errors in the browser.

 

Steps to Reproduce

  1. Go to sys_properties.list.
  2. Filter for Name = glide.sys.date_format.
  3. Open the system property and set it to dd.MM.yyyy (by default, it is "yyyy-MM-dd").
  4. Save the system property.
  5. Go to the System Status page in the Service Portal: https://<instance_name>.service-now.com/sp?id=services_status

Notice the dates in the status History shows the last 5 months, not the last 5 days as expected.

 

 

  1. Navigate to System Definition > Plugins.
  2. Find and open the Task-Outage Relationship plugin.
  3. In Related Links, click Activate/Upgrade.
  4. Click Activate.
  5. Click View Plugin List.
  6. Navigate to Service Portal > Service Portal Home.
  7. Open your browser console.
  8. Click the Current Status more information link.
  9. An unresponsive script warning is displayed:



  10. Click Continue.
    Notice the errors in the browser console:

    "Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: date in ::data.dates, Duplicate key: string:Invalid date, Duplicate value: Invalid date
    http://errors.angularjs.org/1.5.3/ngRepeat/dupes?p0=date%20in%20::data.dates&p1=string:Invalid%20date&p2=Invalid%20date
    minErr/<@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:6202:8
    ngRepeatAction@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:17532:7
    $watchCollectionAction@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:14043:1
    oneTimeListener@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:13485:1
    $RootScopeProvider/this.$get</Scope.prototype.$digest@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:14112:1
    $RootScopeProvider/this.$get</Scope.prototype.$apply@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:14206:1
    done@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:11010:26
    completeRequest@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:11120:1
    requestLoaded@https://helsinki.service-now.com/scripts/js_includes_sp.jsx?v=04-14-2016_1514&lp=Wed_Aug_17_04_09_16_PDT_2016&c=5_252:11081:1
    "


Workaround

This problem was fixed in Helsinki Patch 3 and onwards. No workaround is applicable on earlier releases.

 


Related Problem: PRB675919

Seen In

Helsinki
Helsinki Patch 0 Hot Fix 1
Helsinki Patch 1

Fixed In

Helsinki Patch 3
Istanbul

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-03-20 04:15:57
Published:2018-03-20