IssueLandingPageTaskUtils not allowing override

[kirti114]

As part of IRM OOB configurations, there is a script include 'IssueLandingPageTaskUtils' which calls IssueLandingPageTaskUtilsBase.Its appllication is GRC: Common Workspace Elements

Usually, OOB script includes allow override and have OOB comment as below:

    /** Override base class functions here. **/

But, 'IssueLandingPageTaskUtils' script include does not have such a comment and override function is not working
How can we check if the script include is allowed for override?

Regards,

Kirti

[GouthamAnumolu]

hi @kirti114  , please check the "protection policy" of script include, if its 'none' you should be able to edit it. And IssueLandingPageTaskUtils extends utilsbase, so it can be used to override utilsbase methods.

[Tanushree Maiti]

Hi @kirti114 

As @GouthamAnumolu  mentioned please check the Protection policy.

Out-of-the-box script includes can have a protection policy of "read-only," which prevents direct modification. 

Also , refer this posts:

How to override a Script Include that is a high priority file type. 

override a method in script include 

[Lokesh Pandey1]

Hi Kirti,

Yeah, this can be a bit confusing. Not all OOB Script Includes in ServiceNow are actually meant to be overridden, even if they extend a base class.

In the case of IssueLandingPageTaskUtils, the key thing to check is how it’s being used internally. If the system is directly calling IssueLandingPageTaskUtilsBase (instead of dynamically using the child class), then any override you write won’t be picked up.

A couple of things you can verify:

• Check if the Script Include is exposed across scopes (Accessible from = All application scopes)
• Look at how it’s being instantiated in OOB code (if it’s new IssueLandingPageTaskUtilsBase(), override won’t work)
• Try adding a simple gs.info() in your overridden method and see if it ever gets triggered

Usually, when ServiceNow intends something to be overridden, they leave that comment (“Override base class functions here”) or design it as an extension point. Since that’s missing here, chances are this one isn’t designed for override.

In IRM Workspace stuff, a lot of these utilities are tightly controlled, so the safer approach is to look for extension points or alternative configs instead of overriding the Script Include.

Hope that helps.

Regards,

Lokesh