353 views

Description

A filter condition using any of the Fiscal Periods does not work because of the 'undefined' value generated in the resulting query, instead of the correct date/time.

 

Steps to Reproduce

  1. Go to the list view of the [incident] table.
  2. Enable session debug logs.
  3. Build a filter such as: Created is <pick a fiscal option such as "This fiscal year">.
  4. Observe the query generated is not correct. It has create_at = undefined instead of actual date/time values. I.e.:
    task0.`sys_created_on` >= 'undefined' AND task0.`sys_created_on` <= 'undefined'.
  5. Notice the Business Calendar API running as a background script also returns 'undefined':
    gs.info(sn_bc.GlideBusinessCalendarUtil.isLegacySchedule('cmn_schedule'));
    [0:00:00.056] Script completed in scope global: script
    Script execution history available here
    *** Script: undefined

 

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.

 


Related Problem: PRB1380054

Seen In

SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Fixed In

New York Patch 7
Orlando Patch 1
Paris

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-03-27 09:52:36
Published:2020-03-10