SysTurnkeyTraceLog Pattern
No edit summary |
(Added Edited template with July 12, 2025.) |
||
| Line 1: | Line 1: | ||
{{Edited|July|12|2025}} | |||
If you need to track what users are up to in an MDriven Turnkey app, add a class following this pattern. The pattern collects user actions in an effecient manner.[[File:2022-07-19 13h48 16.png|none|thumb|265x265px]] | If you need to track what users are up to in an MDriven Turnkey app, add a class following this pattern. The pattern collects user actions in an effecient manner.[[File:2022-07-19 13h48 16.png|none|thumb|265x265px]] | ||
Latest revision as of 06:35, 20 January 2025
This page was created by Charles on 2024-12-11. Last edited by Edgar on 2025-01-20.
If you need to track what users are up to in an MDriven Turnkey app, add a class following this pattern. The pattern collects user actions in an effecient manner.
Merge the pattern into your model from TK Live View
For every navigation (change of view) or action (action language execution resulting in potential data change), information will be snapshotted, and every 30 seconds, MDrivenTurnkey will spool out objects of the above class.
This is how it was used in one customer case:
This example is available at: https://github.com/supportMDriven/MDrivenComponents.git