Each time an object is modified the system checks if its state attribute (if defined) has been modified, and in such a case record its previous value in the object update audit trail entry. So the audit-trail entry obtained using use ‘do.ashx?cmd=audit…’ or ‘cmd4 audit’ of a normal object update looks like this:

  <ActionDesc xsi:type="UpdateActionDesc" Time="2009-10-28T20:06:31.097Z"

    UserId="1687" LoginGuid="aa284e85-c7e6-4f0b-b59f-3370c766de45" 

    Action="Update" UserDesc="TeraDP\MiMo" 

    ObjectId="2185" ObjectTypeName="story" ObjectDesc="story257" 

    Codes="Normal Content" NewVersion="false" />

The audit-trail entry of an object update that modified the state attribute looks like this:

  <ActionDesc xsi:type="UpdateActionDesc" Time="2009-11-14T23:47:42.69Z" 

   UserId="1687" LoginGuid="38fd2025-0abe-4bb3-affe-5f54095cb63a" 

   Action="Update"  UserDesc="TeraDP\MiMo" 

   ObjectId="2185" ObjectTypeName="story" ObjectDesc="story257" 

   Codes="Normal" PreviousStateId="1702" NewVersion="true" />

indicating that the state attribute was referencing the object with id 1702 and now (after the update) references a different object.

Of course audit-trail entries for objects that do not have a state attribute never have a ‘PreviousStateId’ attribute.

Related links

Audit trail of merged articles: see Merge content ot two or more articles.

Audit trail of wires: see Wires footprints.

Audit trail of pages: see Display page audit.

Audit printing

Audit palette

Audit trail reports

Display audit of articles/images on Tracking main tab