Service Desk Practitioners Forum
cancel

SD OVO integration

SOLVED
Go to solution
Highlighted
Andrej_19
Honored Contributor.

SD OVO integration

Hello,

I have a question, again, this time it's about service desk and operations integration. I've imported nodes sucessfuly, but for some reason, ovowindowsservices out of the box gives back bunch of errors. I'm attaching err. log, XML file, import mapping pic and export ini file.

Why is field Search code set as fixed value (using OVOSERVICE template) ?
What am I doing wrong ?

Plese help.

Best regards,

Andrej
6 REPLIES
Ganesha Sridhar
Outstanding Contributor.

Re: SD OVO integration

Hello Andrej,

The reason for the following error:
--------------------
while processing attribute PartComponent
0 4 While processing SERVICE_COMPOSITION (id = 32):
0 4 For ci relation the following fields are required: ci to.
0 4 No item found with this search code. Please enter an existing search code.
--------------------
Is due to case sensitive issue in the CI Search Code. In the XML file the value â ApplicationServicesâ for ID 32 is mix of both upper and lower case, but in OVSD the CI search code is stored in all caps - â APPLICATIONSERVICESâ hence the failure in comparing the values.

If you change the value to all upper case in import mapping then it should work.

The reason for the following error:
--------------------
0 4 While processing SERVICE (id = 1):
0 4 This instance of SERVICE can not be processed, because not all primary keys values have been provided.
--------------------

Is due to some the required value is missing in the service. The required value can be made either optional or it can be hard coded in service template which you are using the import mapping.

HTH

Regards,
Ganesha Sridhara
Andrej_19
Honored Contributor.

Re: SD OVO integration

Dear Ganesha,

I'm afraid I'm a little bit lost.

I'm attaching screenshots of import mapping.

Any further help ?

Best regards,
Andrej
Ganesha Sridhar
Outstanding Contributor.
Solution

Re: SD OVO integration

Hello Andrej,

Please see the attachment for the solution.

Regards
Ganesha Sridhara
Andrej_19
Honored Contributor.

Re: SD OVO integration

Many thanks for your reply Ganesha, I'don't have time to test it yet, but I'll try ASAP. 10 points just for effort.

I'll let you know if it works.

Best Regards,

Andrej
Andrej_19
Honored Contributor.

Re: SD OVO integration

Now I've realized, that I've forgotten to ask you something.

As the connection between Service desk and operations is working, and I'm receiving messages from OVO, the out-of-the box rules do their job.

Now I'd like to modify the following acknowledgement message

/NoLogo "\"%SD_OVWHOME%\\bin\\ovo-sd.vbs\"" [Source ID] OV_MessageUpdate_Acknowledge

so that it could contain OV_MessageUpdate_AddAnnotation

message as well.

So, I'd like to set acknowledge flag and message both at the same time in same rule.

Can this be done ?


Ganesha Sridhar
Outstanding Contributor.

Re: SD OVO integration

Yes it can be done.
The first method is like hard code the flag value in the DB rule to "Acknowledge".
The second method is to send some hard coded value "Acknowledge" as parameter to DB rule.

HTH

Regards
Ganesha Sridhara