History

An object's historical information includes:

• The type of activity performed on the object, such as create, modify, connect, and so on.
• The user who initiated the activity.
• The date and time of the activity.
• The object's state when the activity took place.
• Any attributes applicable when the activity took place.

You can add a customized history through MQL to track certain events, either manually or programmatically For more information, see MQL Command Reference: history clause.

History records can be selected when printing or expanding business object, set, or connection information using the MQL select clause. In addition, when printing all information about a business object, set, or connection, history records can be excluded.

System Administrators only can purge the history records of a business object or connection using MQL. All history records of a business object or connection can be deleted with one command.

History can be turned off in a single session by a System Administrator for the duration of the session or until turned back on. If an implementation does not require history recording, or requires only custom history entries, Collaboration and Approvals "standard" history can be disabled for the entire system. Turning history recording off can improve performance in very large databases, though certain standards may require that it is turned on.

History entries larger than 255 characters are truncated to 255 characters. This includes custom history entries as well as Collaboration and Approvals history entries. This means that history logs for the modification of long description or string attribute fields may be truncated.

When objects are created and then immediately modified within a trigger, the timestamp is often identical. When this happens, the modify event may be logged before the create event, although both will have the same timestamp.

For more information, see MQL Command Reference: history clause.