Seeing an issue with the timestamp in the “File Modified On” field, which is showing a future time. Timestamp field may be used to validate the approvals for audits. Question as to why the "File Modified On" time showing in the future.
For example, the current time is June 29, 2020, 1:48:00 PM EST. On the Lists tab seeing
Release : 13.0.3 and higher
Component : CA Harvest Software Change Manager
The reason this is appearing this way is that Harvest handles the two "Modified on" columns differently.
The "Modified On" column shows the time that the file was checked into Harvest. Harvest will store this time as of the GMT time zone value and will convert it to the Workbench user's local time zone when it is displayed on the screen.
The "File Modified On" column shows the time that the file was saved on the computer of the user who updated it. Harvest will store this time as of the local zime zone value for the user who checked in the file and it is not converted to the Workbench user's local time zone when it is displayed on the screen.
In the above example screenshot, the user who modified the file and then checked it in was in India (UTC +5:30) and the Workbench user displaying the package contents was in Michigan (UTC -5:00)
This behavior is working as designed.