Viewing error messages
Tasks contains a list of compiler errors and warnings. Compiler errors preclude successful web project compiling and must be eliminated. Development states that cannot be compiled cannot be released because the corresponding web application do not run.
Compiler warnings relate to missing extensions, or to messages concerning accessibility. If compiler warnings are the only type of message that is generated, the development state will be successfully compiled nonetheless.
If individual messages are displayed hierarchically, it means that the errors indicated occur at various places in the web project. This can happen, for example, in connection with a missing extension that is referenced by a number of nodes. In such cases, the error need only be eliminated once.
To call up the relevant node in the definition tree view, double-click a table entry; the Web Designer will then automatically go to Node editor. This behavior applies if the error is in the node. If the error occurs when the resulting code is compiled, you can double-click it to display Generated code (read-only) in the definition tree view.
Table 64: Functions in the object state window toolbar
||Display error message.
This button is only active when an error message has been highlighted in the list. By clicking this button a detailed error description is displayed. You can send an email message in the default email program using Send as Mail. The error message is automatically transferred to the email.
By clicking this button, errors can be shown or hidden.
By clicking this button, warnings can be shown or hidden.
Querying a web application
Web SQL expressions can be created and run in the query window. However, in order for this to occur the compilation must be successfully completed. This window integrates a toolbar of its own. The query window is divided into three sections.
NOTE: A WCF connection must be created for this function.
On the left, the currently available session collections are shown. The internal currently selected session is preset in the toolbar selection. Individual collections are bundled under the modules or components in which they were originally defined. The number of rows within the collection is shown next to the collection.
If you mark a database object in the hierarchy, the following context menu items are available. Which menu items are shown, depends on the database object you have marked.
Table 65: Context menu entries for marked collections
|Show definition object
||Takes you to the definition object in the definition tree view and marks the nodes with a color.|
|Show collection data (this entry is only available for a selected collection)
||This displays an expression for the query in the SQL input box. More information about the collection is displayed below the SQL input box.|
|Show last used WHERE clause (this entry is only available for a selected collection)
||This displays the last WHERE clause in the SQL input box. More information about the collection is displayed below the SQL input box.|
On the right-hand side of the window is a SQL query window. Here you can enter a query statement to be run. The results of the query are also displayed in the part of the window.
To select another session
To view the current module
To view the collection contents
- In the hierarchy, mark the collection.
Table 66: Toolbar functions in the "Queries" view
Sends a query.
The entered expression is run by clicking Web SQL. If more than one such expression has been formulated, mark the expression that is to be run. Only one expression can be run at a time.
The expression being run is evaluated against the module or component currently selected in the tree structure. Use Web SQL syntax for inputting the expression to be run.
If the queried collection is a part of a component, the suffix must be appended to the collection name. the suffix displayed on the left side of the query window must be added to the collection name.
If an asterisk (*) is inserted in an expression as a placeholder for the columns that are to be displayed, only those columns that are needed (referenced) in the module are displayed.
To reopen a closed query window
- In the toolbar, in the View menu, select the Query menu item.
Metadata from a web application query
A column, _DebuggerData, with additional meta data is returned from the web application query.
Table 67: Meaning of the output in the "_DebuggerData" column
State of the entity.
Specifies whether this is an interactive entity (IsInteractive=True).
Specifies whether the data is read-only (IsReadOnly=True) or read/write (IsReadOnly= False).
For more detailed information about working with entities, see One Identity Manager Configuration Guide.
Evaluating the Web SQL expression of a property
This function is a debugging extension and is only available in debug mode. The evaluable Web SQL properties of an XML node for a specific control can easily be evaluated at runtime.
The Label node type, for example, has Text and Tooltip text Web SQL properties. Identifier and Value are additional Web SQL properties that are stored as HTML attributes and are Web SQL-evaluable.
NOTE: If Web SQL expressions are not available during runtime, these expressions are extracted from the XML definition. If the runtime code no longer corresponds to the XML definition, a different result may be obtained from Web SQL expression evaluation.
In the steps below, the evaluation is described using the Label node type as an example.
To evaluate the Web SQL expression of a property
- In the preview, mark the database object that needs to be displayed and select the properties view.
The database object, represented as an XML node, is marked in the properties view.
The evaluable Web SQL properties belonging to the XML node are determined in the background and are listed as entries in the context menu. These entries are selected in the next step.
- Click the marked XML node and select Evaluate label....
All the corresponding modules are listed in the tree structure in the query window and the definition for the selected Web SQL property is displayed in the SQL input box.
- In the query view's toolbar, click .
The results are shown below the SQL input box.