Preview of successfully recorded Oracle Forms requests:
Each Virtual User may contain several pages that, in turn, may each contain several requests.
An Oracle Forms request is displayed in XML format. It comprises one or more
DataMessages, with one or more
Oracle Forms messages only contain graphical information. The Oracle Forms applet running in the client-side browser acts as a
slave to the server, sending the user's actions and waiting for instructions on the graphical changes to apply.
An Oracle Forms message is a set of graphical actions, as can be seen in this example of a request:
Dialog element indicates the message principal purpose; in this case, it is an
UPDATE -type message for the applet graphical interface. It contains several messages, each
DataMessage element describing an action applied to one of the interface graphical components.
Some examples of graphical components: Window, Canvas, List, TextField, and so on.
DataMessage references a graphical component by its
DataMessage has several attributes:
actionCode: indicates the action applied to the graphical component. Examples:
handlerId: the component unique identifier. In requests and responses, graphical components are referenced using a unique identifier, the
handlerIdidentifier is created and assigned to a graphical component by the server.
handlerClassId: indicates the graphical component type. Examples:
CHECKBOX_ITEM, 539. A number in this field indicates that the type of the component referenced by the
DataMessagecould not be identified.
handlerName: indicates the graphical component name within the applet.
properties: describes the changes made to the graphical component. Each property has an
DataMessages to have a
DataMessagethat references the component will not have a
Oracle Forms requests are named according to the following rule:
handlerName: name of the graphical component. If no name is found, it is replaced by the appropriate
propertyType: type of property
propertyValue: value of the property
login_username_0:value=u3 indicates that the
login_username_0 graphical component has been given the value