strange behavior of "Modified Working Files" filter

[Cosmina]

Hi,

Can somebody tell me how IMS compares a file and sets the "modified" flag?

These is my observed behavior:

1) I have several files in my sandbox with the "modified" flag, but when I apply the filter "modified working files", those files are hided.

2) If I select a file that appears to be modified, I have this information displayed: "Working file checksum differs, newer: Mar 18, 2016 1:49:34 PM vs. Mar 18, 2016 1:49:34 PM ".

If I compare it with another tool (Beyond compare for example) I have no difference. This situation leads to critical conditions, because developers use this filter commonly to detect the need for check ins.

Is this a known problem?

Do you know why IMS has this behavior?

[awalsh]

For the working file delta, the size, timestamp and checksum of the working file is compared to the revision it is based on. Any changed or missing working files will show this delta. The filter "Modified Working Files" will show any member with a working file delta. The filter "Working File Size Deltas" only shows members where the working file is a different size (so if only the timestamp changes, it won't be shown. 

For a revision delta, the working file revision is compared to the member revision, and the member revision is compared to the newest revision in the history. If either of these are different, then you will see this delta. 

See CS131973 for more information on the delta icons.

There have been some specific cases where a delta was not shown for a working file when it should have been:

• Working file delta icon not shown until Sandbox is manually refreshed in Integrity Lifecycle Manager: this is fixed by using F5 to refresh.
• Member Delta during Checkin is not recognized if only one character changes / checksum / size is identical in Integrity Lifecycle Manager: This is hotfixed in 10.8, 10.9, 11.0 and fixed in 11.1.
• Resyncing a retargeted sandbox does not always update working file correctly in Integrity Lifecycle Manager: this is corrected by adding a policy to store the working archive in a sandbox.

If your situation doesn't match the above, I suggest creating a support case for investigation. As you say, it is critical that the filters and deltas are correct.