We wrote some code around the IBM DST agent, to effectively screen out some users (by OU1) that do not obey the forthcoming DST change.
The code failed to filter out users in Arizona, and as a result, they are seeing meetings that appear to be one hour off schedule.
Is there an “undo” available?
Subject: Major DST uh-oh. How to undo?
Unfortunately, there is no “undo” per se - fortunately, these documents can probably easily be identified. I would assume the OU1 info is still valid plus, you have the $TimeZoneAgent field set on the now “wrong” documents that you want to update, and an agent that can reset the these values and make them them look “old” again.
Granted, I’ve not tried this, but the principle is sound. I’m sure others on the forum would be interested in your results and probably able to give comment should you have questions.
Subject: RE: Major DST uh-oh. How to undo?
So if I write an LS agent that checks for the presence of the $TimeZoneAgent field and adjust the time back by one hour, would that be sufficient? Which fields in particular have to get updated? What about repeating entries? Are the repeating entries stored as separate documents or as part of a multi-value field within the original document? Thanks in advance.
Subject: RE: Major DST uh-oh. How to undo?
Suggest patterning it after the released “admin” agent actually rather than doing up something totally new.
That is - make the Mountain time rules go back to the Z=7$DO=1$DL=4 1 1 10 -1 1$ZX=42$ZN=Mountain rule you want them to be on and then tweak the logic to select the documents slightly differently. The easy part would be to select based on the $TimeZoneAgent=1 rather than presence of the field. The harder part would be some work would need to be done to isolate the Arizona Mountain Time documents from the rest of the Mountain Time documents if you have meetings scheduled between Arizona and Utah for example, but that’s really getting into details of “fixing” the problem vs. just providing an undo.
Of course, it could also be communicated to users that they would need to reschedule such meetings, but the explanation of why invariably would come back to the state’s choice not to follow the same pattern as the rest of the country. As to why the state does not lobby to get a different time zone identifier, I’m not sure. Maybe somebody else can enlighten us?