Change history
This article explains how change history work.
Function is available in version 4.5 and later.
Overview
Each save operation generates a change note. The change note contains the following information.
Field | Usage |
|---|---|
Time stamp | Date and time for the change |
User name | Windows user name of the person making the change. If change is triggered by an automated import, user name may be the service account or system. |
Status | May contain Added, Modified, Deleted. If ItemStatus is changed it will contain the new value of ItemStatus and reason is “New ItemStatus”. |
Reason | When imported data, this is name of an export folder or Excel file name, to indicate where from data is imported. It may also indicate that ItemStatus is changed. Manual editing in the Manager program often leaves this column empty. |
Note | Refers to where the change was made. Example of values are:
|
Id | Technical key in the database, i.e. used when looking for internal data in the system. |
Persistent identity | Persistent identity of the object |
Reason Type (version 5.3.0 and above) | Predefined Reason Types are displayed on the Manual Change Notes dialog box (when enabled). This could be set in the file user-settings.config, see https://signifikant.atlassian.net/wiki/spaces/ASKB/pages/1449590785/Technical+documentation+-+Server+wide+user+settings+for+all+Managers#Enable-server-wide-user-settings |
Change log is generated for the following information:
Information | Note |
|---|---|
All presentation types |
|
Bulletins |
|
Footnotes | Starting from version 5.0 |
Specifications |
|
Part replacements | Starting from version 5.0 Starting from version 5.1 the notes column will hold a note for the part number. Eg. note may be “Manager Part: 4450025482“. This will make it possible to search for deleted replacements. |
Images | Starting from version 5.0 |
Filters | Starting from version 5.0 |
Part relations | Starting from version 5.0 |
User interface
In Manager it is possible to see the change history on the above information by right clicking on the object and selecting “Show change history…”
The dialogue will show all changes for objects based on the object’s database id.
Starting from version 5.0 the dialogue will show all changes for objects of the same type and that have the same pid. Then change history looks at database id. If database id in change history is different from the selected object rows are made grey. Reason is that if an user adds an object with pid 1, then deletes it and adds it again with same pid, user chan see this. But marked as grey to indicate change of object.
Note that there is a change in change history logic between version 4.5 and 5.0.