Try OpenEdge Now
skip to main content
Developing WebSpeed Applications
Controlling WebSpeed Transactions : Transaction control with HTML-mapping Web objects

Transaction control with HTML-mapping Web objects

WebSpeed allows you to code an HTML-Mapping Web object by customizing well defined sections of the code managed through the AppBuilder Code Section Editor.
In addition to the outputHeader and process-web-request procedures (described in Implementing transaction control), the default HTML-mapping code sections include:
*htmOffsets — (Read only) A procedure that automatically associates each form field with the corresponding field object (widget) in the Web object. The AppBuilder provides this section for reference only.
*Definitions — Where you can code preprocessor, parameter, and variable definitions that apply to the entire Web object.
*Main Code Block — The part of a Web object that performs initialization and executes process-web-request. Generally, this is not a section that you modify unless you want to execute code once the first time a state-aware Web object is called.
*Control handlers — Where you can override the default web.input and web.output control handlers for a specified field object. This code section appears only in HTML-mapping Web objects.
*ADM methods (event procedures) — Procedures that provide standard behavior for the HTML-mapping process-web-request and other sections of an HTML-mapping Web object. You often create overrides to these standard event procedures, for example displayFields, assignFields, or initialize.
* Anatomy of process-web-request in HTML-mapping
* Modifying the request logic
* Moving data through the HTML mapping Web object
* Creating Definitions
* Modifying the Main Code Block
* Customizing field object control handlers