Time/Date settings - what is entered is 4 hours different in email/Remedy
We currently have a service that has date/time settings we pick up and pass into email and Remedy. This is 4 hours ahead of the entered time. The request is correct but in the outbound it is 4 hours ahead. Where do we go to correct this?
Time/Date settings - what is entered is 4 hours different in ema
We had a similar problem with our integration to HP Service Desk. Whenever a service call was generated in Service Desk, the dates and times where 5 hours ahead of the real time. We found that when RequestCenter creates the outbound XML, the dates and times are always passed in UTC but when the Service Desk api recieves the information, it seemed to assume that the date and time was CST because the newScale RequestCenter server's local timezone was set as CST.
We ended up changing the timezone of the RequestCenter server to UTC, which solved our problem. Not sure if any of this would be applicable to your problem.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...