Classes, objects and properties
In a USoft runtime web application, each page and each control is an instance of a class. The behaviour and (if applicable) the look of the runtime software depends on:
Page classes
In Web Designer, a page class is the definition of a browser page in a USoft web application. A page based on a page class can be published to a web service and thus be made available to your end users. They navigate to a page in different ways, for example by selecting a main menu option, or by clicking a hyperlink in a different page.
Layout areas
Layout areas are sections of web pages that have a specific purpose within the page. Often, they are rectangular areas that are visually marked out from surrounding areas.
Input controls by type
This help topic discusses input controls by type.
Messages
In a web application, messages (both information and violation messages) can be displayed in several ways:
Sharing catalog items
All catalog items (with the exception of Page Sets) can be shared by exporting and importing them as XML files. This enables you to:
How to display data as hyperlink
For input controls that contain data representing a URI or URL, you can specify that this data must be displayed as a hyperlink
Setting a variable set with the URL protocol
Variables can be set in an internet browser window, by specifying the url:
How to make a page read-only
After you have designed a page, you may want to protect it from accidental changes. To do so, you can make it read-only. If pages have been set to read-only, this is indicated in the title bar of the object tree.