Failure, typo in PostgreSQL DB Pattern causing CI Name with double "s"

Matthias H_
Tera Contributor

3 weeks ago

We updated our ServiceNow Instances (Yokohama Release) with the latest "Discovery and Service Mapping Patterns" V1.29.0 and wonder why suddenly Queries, Reports, Dynamic CI Groups etc. relying on the CI Name part "PostgreSQL" no longer work.

Failure is within that Pattern, that it creates CI Name prefix "PostgresSQL" - with a double "s" (left of the 'SQL').


Example from Pattern text  (red highlighted double "s")
The typo exist 3 times in the Pattern text

"....

on_true = set_attr {
"instance"
concat {
"PostgresSQL-port-"
get_attr {"entry_point.port"}
..."
Labels:
0 Helpfuls
  • 313 Views
1 REPLY 1

Tanushree Maiti
Tera Sage

3 weeks ago

Hi @Matthias H_ 

 

Raise a case to Servicenow as similar issue not mentioned in any problem (known error) of Yokohama release.

 

Refer: https://www.servicenow.com/docs/r/yokohama/release-notes/yokohama-patch-1.html

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:
0 Helpfuls