You can inspect the rendered definition, live AngularJS data, per-view metadata, and server diagnostics of a deployed MDriven Turnkey application when you develop or troubleshoot a ViewModel.

Choose the right runtime information

MDriven Turnkey exposes different kinds of development information. Use the page that answers the question you have:

Need	Use	What you can inspect
Understand how a ViewModel definition was rendered	/Turnkey/Development	ViewModel variables, types, rendered AngularJS widgets, bindings, CSS classes, and generated snippets.
Inspect the data in the AngularJS page that is currently open	Add /debug to an AngularApp URL	Live AngularJS page data corresponding to the rendered definition.
Read structured metadata for one view	ViewMeta	Per-view structured metadata.
Check memory and application status	Serverinfo	Memory and EcoSpace information, when debug information is enabled for the site.

Inspect a ViewModel definition

Use the Turnkey Development page to see what Turnkey generated from a ViewModel. This is useful when you need to understand a standard UI element before you style, override, or troubleshoot it.

1. Open https://<yoursite>/Turnkey/Development.
2. Select the ViewModel you want to inspect.
3. Review the ViewModel's available variables, types, and generated output.
4. Locate the widget or binding relevant to your question and use the generated snippet as the exact expression of the rendered UI.

For example, when you inspect a grid, the generated output shows how the grid is bound and how its rows are represented. It can show an ng-show expression used to control visibility, the classes assigned to table cells and rows, and the expression that identifies the current row. If a row's vCurrent value is true, the generated class expression can apply the current-row styling. This lets you trace a visible UI behavior back to the ViewModel data tree and its rendered AngularJS expression.

The Development page is a rendered-definition inspection tool. It shows the transformation from the ViewModel definition to the standard AngularJS UI; it is not a separate definition that you must maintain.

Open Development info from the portal

If your site is registered in the MDriven portal, you can reach this information from the portal:

1. Sign in to the portal.
2. Open My apps.
3. Select your application.
4. Select Development info.
5. Select the ViewModel to inspect.

The portal holds metadata about the application registration and can refresh a Turnkey installation when publishing information is available. Keep the model itself in your own source control or another location you control; do not treat the deployed runtime or portal registration as the only copy of the model.

Inspect live AngularJS page data

Use the debug route when the question is about the data currently present in a running AngularJS page rather than the generated definition.

1. Open the view in your deployed Turnkey application.
2. Identify its AngularApp URL in this form:

https://<yoursite>/Turnkey/AngularApp#/<View>/<rootid>

1. Append /debug after the root ID:

https://<yoursite>/Turnkey/AngularApp#/<View>/<rootid>/debug

1. Inspect the live page data and compare it with the corresponding ViewModel definition on /Turnkey/Development.

For example, if a row is not receiving the expected current-row appearance, inspect the rendered grid binding in Development info and then inspect the live page data in the debug route. Check whether the row data has the expected vCurrent value and whether the rendered class expression uses that value.

Do not confuse the two views:

• /Turnkey/Development explains what Turnkey rendered for a selected ViewModel.
• The /debug route exposes the data for a particular live page instance, identified by its view and root ID.

Use ViewMeta for structured per-view metadata

Turnkey also provides ViewMeta, which exposes structured metadata for each view. Use it when you need metadata in a structured form rather than the rendered AngularJS output shown by Development info.

For example, use Development info to examine the AngularJS binding emitted for a grid, and use ViewMeta when your task requires the view's structured metadata instead of its visual rendering details.

Check server and memory information

Use Serverinfo for runtime memory and EcoSpace information. Serverinfo becomes available when the Turnkey site is configured to show debug information in the portal.

Server diagnostics are separate from view diagnostics:

• Use Development info and the AngularJS debug route to investigate a ViewModel and a live page.
• Use Serverinfo to investigate application status, memory, and EcoSpace information.
• Use the application logs when you need recorded runtime deviations. See Serverinfo for log location and logging requirements.

A practical troubleshooting workflow

When a standard Turnkey UI element does not behave as expected, work from definition to live data:

1. Open /Turnkey/Development and select the relevant ViewModel.
2. Find the generated widget, binding, event expression, or CSS class involved.
3. Open the same live view with the /debug suffix.
4. Compare the live values with the values referenced by the generated expression.
5. If the issue concerns application health rather than view data, check Serverinfo and the application logs.

For a walkthrough of rendered definitions and AngularJS bindings, watch the Turnkey rendering and overrides walkthrough.

See also

• Documentation:Serverinfo
• Documentation:Turnkey local development tips
• Training:Taking It Further Still
• Documentation:Framework