It would be dependant on the Timezone of the Remote Desktop… So the Task Agent shouldn’t matter, I assume Epicor converts the Servers Time to UTC and then says Anything to Run within this UTC Timeframe?
Hence our old problem when we set the time to 8:02PM on a Sunday… The Task Runs on 01:02AM Monday. Because in the Conversion it says “oh don’t run this on Sunday, run it on Monday”.
In your BPM if you do DateTime.Now it will use the Servers Time… Then when you try to convert that field for someone to their timezone, you are screwed… Always if you can save it in UTC Time
EDIT:
Or Nevermind Epicor hasn’t been using the Time yet portion of DateTime, only the Date.
One thing that did get us in the past is using DateTime.Now instead of DateTime.Today which sets it to mm/dd/yyyy 12:00AM. So if you can use DateTime.Today
Youll get into this trouble
if (PartRow.NeedByDate < DateTime.Now) { // }
yes it’s greater, its the same date but 12AM vs 2PM…
You can set Timezone Redirection in your RDP server through a registry entry:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Allow time zone redirection
If you set this, the RDP Client will adjust the time at the desktop to the timezone of the calling workstation.
Haven’t seen this enhancement request become reality yet, but just wanted to check to see what the scope would be.
Sounds like the Task Schedule would look at the Company that submitted the schedule, but what about Multiple Sites in the same Company? There is a TimeZone option in Site Maintenance but I don’t see a Site (Plant) field on a Task Schedule that the schedule could use for the offset.
Couldn’t it be assumed that if the user (who only has access to one site in a company) that submitted the task would expect it to render in his Site’s Timezone (unless otherwise specified when Submitting the Task?)