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

[Matthias H_]

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"}
..."

[Tanushree Maiti]

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

[Matthias H_]

A ServiceNow case was already opened by our developer.

Until the official fix we'll implement a temporary fix of the Pattern