Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Identity Manager 8.1.4 - Web Designer Reference Guide

The Web Designer editor Web Designer structures and functions The Web Designer object model Working with the Web Designer Web project configuration options Customizing the Web Portal Basics of Web Designer programming Compiling and debugging Monitoring Frequent tasks in the Web Portal

Viewing information specific to just one database object in the query window

In the query window, you can use a filter to display information concerning one database object only, such as a component. This function can be applied to Module or Component database objects. By default, this filter is not enabled. If the information you require appears in several components or modules, you can open another database object with the filter enabled in the definition tree view. The information concerning the newly selected database object is displayed in the query window.

This function is available in debug mode.

To narrow the display in the query window to a specific database object

NOTE: Before using this function, select the relevant database object and the corresponding property. For more information, see Evaluating the Web SQL expression of a property.
  • In the query view, enable the Filter on option.

    The information displayed in the query window concerns the open component or module only.

    NOTE: If there is no information relating to the selected database object or if the selected document is not a component or module, the icon is shown next to the filter.

Debugging

If error messages are shown in the preview while the web application is running, the Web Designer provides different forms of help.

NOTE: A WCF connection must be created for this function.

You can set breakpoints in the definition tree view for debugging. For more information, see Setting breakpoints.

You can use the following buttons in the preview to manage the Web Designer debugging.

Table 68: Buttons for managing debugging in the preview
Icon Function
Enable debugger.
Single step mode.
Resume execution

For more information, see Working with the preview.

An external program can also be used to debug the web application (for example, Visual Studio). Debugging steps are created in the debug compilation to help you with subsequent debugging. Debugging with external programs is dependent on the environment used. This approach is therefore not referred to again here.

For internal debugging, called-up methods can be displayed in the Call Stack view. This gives you important information on the source of the error.

For more information, see Call stack.

Setting breakpoints

To set a breakpoint

  1. Perform one of the following tasks:
    1. Open the relevant module or component in the navigation view.
    2. Select a corresponding object in the properties view and click .

    For more information, see Properties.

  2. Mark the node where you want to set the breakpoint and select Set breakpoint.

    NOTE: Not all nodes in the definition tree view can support a breakpoint. However, as a general rule, you can set a breakpoint on all nodes that can be suspended in single step mode. You can also set a breakpoint for Container, Label, or Button nodes. In these cases, a breakpoint is set as soon as the control is rendered.

    The marked node is highlighted in red.

To remove a breakpoint

  • Mark the node that has the breakpoint and select Remove breakpoint.

    The marked node is no longer highlighted.

Call stack

Call stack contains a list of internal action calls when the debugger is enabled and a breakpoint activated. For more information, see Setting breakpoints. All actions executed during the breakpoint are listed. This information can be used to identify the C# methods and related DLLs causing the error.

NOTE: The description of the Call Stack given here only helps you to pinpoint the error source For debugging itself, use external development tools such as Visual Studio.

Call Stack provides the following information:

  • Method

    Name of the method called up

  • DLL

    DLL name. The DLL provides you with the origin of the method.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating