After making changes to the service-desk-ticket-config.xml file for the Spectrum Service Desk integration errors were reported in OneClick.

Related Issues/Questions:
Receiving errors when loading service-desk-ticket-config.xml file with Spectrum Service Desk integration

Problem Environment:
Spectrum 9.1
Service Desk Integration

Error on line 159 of document file:/SPECTRUM/tomcat/webapps/spectrum/../../../custom/svdsk/config/service-desk-ticket-config.xml: cvc-complex-type.2.4.a: Invalid content was found starting >with element alarm-attribute. One of {"http://www.ca.com":sd-problem-type, "http://www.ca.com":sd-userid} is expected.

Causes of this problem:
The error above was reported because you can only specify one parameter for each associated problem type in the service-desk-ticket-config.xml file. This was currently in place in this scenario:

<sd-ticket>

<model-association>

<relation>0x1003a</relation>

<left-model-name>Network Devices</left-model-name>

</model-association>

<alarm-attribute>

<attr-id>0x11f56</attr-id>

<value>Critical</value>

</alarm-attribute>

<sd-problem-type>Spect_Network_Critical_Error</sd-problem-type>

</sd-ticket>

So in this case you can only specify a global collection or alarm attribute, not both in one rule. Unfortunately you can?t combine parameters at this time with the current integration.

(Legacy KB ID CNC TS33229 )

Release: SPPREM05900-9.1-Spectrum-Infrastructure Manager-Premium Suite
Component: