Integration with ServiceDeskPlus breaks resolve notification
Just downloaded and installed the V4.2 Pro versn on trial on a seperate server from our live Service Desk Plus installation ( 7011 ).
During the ADManager configuration it requests the Service desk port and an admin account so these ( naively ) were entered and tested and accepted fine.
Net result is the link at the top of Service Desk Plus now goes to this test install, we don't have a live install of ADManager so that's not an issue.
The problem is that the Resolution notification that is sent when the request is resolved has a link to the Closure acceptance page which is now corrupted by the URL of the ADmanager installation.
The Url should read http://servicedesk:8080/close and instead is reading http://admanager:8081/http:/servicedesk:8080/close and hence doesn't work!
So how can I get rid of the integration of ADManager from ServiceDesk?
Need to get this sorted ASAP as Service Desk is live application and that was the reason for putting ADManager on a seperate server.
Appreciate info ASAP, also posting same in the ServiceDesk forum incase someone in there has a solution.
Regards,
Andy
During the ADManager configuration it requests the Service desk port and an admin account so these ( naively ) were entered and tested and accepted fine.
Net result is the link at the top of Service Desk Plus now goes to this test install, we don't have a live install of ADManager so that's not an issue.
The problem is that the Resolution notification that is sent when the request is resolved has a link to the Closure acceptance page which is now corrupted by the URL of the ADmanager installation.
The Url should read http://servicedesk:8080/close and instead is reading http://admanager:8081/http:/servicedesk:8080/close and hence doesn't work!
So how can I get rid of the integration of ADManager from ServiceDesk?
Need to get this sorted ASAP as Service Desk is live application and that was the reason for putting ADManager on a seperate server.
Appreciate info ASAP, also posting same in the ServiceDesk forum incase someone in there has a solution.
Regards,
Andy