Documentation:SysTurnkeyTraceLog Pattern: Difference between revisions

SysTurnkeyTraceLog Pattern

Revision as of 09:24, 13 January 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.

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

This page was edited 57 days ago on 01/20/2025. What links here

@@ Line 1: / Line 1: @@
-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]]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.
+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]]
+Merge the pattern into your model from [[/wiki.mdriven.net/Documentation:TK Live View|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:[[File:2022-07-19 13h52 14.png|alt=x|none|thumb|851x851px]]This example is available at: https://github.com/supportMDriven/MDrivenComponents.git