I tested in our Dev environment. I had some old recurring tasks in there. It moved them on the calendar. So, if it was a 6am job, it is now showing at 5am on the calendar. So, I am not sure I want to do this in Production as my jobs are showing the correct time on the calendar. I saw Jack's response where I think he is suggesting an IIS reset. I would probably have to wait until this evening to do that but need to fix the jobs before then. I think what I did last year was opened each one, changed the time from example: 8am to 9am, saved, and then changed back to 8am.
Hi Denise, thank you for testing. I would not execute this in PROD then. We will look into this and see if there is a better solution to retain the correct calendar view and have the task execute at the desired time.
I don't believe IIS is the answer. That resets daily anyway. I think what is needed is to change the "Start Date" (not the time) in the task scheduler item so that it retains the correct time in the calendar view, and also executes at the desired time based on the time change for the date. I think the best solution for this would be to have the data management solution change the start date for all tasks to the date of when the next time the job will run. This will result in the start date changing to a date that is after the daylight savings change which I expect will resolve the issue. You would ideally want to run this the day before daylight savings or the business day after daylight savings to ensure the start date is changed to a date that is post daylight savings. Try reloading the zip file in my original post to upload the latest version and see if that provides the desired results.
I was able to work with Jack to attach the latest solution in my original post, but here is the new code block that handles the daylights savings logic if anyone would like to review.
Public Sub UpdateDaylightSavings(ByVal si As SessionInfo, ByVal globals As BRGlobals, ByVal api As Object, ByVal args As ExtenderArgs)
Try
Using dbConnFW As DBConnInfo = BRApi.Database.CreateFrameworkDbConnInfo(si)
Using dbConnApp As DBConnInfo = BRApi.Database.CreateApplicationDbConnInfo(si)
' Get a list of schedules
' Function GetScheduledJobs(dbConnFW As DbConnInfo,dbConnApp As DbConnInfo, getItemsForCurrentUserOnly As Boolean) As List(Of DataMgmtScheduleItem)
Dim dmSchedItem As List(Of DataMgmtScheduleItemEx) = DataMgmtScheduleWcf.GetScheduledJobs(dbConnFW,dbConnApp,False)
For Each schedJob As DataMgmtScheduleItemEx In dmSchedItem
'adjust the start time based on what the user defines
schedJob.DataMgmtScheduleItem.StartTime = schedJob.NextRunTime
' Function SaveScheduledJob(dbConnFW As DbConnInfo,dbConnApp As DbConnInfo,isNew As TriStateBool)
DataMgmtScheduleWcf.SaveScheduledJob(dbConnFW,dbConnApp,schedJob.DataMgmtScheduleItem,TriStateBool.FalseValue)
Next
End Using
End Using
Catch ex As Exception
Throw ErrorHandler.LogWrite(si, New XFException(si, ex))
End Try
End Sub
I think Jack may be onto something. Unfortunately I was not able to test the theory of doing an iis reset to see if that would update the display on the Task Scheduler calendar to show them at the time they were actually executing. (showing at 8am, scheduled for 8am, but task was starting at 9am). If an iis reset corrected how they were shown in Task Scheduler then it would have worked to change the times by an hour. I was not able to do an iis reset until evening and had to get all the tasks back on the right schedule prior to that. I did open a case with OS Support and was told it was a bug and that I would need to go into each task and edit the task to a start date after the time change. I think that may have been another part of my issue - my tasks were recurring daily with the time change happening inside the recurring window. I will have to wait til fall and at that point will probably schedule an iis reset to happen early Sunday morning after the time change.
Thank you
Denise