Skip to main content
May 4, 2017 7:46 AM UTC
New Idea

Source Integrity: New functionality for Line Terminator (Policy) - "Do not normalize line terminators"

Based on Cases:

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=13639315

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=12140188

https://support.ptc.com/apps/case_logger_viewer/auth/ssl/case=11991881

 

PTC Community Discussion:

https://community.ptc.com/t5/Windchill-Systems-Software/When-check-in-text-files-with-n-line-terminator-are-modified-to/td-p/251762?ProductFamily=Integrity&art_lang=en&posno=3&source=search

 

PTC Article:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS92954&source=Case%20Viewer

 

Problem:

Source Integrity always crashes our files under version management when they have inconsistent line terminators. This happens mostly with deliveries from external customers suppliers.

To overcome this problem we want to get a possibility that our file content is not changed by PTC toll automatically.

 

 

Integrity archive CONTENT was corrupted. It seems that '0A' was replaced by '0D 0A' which corrupted the files from archive

 

 

Some files received by customer in UNIX and DOS mixed mode

Format are converted to DOS format by MKS at check in.

As a consequence they don't have the same CRC.

So it's not convenient for customer point of view because the integrated files are different than those received.

 

Why can't MKS check in the files without converting their format?