Skip to main content
1-Visitor
December 13, 2005
Question

Audit Trail

  • December 13, 2005
  • 2 replies
  • 703 views
Good day all,

Is the audit trail a reasonable fingerprint (by the information it
contains) of the modified history of an object?

Jon

    2 replies

    1-Visitor
    December 13, 2005
    I don't really think that it is a true fingerprint..., but it's probably
    fairly reasonable.

    It only seems to record the last save by a given user-workstation
    combination.

    Also, if you really wanted to, you could find a part model with an audit
    trail that you like, delete all the features, and then import all the
    features of a different model (via udf, copy-from-diff-model, etc.).
    Then rename the resulting part and you've effectively swapped out the
    audit trail of one part with that of another. Of course, that model
    would probably not automatically regenerate correctly in its parent
    assembly, but that's another story.


    -Brian
    1-Visitor
    December 13, 2005
    Two things that I've always wondered about audit trails are:

    1. Sometimes they can be reported for drawings and sometimes they
    can't. What drives the difference?

    2. How can audit trail information be easily removed from a file? Say
    before sending to a Pro/E enabled vendor who is making parts on your behalf
    ...


    Regards,

    Dustin Neifer
    General Dynamics Land Systems






    "Adkins Brian M"
    <adkinsbrianm@joh <br="/> nDeere.com> To
    Sent by: "PTC/USER System Management
    bounce-sysmgt-109 Discussion"
    -user <->
    .org cc

    Subject
    12/13/2005 03:50 [sysmgt] RE: Audit Trail
    PM


    Please respond to
    "Adkins Brian M"
    <adkinsbrianm@joh <br="/> nDeere.com>






    I don't really think that it is a true fingerprint..., but it's probably
    fairly reasonable.

    It only seems to record the last save by a given user-workstation
    combination.

    Also, if you really wanted to, you could find a part model with an audit
    trail that you like, delete all the features, and then import all the
    features of a different model (via udf, copy-from-diff-model, etc.). Then
    rename the resulting part and you've effectively swapped out the audit
    trail of one part with that of another. Of course, that model would
    probably not automatically regenerate correctly in its parent assembly, but
    that's another story.


    -Brian