Table of Contents
Advertisement
CA50 Web Application Developer Guide
This section provides a functional description of the operation of the browser and the customized tags.
To work with the UCA client application browser, the responses generated by the Web server adhere to the HTML
specification to the greatest extent possible. Due to the small display on the CA50 client, many HTML tags are not
applicable. For example, a graphical submit button would use most of the rendering window for the browser. In
addition, the UCA client application does not have a pointing device and has limited physical buttons or keys.
Therefore, proprietary HTML element attributes were designed and implemented to submit form data based on
scanner data or physical buttons as input tag. There are also some proprietary HTML meta tags that provide
additional functionality.
The UCA server installation includes a few sample CA50 Web applications. In the default installation, the source
can be found in the following directories:
\Program FIles\Motorola\UCA Server\Development Toolkit\Sample Lookup and
\Program FIles\Motorola\UCA Server\Development Toolkit\Sample Lookup2.
Launching a Business Application
Business applications can be launched by associating the application URL to the selection of a menu item in the
base profile, or by associating the application URL to an action taken from the desktop (like scanning a bar code).
In the default sample profiles installed on the server, see the desktop element and the application menu elements
for examples of both. These examples can be modified to reference the URL of any CA50 Web application. For
more details, see
Chapter 7, XML Profile for
Automating the Launch of the UCA Client Application
For details, see
page
Employee Identity Validation
For details, see
PIN
Configuration.
12-2.
Input,
Figure 4-5 on page
4-3.
CA50 Business Application Development 10 - 3
Advertisement
Table of Contents
Troubleshooting
