HTML5 Debugger settings
You can use the following settings to troubleshoot an app, form, or wire in HTML5 Debugger. Tabs that are form or wire specific only display while a form or wire is running.
Exits the current application, and removes all breakpoints. This resets the app to its original state.
Step Over
Runs an entire subroutine, subapp, wire, or form without opening a new list of source elements in the debugger. The app stops after running the app item.
Step
Steps through the app one source element at a time, stopping after each line. The
icon displays next to the source element on which the app is stopped. For more information, refer to Run one source element at a time in debug mode.
Go
Runs the app from beginning to end or until it reaches a breakpoint. The app pauses when user input is required and resumes after the requested information is entered.
Clear all breakpoints
Removes all assigned breakpoints. For more information, refer to Remove breakpoints.
Source elements in the debugger
The central section of the debugger displays the source elements contained by the app you are currently running. The order in which elements are displayed in the pane follows the default logic of the app.
The following information displays for each source element.
Index
Displays the order in which the source element occurs in the app.
App Type
Displays the type of source element. For more information about source element types, refer to Source element types.
ID
Displays the ID of the source element. The Application Studio ID displays for source elements that require developers to specify an ID when the element is added to an app.
Source elements that do not require an ID in Application Studio, such as the Exit App element, display a GUID.
Set next step
Specifies the next source element to be executed. The point of execution moves to the specified source element, which can be located either before or after the current source element. For more information, refer to Run a specific source element in debug mode.
Set breakpoint
Specifies a source element at which the app stops. You can set an unlimited number of breakpoints. For more information, refer to Set a breakpoint for a source element.
Remove breakpoint
Removes a breakpoint from a specific source element. For more information, refer to Remove breakpoints.
Config Elements in the debugger
If your environment uses configuration elements, the Config Elements section of the debugger displays information about each element. Global configuration elements display whether an app is open or not. App-specific configuration elements display when the associated app is running in debug mode.
The Config Elements section displays the following information for each configuration element.
Name
Displays the name of the configuration element. For more information about configuration elements, refer to About configuration elements.
Value
Displays the value of the configuration element.
System Variables in the debugger
The System Variables section of the debugger displays system variables and their associated values.
The following information displays for system variables, if available.
Name
Displays the name of the system variable. For more information about system variables, refer to System variables supported in the formula editor.
Type
Displays the system value's data type. Possible values are S (string), or N (numeric).
Value
Displays the value returned by the system variable. The default value for string variables is an empty string. The default value for numeric variables is 0. If a variable is referenced in the app, or in the formula tab of the console, the value changes to reflect the most recently returned value.
Variables in the debugger
If your app contains variables, the Variables tab in the debugger displays information about each variable.
The following information displays about each variable in your app. You can use the search field to filter the list.
ID
Displays the ID of the variable.
Type
Displays the type of variable data. Possible values include string, date, record set, or numeric.
Value
Displays the value of the variable. Blank values indicate an empty string.
Datasources in the debugger
If your app uses a datasource, the Datasources tab displays information about each Mobile Client table, function call, or download used as a datasource. If your app includes a wire, you can also view information about your wire datasources.
The following information displays for each datasource. You can use the search field to filter the list.
ID
Displays the ID of the datasource.
Type
Displays the datasource type.
You can inspect the contents of table or wire datasources from the Preview window.
Form Controls in the debugger
If Forms Development is licensed, and your app contains a form, the Form Controls tab displays in the debugger. This tab provides information about the form and each control within it. You can select a control from the list to display its properties in the Preview section.
The following information displays for each form control. You can use the search field to filter the list.
ID
Displays the ID of each form, form control, or data control.
Type
Displays the type of control. For more information about control types, refer to Form controls or Data controls.
The following information displays in the Preview section after you select a form control.
Name
Displays the name of the property.
Type
Displays the property type. Possible values include String, Boolean, and Numeric.
Value
Displays the current value for the property.
Wire Controls in the debugger
If your app contains a wire, the Wire Controls tab in the debugger displays the objects in your wire in a tree view. The tree view allows you to show and hide nested objects. You can select an object to display its attributes in the Preview section. Additionally, you can hover over an object to highlight its location in your wire.
The following information displays in the Preview section after you select a wire object. The list of attributes is organized by function.
Attribute
Displays the name of the attribute used in the object. For more information about wire attributes, refer to Wire attributes.
Value
Displays the value of the attribute.
Wire Actions in the debugger
If your app contains a wire, the Wire Actions tab displays a list of the actions in your wire in a tree view. The tree view allows you to show and hide the actions nested within each action block.
The following information displays in the Preview section after you select a wire action.
Attribute
Displays the name of the attribute used in the wire action. For more information about wire attributes, refer to Wire attributes.
Value
Displays the value of the attribute.
Preview
The information displayed in the preview window varies based on the item you selected from the tabs above it. The preview window allows you to inspect items more closely and monitor changes in data.
The following tabs can open items in the preview window.
Console
Developers can use the console to access more advanced troubleshooting options. The console enables you to view more detailed information about each source element and information about the memory usage of your app. Additionally, you can run formulas, SQL statements, JavaScript, and Wire evaluations from the console.
The following console tabs enable you to troubleshoot apps, forms, and wires.
App Log
Displays the ID and description of the current source element. Additional information about each source element also displays. This information varies based on the source element, and is populated from the settings for that element in Application Studio.
Formula
Allows you to enter formulas and formula functions into the console, and returns the value of the formula. This is useful when troubleshooting issues with specific formulas.
Database Queries
Allows you to enter SQL select statements for database tables referenced in your app. This allows you to verify that Mobile Client is able to locate specific information from your database tables. You can not make changes to a database table from the console.
Javascript
Allows you to run javascript from Mobile Client for HTML5. This is useful when troubleshooting Javascript functions in a wire. You can also use this feature to verify that the javascript you run from Mobile Client returns the results you expect. For example, you can use an AJAX call to see if Mobile Client is connecting to a specific server.
Wire
Allows you to enter a wire evaluation and returns the result of the evaluation. This is useful when troubleshooting issues with specific expression or looking up data values. For more information about wire evaluations, refer to Wire evaluations.
Memory
Displays the memory usage of the browser tab running the app.
Loading...
There was a problem loading this topic