Indicator reading times in version 7.8

This issue was reported by another user using release 7.7. We've replicated and reported the issue as #21142 in our VSTS and it's already been investigated. What's going on is that we started transitioning APM to be able to support UTC time in release 7.7. The logic that sets the ProcessedOn date on the reading request in ODCPluginBase.UpdateRequest was changed to use the current date/time in UTC instead of the local date/time. 

This has been fixed in release 7.9.

In version 7.7 and 7.8, the CreatedOn Date should be the correct local time and this is the important time from an analysis, monitoring and audit trail perspective. The Processed On is really more of an administrative attribute anyway

This issue was reported by another user using release 7.7. We've replicated and reported the issue as #21142 in our VSTS and it's already been investigated. What's going on is that we started transitioning APM to be able to support UTC time in release 7.7. The logic that sets the ProcessedOn date on the reading request in ODCPluginBase.UpdateRequest was changed to use the current date/time in UTC instead of the local date/time. 

This has been fixed in release 7.9.

In version 7.7 and 7.8, the CreatedOn Date should be the correct local time and this is the important time from an analysis, monitoring and audit trail perspective. The Processed On is really more of an administrative attribute anyway

Thanks. I will mark the issue as resolved