Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

OVO-SD integration problem

Highlighted
sunilgupta
Super Collector

OVO-SD integration problem

I am not getting trouble ticket from the OVO, which was working fine previously.

I have debugged this into OVO side, here is the received error

Command: /opt/OV/lbin/sd/ovsdevent.sh 74235f88-a9f9-71db-0e85-0a13176c0000
produced the following output error:


with exit code: 3


I have attaced the ovsdevent.log also.

Thanks in advance.

Sunil

3 REPLIES
Carol Hibbard
Honored Contributor

Re: OVO-SD integration problem

It looks like you are missing some required fields. Did you change the required fields?

The error message doesn't tell you which fields are missing unfortunately.
sunilgupta
Super Collector

Re: OVO-SD integration problem

Thanks,

I have checked the log and try putting required field one by one and came to know this was happening due to Severity field of Incident, though this field is coming from OVO message and getting populated also in the service desk severity. But once I make it mandatory i get the problem in the log.

Please guide me on this.

Regards,
Sunil
Carol Hibbard
Honored Contributor

Re: OVO-SD integration problem

The out-of-the-box import mapping takes the OVOU Severity value and maps it to the SD impact field. There is no severity field in SD by default. You will have to show us your mapping if you have created a field called Severity in SD.
//Add this to "OnDomLoad" event