You can trace the execution of a Tersus application visually on the same diagrams used to define the application, making it easier to understand the business logic and detect bugs.
When working in trace mode, the Tersus Server records every step during the application’s execution. This recording ("trace") can then be played back to view the flow of the application and the value of each data element.
Unlike regular debuggers, which can only move forwards, the Tersus tracing function acts like a “time machine.” You can move back and forth along the execution. If you reach a point where something looks erroneous, you can trace back to locate the root cause of the improper behavior.
Visual Debugging is performed in two steps:
Visual debugging utilizes a trace file – a recording of the steps performed by the Tersus Server while executing the application (typically, in response to user actions). The trace file records which elements of the application model have been activated, in what order, and what data passed between these elements.
The creation of a trace file is initiated and terminated by the user of the application as follows:
Note the following regarding trace files:
Once a trace file has been created, it should be loaded into the Tersus Studio in order to debug the model you want to trace, as follows:
The trace view looks similar to the following:All screenshots are based on the Requisition Management System sample application.The user has opened the Open Requisitions view, clicked Start Trace, added a requisition (through the New Requisition button), then canceled the requisition (through the Cancel Requisition button), and clicked Stop Trace.
Each row in the trace view includes the following fields:
The following are possible when using the trace view:
For best results, use the Firefox browser..