SLA Definitions not triggering for new scoped app

[Shane J]

I've created a new scoped app with some SLA definitions of of the custom table I extended off Task.  None of those Definitions are triggering.

When I try to run the SLA Validation UI Action I see this error message:

java.lang.NullPointerException

In the log, I see this error:  

wfv_gr.condition:;undefined

I've gone through everything here and none of it applies:  https://hi.service-now.com/kb_view.do?sysparm_article=KB0598456

Nothing of any value comes up with a Google search:  https://www.google.com/search?q=servicenow+sla+java.lang.NullPointerException&rlz=1C1GCEA_enUS834US8...

I thought maybe the issue was due to Cross Scope but we have other scoped apps that don't seem to be having any issues.

Anyone else seen this before and know how to fix?

[Joaquin Campos]

Hi Shane,

I'd then review your SLA definition.

Just in case, this is the SLA definition that I created just for testing purposes:

This is the stop condition:

And this is the result of SLA definition validation. No errors on my side:

Regards:

Joaquín

[Shane J]

You'd have to pick a record (top left) to see the error.

[Joaquin Campos]

Hi Shane,

I just had to include the audit flag for the custom table and then it works for me.

Please refer to this link to see how to include the audit flag:

Regards:

Joaquín

[Shane J]

Auditing was enabled from the get go:

[Shane J]

Well with SN HI, determined the issue with the lack of triggering.

When we create a new SLA, we get an Interceptor that asks if it's for Contract or SLA Offering - Contract is correct and SLA Offering is not (in this case).  These options create SLA Def on completely different tables, though they appear to be the same.

The SLA Validation UI Action still doesn't work though.