Common issue
The application takes its time from the current server time, for instance, UTC - 6 hours, which causes some issues at EU sites when tracking the current work order status. As this is a non-GMP application and based on users Remote desktop services profiles, is it possible for the system to use the users regional timezone?
What causes this issue?
Some functions in Orchestrate, for example, those performed at the database level, take their date/time from:
The system time and time zone of the SQL Server. Other functions (those performed at the application level) use.
The system time, time zone, date/number formats on the client.
We are able to adjust some of these functions with an offset from the time of the SQL Server, so that the date and time match the date and time in a different time zone. Other database-level functions cannot be adjusted and will always show the system time of the SQL Server
If it is a Remote Desktop/Citrix session, the session may be configured to provide the application with the time and formats of:
The RDP server
The local client (the user's own computer)
In MyDesk, for example, the Citrix session provides Orchestrate with the time at the local client.
Need further help?
If you are using a Citrix Session which provides Orchestrate with the time at the local client, please contact support.
🤓Tip: For an on-prem install, those settings of the remote session would need to be configured by your IT department. The ideal scenario would be to have a SQL Server and RDP Server(s) in each time zone.