Track changes and history of your Vertec objects using AuditTrail.
Cloud Suite
On-Premises
As of Vertec version 6.8.0.19 it is possible to track the history of the data, i.e. from generation to deletion. The change logchange log the so-called AuditTrail, is written automatically and is stored in Vertec via Python. vtcapp retrievable.
In this way, changes to objects are transparently recorded in Vertec and it becomes clear who made which changes when.
Under System settings > General, this feature is available with the option Keep Maintain full change log. If this setting is active setting, a full change log is change logged, including user data and details of changes made to objects. If this setting is deactivated setting, a truncated form of the change log is change logged, in which neither specific changes nor user data are saved. It only records that an object has been deleted created, changed or deleted.
The data is queried via Python. Please note that any person who can call any of the Python features will receive the full data as a return value with this setting. So there are no additional restrictions. Therefore, you should make this setting consciously setting according to your privacy requirements.
In the AuditTrail, all changes to objects in Vertec are logged, depending on the system settings in different levels of detail.
Changes to objects of the classes are not taken into account:
The following members are also not written separately, since they are identical to the time of the AuditTrail entry:
The AuditTrail can also be used to write notes. For example, a note could be written when a user invokes a certain feature.
The following Python features are available for this purpose:
| feature | description | Example |
|---|---|---|
vtcapp.createauditnote(obj, text: String) |
Creates a note with the specified text on the passed object. |
vtcapp.createauditnote(argobject, "Meine Notiz")
|
vtcapp.getauditnotes(objid: int): list of notes |
This method outputs the notes that have been created on the passed object. In addition, the notes also appear when querying the AuditTrail via |
notes = vtcapp.getauditnotes(argobject.objid)
|
The AuditTrail can be featured with the following Vertec Python Features:
| feature | description | Example |
|---|---|---|
vtcapp.getchangelogforobject(objid: int[, changesSince: datetime]): dict of changelogs |
This method outputs changelog entries for a specific object by passing the internal ID of the object and optionally the time of filtering. |
vtcapp.getchangelogforobject(argobject.objid))
|
vtcapp.getchangelogsince(changesSince: datetime[, classfilter: stringlist]): dict of changelogs |
With this method, all changelog entries that have been created since the given time are output. Optionally, a filter of the classes can be passed in the form of a comma-separated list. The class names can be specified in English or German. Base classes are supported (e.g. when specifying performance, both Open service and Billed Performance are taken into account). |
import datetime vtcapp.getchangelogsince(datetime.datetime(2026, 4, 27), ["Project"]) |
The Python features return a list of Python dictionaries. Each dictionary contains a single change with the following information:
[{'Id': 7017, 'BoldId': 2771, 'UserId': 515, 'BoldType': 18,
'AuditType': 'Modified', 'Member': 'type', 'TimeStamp': datetime.datetime(2026, 4, 27, 20, 14, 37),
'NewValue': '183'}]
| Column | description |
|---|---|
Id |
The identification number of the Vertec object. |
BoldId |
The unique Internal Identification Number (Internal ID) of the Vertec object (see also KB Article The Properties Dialog). |
UserId |
The identification number of the user who made the change. |
BoldType |
The identification number of the Vertec object type. |
AuditType |
The changes to Vertec objects are noted by the following audit entries:
*Note: The status note is only given if the note is written via the Python feature vtcapp.createauditnote(). |
Member |
The name of the changed attribute, i.e. a data field of the object or a link. |
TimeStamp |
Date and time of the modification. |
NewValue |
The changed or new value. For data type Blob a maximum of 4000 symbols are output. |
In a truncated change log, the UserId, Member, and Newvalue information is not saved.