Notifications

28 views

Description

There is support for SCOM 2019 In Orlando:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0809876

It says:

Supported versions:
2007 – version 6.1.7221.0
2012 – version 7.1.10226.0
2016 – version 7.2.117190 and 7.3.13261.0
2019 – version 10.19.10050.0

however following documentation to set up the connector it mentions only in step 8 e.

scom_version It is mandatory to specify the SCOM version, select from 2016, 2012, or 2007.


If we are going to support 2019 then we should allow 2019 to be added. Which means that we need to enhance the documentation and the business rule where it checks the input for valid value in the scom_version field. If you enter 2019 and then hit: 'test connector'

The business rule: Validate inputs

will generate an error thus:

SCOM version is not defined or invalid

Steps to Reproduce

1) Get an Orlando instance
2) Follow documentation:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0809876
3) Setup scom_version field with a value of: 2019
4) save configuration
5) Click on 'test connector' at the top right of the form
6) An error is generated see: scom_version_error.PNG

Workaround

There is a business rule here:

https://<instance>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=32bd5371d73221008de76ccf6e610318

the code for this is in there:

if (connectorVal.next()){
if (connectorVal.getValue("value") === "2007" || connectorVal.getValue("value") === "2012" || connectorVal.getValue("value") === "2016")
isDefined = 1;
}
if (isDefined == 0)
errorAndAbort("SCOM version is not defined or invalid");

You can see the error above. I think all you need to do is add another OR (||) for 2019 for example:

if (connectorVal.getValue("value") === "2007" || connectorVal.getValue("value") === "2012" || connectorVal.getValue("value") === "2016"|| connectorVal.getValue("value") === "2019")

OR customer needs to put valid value e.g. 2016 in scom_version

 

 

 

and it should be ok


Related Problem: PRB1402108

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Discovery and Service Mapping - 201908

Intended Fix Version

Paris

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-05-19 09:06:08
Published:2020-05-01