Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/166—Editing, e.g. inserting or deleting
  • G06F40/174—Form filling; Merging

Definitions

• the present invention relates to application development tools for handheld personal digital assistant devices, such as Palm Pilot, and particularly to a rapid application development tool that allows users to automatically generate a customized data collection software application for use on hand-held and wireless mobile computing devices based upon a specifically prepared pre-formatted document, and further enables the deployment and flexible delivery of formatted output forms including the collected data information therein.
• PDA personal digital assistant
• Palm ® and other Palm OS devices are enabling today's workers to be more efficient and productive.
• the advent of newer mobile device platforms, including Pocket PC and RIM and the growing infrastructure for wireless connectivity to the Internet and private networks are expanding the role of mobile devices and their ability to improve worker productivity. While devices and infrastructure are the backbone, they are not enough.
• Application software enables these devices and networks to accept, validate, process, store consolidate, format and deliver information in specific ways.
• Application software is expensive to develop test, support and maintain. As a result, small pools of users and individual users have not been able to justify the cost of custom mobile data entry applications.
• RAD application development
• Fig. 1 is a block diagram 10 depicting the system architecture enabling document driven programming according to the principles of the invention.
• Fig. 2(a) depicts the process 100 for creating and uploading forms according to the invention.
• Fig. 2(b) depicts the process 125 for running portable forms applications on a portable hand-held device according to the invention.
• Figs. 3(a), 3(b) and 3(c) depict examples document templates capable of being uploaded to the document upload web server for portable form generation.
• Fig. 4(a) depicts a world-wide-web/Internet based home page located on the portable forms web-server 26 ( Figure 1) and Fig. 4(b) depicts the interface for uploading a form file.
• Fig. 4(c) depicts a pop-up window 335 providing browse capability to enable user selection of a created template.
• Fig. 4(d) depicts a pop-up window 340 displayed to indicate the successful storage of the file upload 344, and, providing an indication 345 of the name by which this form may be selected by the hand-held devices.
• Fig. 4(e) depicts the interface 350 provided for enabling the modification of form variables 353 and data transfer locations 355 or, definition of new form variables or data transfer locations provided for an uploaded template form.
• Fig. 4(f) depicts a pop-up window 375 displayed to provide selection of field type and user prompt.
• Fig. 4(g) depicts a pop-up window 390 displayed to provide selection of transfer type and destination.
• Fig. 5(a)-5(d) illustrate an example of a simple template form 250 , Fig. 5(a), and three corresponding data.transfers available for output including: an e-mail document transfer 255 (Fig. 5(b)), facsimile document transfer 260 (Fig. 5(c)), and an e- mail of a data set for delivery to Excel or another database 265 (Fig. 5(d)).
• Figs. 6(a) and 6(b) depicts the interface of a client application from a computing device running Palm OS. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
• the present invention is directed to a document driven programming system and methodology that enables the creation of software applications for handheld and wireless mobile computing devices by extracting variable definition information from documents created in a variety of text editor programs. These applications are then available for use on a variety of handheld and wireless mobile computing devices.
• the system comprises creating a user created document (template) for data collection that uses structured variables for data collection points.
• This document is then uploaded to a networked server where variables are extracted to a database and assigned a document identifier, variable field types can be modified and where the uploaded document is stored for delivery reference.
• the variables Upon request for the document identifiers, the variables only are extracted from the database and downloaded to the requesting device in an active format for the user to use.
• the user Upon presentation of the variables on the device, the user is offered the opportunity to fill in the data collection points prompted by the variables.
• the collected data can be stored on the device and/or uploaded to the server. The user can repeat the data collection multiple times.
• FIG. 1 depicts a generic block diagram of the system architecture 10 enabling document driven programming according to the principles of the invention.
• the system includes a computing device 13 such as a client PC equipped with a client browser and a form creator program.
• the form creator may be a word processor/text editor program which may include PC platform text editors such as Word, WordPerfect, WordPad, Lotus WordPro, and the like.
• spreadsheets or other form creators may be used including, but not limited to, formats such as text, html, word doc, xml, pdf, as well as electronic forms formats such as
• a specifically prepared rich text formatted document alternately referred to as a "template”
• a template which is then translated into a customized data collection software application based upon specific value entries on the document.
• the template document is uploaded over a public computing network, e.g., the Internet 99, to a networked web server device 26 which may be one of a larger server cluster 25 comprising a plurality of server devices 26a,...,26n, having one or more dedicated functions (communications, load balancing, database, etc.).
• template document uploads to web server device 26 via the Internet is provided over a secure sockets layer (SSL) connection, or like secure data transfer link.
• SSL secure sockets layer
• the template documents are uploaded to a user account maintained on the server.
• the server device 25 is preferably a robust, highly scalable server software application that performs three primary functions: 1) creates custom data entry applications based on template documents and field definitions; 2) receives, translates, formats, and delivers collected data in a prescribed format to one or more specified destinations; and 3) maintains user accounting and management functions.
• the web Server 26 may be installed and operated on a public or private network by an enterprise customer that is using the document driven programming tool either for multi-user data collection applications or as an individual employee productivity tool. Alternatively, individual subscribers may have an account with a web-site and access the web server.
• the server 26 includes accounts that provide access to users of specific applications.
• the server also provides an account hierarchy for the managing of shared and non-shared documents.
• the custom data entry application is created at the server by extracting the variable definition information from the template documents.
• the data entry application is then accessible via the user accounts included on the server.
• a user can set specific data attributes for the information to be collected based on the needs of the user and the types of information to be collected at the point of capture. It is understood that these can also be set automatically by the server 25.
• An example of possible attributes include data type for variable, i.e., text, numeric, formulas, lists of choices, yes/no logical, constants, and collections of results of a determinate or indeterminate size; choice lists that can be shared by multiple variables; sections of templates that can be defined by establishing Header variable types; user prompts for individual data elements can be specified, and; lists of choices can be externally called by identifying addresses where the data choices reside.
• the communication of the choices is preferably made via XML mark-up language, though other techniques such as File Transfer Protocol (ftp) may be employed.
• Some specific features the application may support include, the entry of bar code scan entries for any variable field; the entry of comments via an on screen keyboard, the provision of a digital data input field for receiving image input data, for example, from handwritten drawings, signature capture, a digital camera, or voice data from an integrated voice recorder, or; delivery of collected data locally to local area network during communications activity. It is understood that, besides defining the individual data fields, the template definition process includes the specification of delivery options and other conditions regarding the portable forms may be set.
• the custom data entry applications may be deployed to handheld or mobile computing devices 35 a, 35b for use in the field.
• the handheld or mobile computing devices 35a, 35b communicates with the server 26 to retrieve the applications for collection of information. Connection to this server can be made either wirelessly, e.g., via a I.E.E.E 802.11, cellular, packet radio, or like wireless connection 29, or through wired connections to a computing device 39, e.g. via a hot sync 38.
• Created data entry applications are operated either in a browsing session or, on client applications operating on the handheld, mobile computers 35a, 35b. These sessions can share the application at the same time to build a shared data set.
• the handheld, mobile computers 35 a, 35b communicate the data back to the web- server cluster 25 which formats and delivers the data to recipients specified by the user as part of the application creation process.
• the web server 26 includes functionality for formatting the collected data for delivery in a variety of methods including: e-mails 41 of the filled out document, faxes 42 of the filled out document, e- mails of the information collected in standard text formats, and Internet delivery of the collected data via http and/or https posting of XML or variable pair sets.
• Other delivery options include, but are not limited to: e-mails of a completed, formatted template as an html formatted e-mail; facsimiles of a completed, formatted template document; e-mails that contain completed, formatted template documents as an attachment; e-mails that contain the collected data set in comma separated variable format as an attachment; posting of the collected data for storage in a client accessible database 44 which can be later downloaded for data exchange; delivery 43 of the collected data set to an Internet web address URL in variable/pair formats, the addresses of which can be called either as http or https ssl encrypted formats, or; delivery of the collected data set to an Internet web address URL in XML format, the addresses of which can be called either as http or https ssl encrypted formats.
• a local printer 45 Users further have the ability of reporting collected data onto a local printer 45. Connection to the printer could be, without limitation, hard wired, infrared or Bluetooth. With respect to comma separated variable format, this is a file format typically used to transfer data between databases and spreadsheets 44. Each line up to the carriage return is considered a record and fields within each record are divided by a comma. In either format, there is no limit to the number of individual data sets delivered during a session.
• Figure 2(a) depicts the process 100 for creating and uploading forms according to the invention.
• a first step 102 includes writing the document template and saving it in a recognizable format.
• document templates may be created in Microsoft Word Document Format (*.doc) or Rich Text Format (*.rtf), text, html, spreadsheet formats such as xls, xml or PDF, but are not limited to these formats.
• Figures 3(a), 3(b), and 3(c) depict examples of document templates 200 and
• the example template depicted in Figures 3(a) and 3(b), is directed to an order/invoice data entry application.
• the document templates may include functional sections and portions that are defined as special heading types. Heading types divide the form into functional data work flow areas or sections for ease of use.
• a variable declaration section 205 including variable names 202, 204, 206, etc., that are embedded in square brackets.
• FIG. 3(c) there are header variables shown at 242-246. It is understood that other embedded variable name delimiters may be used.
• Variable names may be both human readable and non-human readable.
• the variables may appear in order of their first occurrence in the document. Formatting such as fonts, images, icons, tables, logos and other graphics are permitted on the template documents.
• the example template 200 of Figure 3(b) defines a table 220 having the fields where the data is to be entered in the created application by the user.
• Embedded in the variable declaration may include, but is not limited to: type, for example, a number 206; decimal precision, for example, a unit price field 210 having two (2) decimal place precision; user prompt ordering on page, for example, a delimiter for prompting entry of a fax number 213; and or choice elements lists.
• fields e.g., fields 216, 217 provided with computational functionality, e.g., addition, multiplication, and formulae, etc.
• areas for placement of comments, signature images, digital photo images and other data may be defined in the example template 200 of Figure 3(a), is a transfer section specifying the manner in which the populated form is to be transferred.
• the example template 200 of Figure 3(a) specifies transfer by facsimile 213 and e-mail 228.
• a Field Reordering utility which comprises syntax enabled to change the ordering of variables in the system by embedding the field order into the template.
• a template includes the following sections and specified field information:
• the implementable features include: the expansion of Text Area which is for the purpose of enabling data entry of an unknown size, particularly bar code scans; Lookup and fill-in fields, whereby based upon a selection of a value, other values will be automatically placed into other fields; Editable Date and Time Fields whereby users will be presented with graphic user interface for quick entry of these values on demand; an
• External List whereby during a communications session the server device will go to an external internet URL to receive a formatted xml document which includes up to the minute choice values; the addition of a signature image area which is an area permitting the entry of graphic data such as handwritten signatures, handwritten notes and other binary image data; preset values which are text and numeric fields that have "starting values" which may then be changed by the handheld computer user; validation fields which provide users with the ability to set business logic to test values that are entered for validity; and, Portable Printer support which includes a graphic user interface generated to establish output criteria for portable receipt and label printers.
• a document is written and saved in the acceptable format (e.g., *.RTF)
• the user may upload the document into the networked web server device 26.
• this requires secured access to the web- server 26, hereinafter referred to as a "Portable Forms" web-server.
• a user is provided with functionality to enable uploading, sending, modifying or deletion of templates (forms) via the user's web-browser.
• a portable forms interface is provided with functionality enabling template upload which is performed at step 106.
• the invention provides the ability to share forms between accounts via a master account that contains one or many user accounts.
• the server according to assigned rights for each user or user type, may govern access to specific documents, fields or other attributes.
• Figure 4(a) depicts a world-wide-web/Internet based home page located on the portable forms web-server 26 ( Figure 1) for accessing user created forms and mamtaining and updating user accounts. As shown, the home page provides an interface
• an option 302 providing functionality for sending a form to a fax machine or e-mail address
• an option 304 providing functionality for uploading a template to a user account file storage area
• an option 306 providing functionality for deleting a created template
• an option 308 providing functionality for modifying a created template
• an option 310 providing functionality for updating a user's personal account information.
• a web page is displayed providing an interface enabling the user to upload a created template for association with that user's account.
• Figure 4(b) depicts the interface 320 provided for enabling the uploading of a form file.
• the interface provides a user with an entry field 323 for providing entry of a form name that will eventually be selectable via the user's hand-held computer, and an entry field 327 for enabling entry of the file name where the created template file may be found in the user's computing device.
• a pop-up window 335 is displayed providing browse capability to enable user selection of the created template. Once these fields are populated, template upload is effected by selection of the upload button 329 ( Figure 4(b)) and, upon successful uploading, as shown in Figure 4(d), a popup window 340 is displayed indicating the successful storage of the file upload 344, and, providing an indication 345 of the name by which this form may be selected by the handheld devices.
• step 108 indicates the facility enabling a user to set specific data attributes for the information to be collected after the template documents are uploaded to the portable forms server.
• step 108 indicates the facility enabling a user to set specific data attributes for the information to be collected after the template documents are uploaded to the portable forms server.
• a web page is displayed providing an interface enabling the user to modify a form.
• Figure 4(e) depicts the interface 350 provided for enabling the modification of form variables 353 and data transfer locations 355 or definitions of new form variables or data transfer locations provided for the uploaded file in Figure 4(d).
• a defined variable in the template may be selected by a user for editing.
• Figure 4(f) depicts an example edit field properties interface 375 enabling a user to edit a predefined variable "Owner".
• 4(f) pops up after a user has clicked on the variable name from a previous window, such as Figure 4(e), to select it.
• a user has the ability to set conditions related to "Owner” (376, 380, 382, 383, 384, 385, 386, 387, 388) including the prompt text 379 that the user will receive.
• a user can not however define any variables unless on the original form template.
• variable type which may be assigned includes: alphanumeric text 376 (will accept bar code scan if client hardware will support it); number 380 (including decimal precision), formulas 382 (which set numeric relationships between variables); date 383, list 384 (where a user sets up choice selection lists to their specifications); bulk list 385; yes/no
• header 386 (where the user establishes field as a logical true/false yes/no condition set); header
• External List - wherein during communication session the portable forms server will retrieve an XML document from an external web URL that includes list choice information based upon real time current condition sets; an "Expanding Alphanumeric field” which is an object based upon a text area of unlimited size that "grows" when multiple entries are made, and will mostly be used for bar code scanning applications where there is an unknown number of scans, e.g., one to many; A "Lookup Field” wherein based upon a value selected here, additional values will be placed into other "assignment fields” which will provide search capabilities to find data record that contains assignments; and, an Assignment Field which are placeholders for values retrieved by lookup fields.
• Figure 4(g) depicts an example data transfer edit field properties interface 390 enabling a user to edit a predefined data transfer variable including specifying delivery options such as: e-mail 391; facsimile 392; e-mail csv 393; post to URL 394 and post to xml 395.
• delivery options such as: e-mail 391; facsimile 392; e-mail csv 393; post to URL 394 and post to xml 395.
• a user upon selection of the data transfer option 391-395, a user is enabled to enter the destination address or delivery point in entry field 398.
• a user may specify delivery options such as: E-mail delivery of a completed original document with data set as an attachment; Fax delivery of completed original document with data set; E-mail delivery of data set in comma separated variable format; Web delivery of data set in variable / pair sets; Web delivery of data set in XML format; and, local delivery of a data set (in certain connectivity sessions).
• Additional delivery types are available including: HTML e-mail of completed original document; and, conversion of documents to image files for delivery to document management systems.
• Figures 5(a)-5(d) illustrate an example of a simple template form 250
• Figure 5(a) and three corresponding data transfers available for output including: an e- mail document transfer 255 ( Figure 5(b)), facsimile document transfer 260 ( Figure 5(c)), and an e-mail of a data set for delivery to Excel or another database 265 ( Figure 5(d)).
• applications created on the portable forms server 26 are delivered to handheld computers.
• these client applications will run on a PDA, Pocket PC platform, or full Windows® device and communicate with the portable forms server 26.
• the client takes the information stored on the server and translates it into data collection applications.
• the document driven programming client applications of the invention exists in a browser client version, a client for Palm OS, and a client for Pocket PC and BlackberryTM devices.
• the document driven programming client applications of the invention exists for IP phones with display screens that may be portable or hardwired.
• Figure 2(b) depicts the process 125 for running portable forms applications on a portable hand-held device according to the invention.
• Created data entry applications are operated either in a browsing session or, on client applications operating on the handheld, mobile computers 35a, 35b.
• a user logs on to the portable forms web page or microbrowser page via the user's handheld or mobile computing device.
• the user will select the form to be retrieved from the portable forms web server at step 130.
• the user receives the custom data collection application based on template document and custom settings and fills out the form on browser screen or hand held computer.
• the form populated with the entered data is delivered according to the data delivery transfer specification provided in the template.
• a client application may be run on hand held computers that wirelessly connect to the Internet, e.g., on a variety of platforms including Palm OS, Pocket PC and
• a Palm Pilot interface screen 425 first presents a means for enabling real time microbrowser access to the web site providing the portable forms functionality via a wireless Internet connection.
• an interface screen 435 such as depicted in Figure 6(b) is presented that prompts the user to log into that user's account, for example, by entering a user_name and password combination 436.
• a user may access all the forms that the user has created.
• a further microbrowser screen display 445 such as depicted in Figure 6(b), is presented that enables user selection of a created form
• a further screen display may be provided providing a menu of options enabling a user to specify data transfers, to fill out a downloadable form, or to send the form.
• a user may be prompted to enter data transfer methods and locations via interface screen 450 such as shown in Figure 6(d).
• An interface screen 460 such as shown in Figure 6(e) is provided that provides the form sheet having the defined variable names 473 and corresponding locations 475 enabling entry of the form data to be filled out by the user.
• FIG. 6(e) "Work_To_Be_Done” is shown in Figure 6(e). Further shown in Figure 6(e) is the provision of a selectable "Send” button 482 that initiates the upload of the data entered by the user that is to be populated in the created form. Finally, as shown in Figure 6(f) an interface display 485 is provided that enables a user to confirm that the data entered in the particular form is correct, and further enables data transfer operation of the completed form to the data transfer recipient(s) in the manner set forth in accordance with the specified data transfer methods, upon selection of the "Send Form" button 490.
• mail merge utilities are limited in the types of data that can be collected and the manner in which a field may be formatted.
• the data source is typically a spreadsheet or flat ASCII file.
• the document contains variables embedded inside of delimiters.
• the template creation may also be compared with eforms.
• eforms a web page, document or pdf is created and delivered by a server to a browser screen or editor.
• the form is filled out and delivered via fax, email, web delivery.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Health & Medical Sciences (AREA)
• Artificial Intelligence (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Computational Linguistics (AREA)
• General Health & Medical Sciences (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (5)

Publications (1)

Family

ID=30003269

Family Applications (1)

Country Status (5)

Families Citing this family (9)

Family Cites Families (1)

• 2003
  • 2003-05-05 EP EP03761897A patent/EP1535175A1/de not_active Withdrawn
  • 2003-05-05 WO PCT/US2003/013947 patent/WO2004003768A1/en not_active Ceased
  • 2003-05-05 CA CA002491435A patent/CA2491435A1/en not_active Abandoned
  • 2003-05-05 AU AU2003232052A patent/AU2003232052A1/en not_active Abandoned
• 2005
  • 2005-12-30 IL IL16604705A patent/IL166047A0/xx unknown

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events