Editing the Audit Trail Info

Very often companies wish to reset the Audit Trail for their start parts. This article shows you how to tweak the Pro/E file such that it is as you wish to see it.

Open up one of your parts in notepad++. Now scroll down the header, if you read closely you may start getting the feeling that you can read this file a bit! OK once you get to the binary block you'll be lost but it is possible to decode the header for our purpose of adjusting/removing audit trail information.

 

Look at the line left, you can see that line 65 states '@comment 26' then at a line which has 26 in it, you can see the content of a comment. This is the clue to how this header is constructed. A little bit of experimenting with different values leads to my conclusion that the linkage is straightforward:

Audit Trail Information Location

The Username is controlled by lines with '17' as second number.

  • Line 47 specifies that '@name' is on lines with 17.
  • Line 48 (in my file) happens to call out CLEWIS2 in the name field.
  • Replace the text to edit it.
  • Seconds is controlled by lines with '19' as second number.

  • Line 51 specifies that '@tm_sec' is on lines with 19.
  • Line 52 (in my file) happens to call out '02' for seconds.
  • Set to a value between 00 and 59.
  • Minutes is controlled by lines with '20' as second number.

  • Line 53 specifies that '@tm_min' is on lines with 20.
  • Line 54 (in my file) happens to call out '02' for minutes.
  • Set to a value between 00 and 59.
  • Hour is controlled by lines with '21' as second number.

  • Line 55 specifies that '@tm_hour' is on lines with 20.
  • Line 56 (in my file) happens to call out '02' for the hour.
  • Set to a value between 00 and 23. (Seems to be 2 out)
  • Day is controlled by lines with '22' as second number.

  • Line 57 specifies that '@tm_mday' is on lines with 22.
  • Line 58 (in my file) happens to call out '2' for the day.
  • Set to a value between 1 and 31.
  • Month is controlled by lines with '23' as second number.

  • Line 59 specifies that '@tm_mon' is on lines with 23.
  • Line 60 (in my file) happens to call out '1' for the month.
  • Set to a value between 0 and 11 (Seems to be 1 out).
  • Year is controlled by lines with '24' as second number.

  • Line 61 specifies that '@tm_year' is on lines with 24.
  • Line 62 (in my file) happens to call out '2' for the year.
  • Set the end digit to value between 0 (2000) and 9 (2009).
  • The Action value is controlled by lines with '25' as second number. But to be honest I can't see a reason to want to change that.

    Comment is controlled by lines with '26' as second number.

  • Line 65 specifies that '@comment' is on lines with 26.
  • Line 66 (in my file) happens to call out "Hostname: 'OVERWRITTEN2'": for the comment.
  • Replace the text to edit it.
  •  

    Modification of the information

    The picture here shows the result of adjusted every field in both entries to demonstrate the point.

     

    Hidding Entries

    The lines that control what Pro/E is expecting in terms of the length of the Audit trail is show right. The [2] indicates that Pro/E is expecting two Audit File entries. Changing the value to '1' results in the following:

     

    Removing Audit Entries

    Once you have changed the audit trail info such that Pro/E will expect a length of '1', you can go about removing the lines from the additional audit trail entries. Remove duplicate lines for 16,17,18,19,20,21,22,23,25,25,26,27 and 28.

     

    You should remove these lines so that the next time the Part is updated by a different user, Pro/E will correctly register another entry in the audit trail.

     

    Conclusion

    You can edit the content of the Pro/E headers. However as with all hacks, It's up to you whether you choose to clean up your start parts audit trail information. PTC will not condone the use of this technique, use it at your own risk.