Difference between revisions of "Content Logging"
m (→Open logs) |
m (→Branch download) |
||
| Line 9: | Line 9: | ||
When downloading a branch during offline preparations, the entire process can be logged in a single log file. | When downloading a branch during offline preparations, the entire process can be logged in a single log file. | ||
Once a system toast is shown to indicate that the download (for objects or documents) has finished, the user can click on the toast to open the log file to get more details. | Once a system toast is shown to indicate that the download (for objects or documents) has finished, the user can click on the toast to open the log file to get more details. | ||
| − | {{Hint|The file names consist of the date and time of the activity as well as the text and | + | {{Hint|The file names consist of the date and time of the activity as well as the text and ID of the object/document.}} |
{{Clear}} | {{Clear}} | ||
[[File:UI_WinX_Commit_Log_File.png|thumb|alt=Commit Log|Commit Log]] | [[File:UI_WinX_Commit_Log_File.png|thumb|alt=Commit Log|Commit Log]] | ||
| + | |||
| + | [[Category:WinX|Content Logging]] | ||
| + | |||
=== Commit === | === Commit === | ||
Once a commit is made, the details of that commit attempt can be logged regardless of its result. This includes the exact data (e.g. object ID, property values, etc.) sent to the server. | Once a commit is made, the details of that commit attempt can be logged regardless of its result. This includes the exact data (e.g. object ID, property values, etc.) sent to the server. | ||
Latest revision as of 09:51, 30 May 2016
UBIK.WinX users can enable a logging feature to record the results of content related activities to log files.
Log types
Currently, logging for the following content related activities are supported.
Branch download
When downloading a branch during offline preparations, the entire process can be logged in a single log file. Once a system toast is shown to indicate that the download (for objects or documents) has finished, the user can click on the toast to open the log file to get more details.
 | The file names consist of the date and time of the activity as well as the text and ID of the object/document. |
Commit
Once a commit is made, the details of that commit attempt can be logged regardless of its result. This includes the exact data (e.g. object ID, property values, etc.) sent to the server. All commits within the same user login session are kept in a single log file.
| The file names consist of the start date and time of the user login session as well as the user name. |
Log setting
In the "Content" settings panel, a "Content Logging" toggle is available. Users can switch it off so that UBIK® does not save or display any of such logs.
Open logs
In addition to special UI navigations such as clicking on a toast, users can also list all existing logs by clicking a "Show logs" button which is available in the "Content" settings panel. Afterwards, simply click any one of them to open it.
All log files are stored under: C:\Users\Username\AppData\Local\Packages\AugmensysGmbH.UBIK_PackageID\LocalState\Logs.
