Skip to main content
K
kkomarla1-Visitor
1-Visitor
September 2, 2015
Solved

Member check-in

  • September 2, 2015
  • 1 reply
  • 1938 views

How does Source Integrity indentify that a member has been modified and can be checked-in?

 

As per my understanding this happens when:

* the contents of the members have been updated/changed;

* the member file's modification date has been changed.

  

Please let me know if my understanding is correct?

I am trying to understand how the source integrity decides when to update a member’s revision with default policies in place. 

Best answer by KaelLizak

Hello Karthik,

The old system used heuristics including time-date stamps and file size.  It usually works.

As of Integrity 2009 SP4, this can be done with checksums (CRC), by using the instructions in this article.  To my knowledge, if this configured it always works.

Regards,
Kael

1 reply

K
KaelLizak16-PearlAnswer
16-Pearl
September 17, 2015

Hello Karthik,

The old system used heuristics including time-date stamps and file size.  It usually works.

As of Integrity 2009 SP4, this can be done with checksums (CRC), by using the instructions in this article.  To my knowledge, if this configured it always works.

Regards,
Kael

K
kkomarla1-VisitorAuthor
1-Visitor
September 18, 2015

Hi Kael,

I was under the impressin that with Integrity 10.5 too the check in happens under two conditions time-date stamps and file size with default policies in place.

I will look into the Checksum though.

Thanks and Regards,

Karthik Komarla

Terms & ConditionsAccessibility statement