10 - 8 CA50/UCA Client & Server Developer & User Guide
HTML Elements Contained in the Body Element
The proprietary HTML elements contained in the body are all custom "input" elements.
Input elements are not rendered even if they are of type text due to the dimensions of the display. The UCA client
application behaves as though the custom input tags are visible and "clickable" by a user. Each custom input tag
must be within a form element. All input fields that are not of type "submit" or "button" and the input field that was
activated are sent to the server using the value of the "action" attribute and the value of the "method" attribute. The
form data is sent as GET or POST based on the value of the "method" attribute. POST is used if the "method"
attribute is not contained in the form element.
Table 10-2
HTML Elements Contained in the Body Element
Element
Description
<input type=type = "submit" id="ScanData"
name="Price" value = "" />
This input element allows a form to be submitted when the user scans a bar
code label. The id attribute's value must be "ScanData" and the type attribute
must be "submit" or "button". The value for the "value" attribute is the bar
code label scanned when the form is submitted. The name value pair is as
follows, "Price=xxxxx" where "xxxxx" is the bar code label scanned.
<input type="submit" id="LeftSoftKey"
name="SoftKey" value="Prev" />
This input element allow a form to be submitted when the user presses the
left soft key on the CA50 device. The id attribute's value must be
"LeftSoftKey" and the type attribute must be "submit" or "button". The value
for the "value" attribute is the label for the left soft key on the device. Keep in
mind that keys defined by the Web application take precedence over the keys
defined in the <MenuStates> area of the XML profile.
Note: The name attribute's value must be the same as the value for the name
attribute of the "RightSoftKey" when both are on a page of the business
application.
<input type="button" id="RightSoftKey"
name="SoftKey" value="Next" />
This input element allows a form to be submitted when the user presses the
right soft key on the CA50 device. The id attribute's value must be
"RightSoftKey" and the type attribute must be "submit" or "button". The value
for the "value" attribute is the label for the right soft key on the device. Keep in
mind that keys defined by the Web application take precedence over the keys
defined in the <MenuStates> area of the XML profile.
Note: The name attribute's value must be the same as the value for the name
attribute of the "LeftSoftKey" when both are on a page of the business
application.
The labels for the soft keys are displayed above the physical buttons on the
device. In addition, the soft keys are controlled by the UCA client application
if these soft key inputs are not present.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......