Changes on ".NET Application" pattern in Quebec causing Service Map's discovery to update different applications into .NET application


Description

In Quebec, we introduced new fallback logic to get the version in .NET Application pattern.
This is the fallback step:
=====
9. If version is empty - find .NET version
=====
This step's validation is not strong enough as it might catch exception on the response. Example: "Cannot open file xxx"
This response is then set as the version and the logic thinks it is a .NET application.
As a result, your previous application would be replaced with .NET application flow. This is incorrect.

Steps to Reproduce

  1. Build a service map with discovery that contain application like Tomcat in Paris instance.
  2. Upgrade instance to Quebec.
  3. Change step 9 of .NET application pattern so that it will return the version's value with invalid string. Example: "Cannot open file".
  4. Observe that your previous Tomcat application is now replaced with .NET application.

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

If you can't wait till then, you can import attached file sa_pattern_28d607dbfead4be3887c843814451202.xml
The file contain extra step on .NET Application pattern to validate the version.
After that, run discovery on Service Map and check if the applications that got replaced earlier are now correct.


Related Problem: PRB1515979