Revision History of document

[Shilpa_Dubey]

Hi All,

When I export requirement specification document I want its revision history as mentioned below:

Revision Date	Author	Changes/Comments

or 

Revision	Doc. Date	Author	Description

I was looking to extract information from the history of a document and export it into a word document when exported.

Because now if you see the history of a document in PTC Integrity has too much information even if we format small things like font it gets captured in history.

Is there any way how this could be done? 

Thanks and Regards,

Shilpa

[awalsh]

The information you need is stored in the Versions field, which is a built-in field that can be added to the document type. However, since this is a qbr (Query Backed Relationship) field, there are limitations to what you can get for a relationship field using the gateway export. 

The following discussions in the community may help you:
https://community.ptc.com/t5/Integrity-Questions/Gateway-Export-to-Word-works-fine-but-can-t-retrieve-text-field/m-p/538062

https://community.ptc.com/t5/Integrity-Ideas/Enable-Gateway-to-export-linked-objects/idi-p/537467
https://community.ptc.com/t5/Integrity-Tips/Integrity-LM-Server-Gateway-and-Reports/m-p/448480

[VolkerEckardt]

Hello Shilpa,

as you already realized, the difficulty with an automatically generated history is that this would become very long. Even the smallest change (like adding a dot at the end of a sentence) will track the whole text entry. In other cases where you add a dot between numbers can change the whole requirement. (when 10 becomes 1.0)

We discussed this topic a lot, but it turned out that a manually added revision comment is the most appropriate solution. (Document > Baseline)

The question is now how to read the Baselines to send them into a Word export: for this you must use my CustomExport functionality which does exactly that. (see attachment)

Alternatively, you can also feed the baseline data into a new rich text field and print this out together with the document. This would need a (server) trigger only.