CA2533318A1

CA2533318A1 - Policy-driven mobile forms applications

Info

Publication number: CA2533318A1
Application number: CA002533318A
Authority: CA
Inventors: Marc Chene; Kevin Mcguire; Liam Peyton
Original assignee: Truecontext Corp
Current assignee: Truecontext Corp
Priority date: 2005-01-19
Filing date: 2006-01-19
Publication date: 2006-07-19
Also published as: US7774504B2; EP1842140A4; WO2006077481A1; US20060161646A1; EP1842140A1

Abstract

A system for capturing data via an extensible markup language form is disclosed comprising a policy-based mobile content engine, a mobile-Forms application client, and a transport engine. The policy-based mobile content engine is adapted to process a plurality of definitions from one or more mobile-forms application definition files. The policy-based mobile content engine translates the mobile-forms application definitions into policies and actions enforced by the policy-based mobile content engine. The mobile-forms application client has a plurality of rendering engines targeted for a mobile user device to render form controls and to process the forms-based application. The mobile-forms application client is operable on a mobile user device and is adapted to capture the data as an extensible-markup-language document. The transport engine is adapted to transport the mobile-forms application definition files and captured data through a transport layer between the policy-based mobile content engine and the mobile-forms application client.

Description

I'OLTCX~AR.IVEN MpBILE FORMS APPLICATIONS
~IF:Li) pF THE INVENTION
(040'1 ) The present invention relates benerally to content management and, more particularly, to a system and method for defining, deploying, and managing mobile forms applications, in a mufti-tenant (mufti-domain) hosted environment, that can display and capture data on a wide variety of mobile devices in the context of a business workflow routed through a wide variety of intermittently connected networks both inside and outside o.f corporate 1'irewalls.
BACKGROUND OF THE iNVENTtON

[0002] Today, tz~ost data in field force industries (e.g., fiEld sales, field services, inspection and reporting, etc.) is distributed and captured on paper-based forms. The data entered on paper-based forms are typically returned to the business offtce to be rrtanually entered electronically and integrated with a back office system. furthectnore, an enterprise business process might require the captured data to be reviewed by other members of the organization (e.g., authorization, up sell opportunity, billing, ete.) before, during, or after the field has interacted with the data. The process of distributing, updating, captuung, and returning form data and adapting it to a unique business process applies to a larbE natnber of mobile workers perforrrxing a variety of tasks such as, but not limited to, inspections (e.g., property, health, etc.), sales force reporting, and work order dispatches (e.g_,1-IVAC, insurance claims, ete.).

[0003) Typically, in more complex forrns-based business processes, work requests and form data are initially dispatched to field force workers using a voice channel (e.g., cell phone) or p~~e-printed paper forms (c.g., clipboard) that is then manually tilled out or updated by th.e mobile Worker (e.g., technician). t~ completed work request might also require one or many subsequent requests (e.g_, required pans, required autharir~tion, up-sell opportunities, etc.) that are typically done through a call over a cellular phone, or return trip to the office, or may cause the displacement of the mobile worket~_ Today, field inspectors may also capture data in the feld using a series of paper forms and binders to complete their inspection tasks, resulting in a slow and inefficient pzocess.

[0004) Businesses incur high wireless voice and vehicle fleet costs due to the above-described processes used in dispatching field workers, capturing or updating form data, and completing work oxde~rs or inspection forms iz~ the held. Additionally, there are signif cant cost and inefficiencies with slow, manual processes for the exchange of data using paper-based forms, from. tb.e cost of the paper based forms, to duplicate data entry, to errors made in data capture on paper, to waiting for the person with the data to update another person or system, etc.

[0005] Electronic forms and XFonns (XML Forms) solutions (such as, Adobe LiveCycle, Microsoft Xnfopatlt, FormDocs, Altova, Advantys, MDS1, X-Smiles, formsPlayer, and Navell XForms) are generally PC-centric and Local Area Network (LAN) oriented as opposed to being opti~xzi~ed for nnobile devices arid wireless use. Additionally, these solutions are on-line and browser-centric, as opposed to being optimized for on- and off line use over intermittently connected wireless networks with varying degrees of cost and quality of service. These solutions typically do not provide mechanisms for hosting zrzulti-tenants (.rz~ulti-dotxtain) fozxns applications using a common 1T infrastructure (e.g., Managed Service Provider hosted environment), nor do they have support for sophisticated routing and tracking of forms and policiES
that define a rtZObile forms application_

[0006] Therefore, it would be desirable to have a system and method for defining,. deploying, displaying, modifying, capturing, validating, and submitting/retuming form data on mobile device msing an intermittent network connection that addresses one or mare of these issues.
SUMMARY OF THE INVENTION
[.0007] A,ccordinD to one embodiment of the present invention, a system for capturing data via an extensible markup language form is disclosed. The system. comprises a policy-based mobile content engine, a mobile-forms application client, and a transport engine. The policy based mobile content engine is adapted to process a plurality of mobile-farms application definitions from one or more mobile-forms application definition files. The policy-based mobiae content engine is adapted to translate the plurality of mobile-forms application definitions into policies attd activ.ns. The policy-based mobile content engine is adapted to enforce the policies and actions that have been translated. The mobile-forms application client has a plurality of rendering engines targeted for one or more mobile user device. The rendering engines utilize a forms application definition markup language to render form controls and to process the forms-based application. The mobile-forms application client is operable on the one or more mobile user device and is adapted to capture the data bath online or offline as an extensible-markup-language document. The transport engine is adapted to transport the mobile-forms application definition files arid captured data through a transport layer between the policy-based mobile content engine and the mobile-forms application client.
(0008) According to another embodiment of the present invention, a method for defirzinb and erztorcing routing .rules to define a business process vvorkflovcr is disclosed. The method comprises the act of defining, via a mobile-forms application desi~er, a mobile-forms application-definition tile that defines a mobile forms application by providizzg, (i) a mobile forms application definition markup lanb age, (ii) an extensible-markup-language-based policy model that applies to one or rrzore data irzstartces that are to be captured, (iii) routing information specifyinb one or more targeted mobile user devices to deploy the mobile-forms applicatiorz-definition file ta, and (iv) a means of distribution of the forms-based application to targeted mobile users devices. The method further comprises the act of detcrmininb the routinb rules for the business process workf3ow by reading, via a business process engizze proxy, the mobile-forzxz.s application-definition file for the specified routing information and associated extensible-rxzarkup-[az~.guage-based policy model_ The method further comprises the act of enforcing, via a policy-based content management engine, the routing rules determined based on the defned and read mobile-forms application-definition file. The deploynent, form interaction, routing, and management of the mobile forms application is automatically supported by reading, deploying, and enforcing the mobile-forms application-definition file.
(0009) AccordinD to yet another embodiment of the present invention, a method for recognizing data superimposed on a paper fonm is disclosed. The method comprises the act of scam~ing a paper based form to create a paper-based form temptate_ '1"he method further comprises the act of capturing the location of a form data instance element overlaid on the papcr-based form template. The method further comprises the act of caph~ring, the si~,e of a form data insta~zce element overlaid on the paper-based fono template. T'he method further comprises the act of creating an input field based on the location and size of the form data instance element.
The method further comprises the act of linking the paper-based forfrt terrzp[ate to an application data madel_ The method further comprises the act of populating the paper-based form template with mobile-forms application data for a specific data instance in the input held.

[0010] The above summary of the present invention is not intended to represent each ezxxbodimexlt, or every aspect, of the present invention. Additional feattues and benefiits of the present invention are apparent from the detailed description, fiigurcs, and claims set forth below.
BRIFH DE$C.'RIPTION pFTHEARAWING$
[0011] FIG. 1 is an illustration of a content management system for mobile forms applications, according to one embodiment of the present invention.
[0012] FIG. z is an illustration of a mobile-forms based content management network, according to one embodiment of the present invention.
[0013] >; (G_ 3 illustrates a business process engine proxy integrated with a policy-based mobile contEnt engine, according to one embodirrzent_ (0014] F1G. 4 is an illustration of a process for creatizzg, traztsrnittirlg, and receiving data via a mobile forms application, accordinb to one embodiment of the present invention.
[0075] While the invention is susceptible to various modifications and alternative forms, specifc embodiments have been shown by way of example in the drawings and will be described in detail herein. It should be undemtood, however, that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, ecluivalcnts, and alternativES falling within the spirit and scope of the invention as defined by the appended claims.
DETAILED DESCR1P'1'ION OF THE ILLUSTRATED EMBODIMENTS
[0016] According to one embodiment of the present invention, the content managetx~ent system for mobile forms applications enables organizations to define axtd deploy mobile applications, forms, and business process workflow to mobile users across an enterprise or by using a Managed Service Provider (MSP) hosted environment. The content management system for mobile forms applications can be utilized without any programming language code being written or scripted since it is defined by policies, wizards, tezxlplates, and XML models. The content manabement system for mobile for.rrxs applications provides secure centralized control and support for hosting multiple security domains, whilE addressin ; all the complications of mobility (access outside the firewall, intermitte~ttly connected, wide variety of mobile devices and networks of 'varying capabilities, integration with existing business processes, IT
in~TaStructuTe, etc_~_ [0017a The content management system defines a mobile-forms-applications definition model and associated tools for: (1) defining XML-based applications, forms, and business process _;
workt3ow that are optimi?ed for mobility; (2) for interacting with XML data in a nrtobile forms application instance with model-driven, mobile-device-optimized fonns; (3) structuring and defining with model-driven policies-the process for delivering, storing, managing, notifying and routin; XML forms and associated form content (data, voice notes, photographs, sketches, GPS/location data, e~tezxial data inputs-e.g., bar-code scanners, etc.) to and frorx~: users and systems for mobile forms applications; (4) managing and monitoring with device-optimized interfaces-the status of XML mobile tbrms applications and all its instances, including support for on and off line use; and (5) document-based translation of XML to and from a wide variety of forms for importing, exporting, transforming, and publishing the data and coxatent associated with an instance of a XIvI~, ncxobile forms application.
[0018[ The content manabement system for mobile forms applications leverages several XML standards and will be compatible with emerging XML standards in the area of business process management. However, the content management system for mobile forms applications provides innovation beyond what is defined in XML and XFom~s standards by addressing uniduc challenges presented by wireless and mobility (users, devices, networks, cost of service, quality of service, etc.)_ The content rt~anagement system for mobile forms applications provides an automated, model-driven visual framework for the deployment and life-cycle management of mobile forms applications, and the processes associated with them (real-time and near-real time integration with strucWred and unstn2etured enterprise applications and content sources, confi'urable and dynamic notiFcations and alerts, routing of content, applications, and form data to and from mobile devices automatically or manually, etc.).
[0019] The policy-driven mobile forms applications have been desired and optimized for:
(I) deployrraent and operation within an Enterprise or a hosted MSP
environment for Enterprises (mufti-tenatat or mufti-domain); (2) support for multiple types of OS-enabled PCs and mobile devices (beyond a PC/Laptop, including but not limited to Smartphones, PDAs, Handhelds, Tablet PCs, bTandsets, Browscr-based devices, Portable and Embedded terminals, etc_); (3) use behind the enterprisE firewall (e.g. LAN, Wireless LAN, cradle) and while in the f eld (e.g., on/off line, asynchronous mobile wireless network connections, Wide-Area Wireless connection, etc..); (4) use by non-technical users within every "role" (form design, business process owner, ertd-user, administrators, etc.) and Sma41 and Medium Sized Enterprises (SME's) as opposed to technical-risers in enterprise 1T departments and Larbe Enterprise Deployments; and (5) use without requirinb extensive .IT components needing to already be in place (e.b., middleware, enterprise content management, document and records management systems, databases, web servers, etc.).
[0020] Turning now to the drawings, FIG. 1 illustrates a content managearient system for mobile forms applications I0, accordinb to one embodiment of the present invention. The content management system for mobile forms applications 10 includes eialat main components: a plurality of mobile-forms application definition files 14; a mobile-forms application client 18; a policy-based mobile content ermine (server) 22; a transpozt engine 2G; a mobile-application rrtanagement client 30; a mobile-forms application desi~er 34; a phirality of translators 38; and an adnunistration client 42_ [0021] The tt~obile-forms application definition files 14, according to onE
embodiment, are specified in XML-based forms application definition markup lanwage based on the W3C
XForms specification to define a rich presentation of forms rendered in a Graphical User Interface (GUI) by the mobile forms application thick or thin-Client. Same enhancements have been made to extend the XFomzs schema to make it more efficient far mobile forms applications, as well as to suppoirt layout of form controls on mobile devices, and inteb acing routing of forn~s between users iii a mobile forms application. An X.Mb,-based policy model is utili~..ed by tkie mobile-forms application definition f les 14 to define application and form states, workflow, validations, conditions, and actions to be processed for the life cycle of a new or updated foczxz data instance. The poli.ey model defines how the form data is manabed {e.g., transformation azid validation of data, publication of data to tarbeted resources, publication of data based on the type network connection, z~otxEcations and alerts to users based on forni actions and events, etc.) and distributed, as well as to whom (people, systems, resources, etc.) it is distributed.
[0022 As discussed above, the mobile extensible forms markup language (mXForms) used in the mobile-forms application-dctinition files 14 is based on the XForms W3C
recommendation (which can be found at http://www_w3.org/TR/2003/REC-xforms-20031014.
This mXForms markup language defines how to render rich GUIs online or offline far mobile devices, and display, update and captures data. mXForms and XFort~i~s distinctly define the presentation definition (look and feel), the format of the data captured, form controls, and the

7 behavior of the formsybased application (e.g_, data validation, navigation, workflow, actions, etc.). It is a language that can fully leverage the limited display and functionality (including native and extezraal peripherals-c.g., barcode scanner, GPS rxaodule, etc.) of some of the targeted mobile devices. Multiple views or mobile forms applications may be required to complete the data capture of a forms-based application, including support for contextual (e.b., dynamic) views or interaction with the foam (e.g., Y happens only if the user has selected X iz~.
the form). Unique form controls are also needed to display, add, edit, and delete repeating line items on such linuted devices. The cx~arkup language also affords for creation of 'unique form controls that Future business processes may require. These multiple views and Fonm contt~oIs can be used on- or off line, via thin/thiek elict~ts on mobile devices that are OS-enabled.
[0023] The mobile-forms application client 18 includes a plurality of rendering engines tazgeted for each Operating System (OS) enabled mobile device or browser enabled device that can be used as a thick and thin client. The rendering engines use the XML-based fortxxs application definition markup lan ;cage to render a rich set of GUI form controls and to process the correspondinD behavior of the forms-based application for the end-user_ The rendering enti nes are adapted to create a fully configurable Look and/or feel for the end-mer. Furthermore, the mobile-forms application client 18 is capable of displaying (read-only or read/write), updating, at~d capturinb the end-user's inputted data on- or off Iine as one or more XML
documents, as well as attachmeztt tiles and managed lists that may be in a forr~lat other than XML.
[0424] The mobile-forms application eliEnt 18 is also able to display, update, capture and attach a wide variety of mufti-media content to the form data. Alternatively or additionally, the rendering engines are adapted to encode this data to the :CIVIL form data instance as a base64 encoded element or reference the inputted text or binary hle as a separate entity_ The form data rraay include, For example, signatures, photos, voice notes, sketches, global positioning information, Goo~eMaps, bar code scanninD information, autornobile monitorinb infortrtation, etc.
[0025] For example, the mobile,forms application client 18 can call and contzol (interchan4e data) with an eztabled device's Global Positioninb System (GPS) coordinates to feed this information (as part of an XML fotTn data instance or data blob) to the policy-based mobile content engine 2z (or to a forms solution). This data may then be used to assist in device g manabement-adding business value by allowing a user to, for example, locate a lost device or assist in locating and dispatching a desired field worker to a specific job.
Additionally, GPS
coordinates may be dispatched along with a work order to allow a field worker to utiliLe a mapping tool (e.?., 'GoogIeMaps, MapPoint Location Server, etc.) to find the directions to the site for the work order. The mobile-fax~ns application client 18 can pass this data to .feed a xr~obile device application. For example, if the address of a dispatched work order is known, the mobile-forms application client 18 can pass this data to Microsoft pocketStreets and launch the application so the field worker can see the mapped address of their next work order. Aceordaz~g to one embodi;vent, the bar code seanninb information can be mapped to an input field within a form, or may be used to extract information .from an external data source (e.g., a managed list, ete.). For example, the bar code information may represent a part number that can then be searched through a part list to extract the part's name, description, price, ete.
[0026 ~'he content used by the mobile-forms application client 18 can either be embedded within the XML form data (basefi4 encoded) or be referenced and manabed as attachment files in a very elegant way as content under the control of policies that control how the content is managed and distributed (e.g., don't force sending of large multimedia f les associated with the form when the form is submitted wirelessly-unlike other database/sync or real-time forms solutions). The mobile-forms application client 18 can support a wide variety of technologies and input devices (e.g., Personal Digital Assistants (PDAs), smarrphones, etc_) for data captLUe and form navigation. The input devices are linked to anal interact with controls defined in the mobile exte~isible forms markup language to provide and enable data capture and form navigation.
(0027) By way of example, the mobile-forms application client 18, via the defined controls, are adapted to support a plurality of input devices, such as: keyboards (e.g., PC keyboard, keypad, Simple Input Panel (SIP), soft-keyboard, etc.); navigation, mouse, axxd T/O devices (e.g., optical mouse, RS-232 standard modules, touch-screens, scroll wheels, USB
rt~emory dongles, hard-drives, etc.); writinb instrlments and pointers (e.g., stylus, electronic pen/ink, handwriting to text conversion apps, etc.); audio (e.g., speech to text recognition, speech used the selection of an item from a list, speech used for form navigation using technology such as 'V12ML, voice recorders, ete.); infrared reader; magnetic reader and cards (e.g., swipe card, proximity card, smart card, expandable media cards and storage devices such as, for example, SD, MMC, compact hash, memory stick, etc.); Radio Frequency Identification (lt.hXD);
external or internal device peripheral (e.g., GPS, environmental meter, printers, etc.} including devices or data monitoring and reporting modules within an automobile (e.g., telematics);
external or internal applications (e.g., VoTP softphone software, GPS software, etc.); scanners (e_g., optical character reader. (OC12), bar code, hfornetrlc, etc.); incort>xng messages (e.g., via SMS, Smart Messages, OMA, SyncML, Eznail, SNMP, Active Sync, SMPP, SMTP, RSS/XML, etc.); and camera and digital imaging tools and devices__ [0028) The policy-based mobile cotttertt engine 22 includes a Business Process Ena°'ine Proxy (BPIwP) 22a that processes mobile forms application definitions from the mobile-foz~rns application defizzitiozt axles 14 and translates the application definitions into folder structures, files, and security roles as well as policies and actions that the poiicy~based mobile content engine 22 enforces. 'flaese poi icies and actions are utilized by the policy-based mobile content engine 22 to nuidc each instance of a mobile form through the business workflow process, including but not limited to, routing tire form to different users and sending out notifications as the data hElds of the mobile form are updated and actions axe taken. The BPEP
22a uses the policy model (application data model, process states, user groups, folder structure, workflow, actions, conditions, ete.) defined in the mobile-forms application definition filES 14. The policy model is extensible, flexible, visual, and may be wizard driven. As such, the policy model may be designed to be used and interacted with by .non-technical users. Note that a mobile forms application is created by the BPEP 22a into a single security domain_ The policy-based mobile content engine 22 explicitly represents the concept of multiple tenants (multiple domains) in its internal structures and partitions the content management, security roles, authorization, and policies associated with a mobile forms application by tenant (domain).
100z9j The transport engine 2<> i.s an integrated cliendservez transport engine that is adapted to reliably transport (e_g_, form data instance integrity and auditing of actions on the policy-driven mobile content engine 22 and mobile user device) the XML mobile application, forms data, and content through a contl ;ured transport layer (e.D., HTTP/HTTP(S), SynchML, AetiveSync, SOAP, FTP, SMTP, SMPP, RIvII, iIOP, etc.) betweezt the policy-based mobile content engine Z2 and the mobile-forms application client 18_ The transport engine 26 is optimised for mobility in regards to support for on- and off line use, support for multiple OS-cnabled mobile devices, support for various wireless and mobile networks with detection, consideration and maxxagezxtent for their various cost and quality of services, etc. Cozxxpzession, byte differencing, and network policies {e.g., do not send large attachments when low bandwidth connection) are used to provide intelligent use of bandwidth_ file caching, robust session management, partial file transmission support, and a robust synchronization protocol aver HTTP
are provided to address network unreliability.
[Ofl30] The policy-based mobile content engine 22 addresses the challenges (limited and unique physical auributes, cost of service, quality of service, etc.) associated with wireless and mobile devices and networks through the use o.f netwozk policies in conjunction with the transport engine 2G. The transport engine 26 determines whether data compression should be used to minimize data transmitted over the transport layer as well as a number of other technidues (use right network at the ribht time, compression, byte-level differencing, check-point restart, caching and queuing of requests, automatic and manual clientlseaver interactions, ete.) [0031] The mobile-application mana5ement client 30 is made available on each Operating System (OS) enabled mobile device or browser enabled device chat can be used as a thick and thin client__ The mobile-application management client 30 allows a manager or dispatcher to create, vivov, edit, assign, sort, search, or track the progress of Form data for atzy given mobile forms application_ The mobile.-application management client 30 allows such functionality based on the infornlation in the mobile-forms application-definition files 14.
The mobile-forms application-definition files 14 xrxap special "search fields" to information in a mobile form, including the current owner, the current state, as well as allowing custom defined fields_ '.)~he mobile-application management client 3U leverages the folder structure and policies generated by the BPEP 22a, to display to a person managing mobile .forms applications (e.g., dispatcher, office administrator, cte.) all the instances of a mobile form application, currently in prob ess.
Additionally, the manajer can see what state the mobile form is in, who it is assigned to, if the field worker has installed the ri;ht data on tlaeir device, etc. The mobile-application management client 30 incorporates the same rendering engine used by the mobile-form application client 18, so that a manager can select any fom~ instance to view or edit it or create a new one. The manager caz~ use this to change the stains of a form or assign it to a different person.
[003Z] The mobile-forms application designer 34 is adapted to create the mobile-forms application definitions contained within the mobile-forms application definition f lcs 14. In particular, the mobile-fotxns application designer 34 allows a non-technical designer (having minimal or no scripting, programming, or coding knowledge) to define an application in terms of: (i) the rtzobile .forms application definition markup language; (ii) the XML-based policy model that applies to the captured data; {iii) the targeted OS-enabled mobile device (e.g., PCs, TabletPCs, Laptop, PDA, Srnartphone, hlandheld, Handset, Browser-enabled mobile device, ecc.) or browser for the forms application definition; and {iv) the means of distribution of the forms-based application to targeted users (e.g., via push technology, SMTP, or available through a Uniform Resource Identifier (URI), etc.).
[0033[ The mobile-forms application designer 34 is a simple Integrated Development Environment (1D~) for ereatinb one or more mobile-forms application definition file 14.
According to one embodiment of the current invention, the mobile-forms application designer 34 is a standalone PC-based application, but can also be an add-in to an existing application (e.g.
Microsoft Visual Studio) or can be browser/web based. The data structure of the forms instance can be created by importing (e.g_, via an enterprise content source) XML
schema definitions or an instance of an XML file that is used as a demarcation point for back-end system integration.
This includes flexible handling of version control and change propagation and data migration when refneznents are made to the schema upon which a mobile forms application is based. The mobile-forms application designer 34 supports up~ades to a forms solution without diszziptinb the use of the forms solution by the field workers. Changes to the model shared between multiple participatzts arc carefully migrated to the ups ~aded Data Instances (DIs) on the policy-based mobile content engine 22 transparently to the users of the forms solution. Version control on the DIs is important to understanding the data mib atiozl that needs to occur --possibly on the tly~-~~-at the time it is created and/or updated on the sezver by a field tech during the transition period until every field worker has the upgraded application/model on their user device_ [0034 The look and feel of the forms application is defined by the mobile-forms application designer 34. The form designer can create form-based applications using a rich set of form controls that can be dragged and dropped or defzzted on a single or multiple form view. The mobile-firms application designer 34 enables the use of drag and drop properties and other means and controls to define the form flow or navigation of the application_ The form flow is howv the user of the application can use a forms control (e.g., buttoza, image, link, menu item, ete.) to modify forms. The Form flow is rxtostly defined by an action added to a button.
Conditional navigation can be controlled by the behavior typically defined by the "bind"

property of the control or the parent container of the control. The mobile-forms application designer 34 can associate actions to the form control to define the forxn flow.
[0035[ The mobile-forms application desi~cr 34 further defines a rich set of templates to speed the creations of or build forms (new or update fozms) based application for specific OS-enabled targeted devices. 'his includes a translation service that hElps with the automatic translation (grad optimization) from a form optimized for one device into other devices (e.g., browser, laptop, etc.), as opposed to the user having to stazt from scratch for each device. The mobile-fom~s application designer 34 deFnes several wizards to simplify the steps to create, modify, copy, publish, test, etc. a forms based application and includes a lest environment to process the authored mobile-forms application-definition files on the targeted device_ Additionally, the mobile-forms application designer 34 provides workflow and form data validation., i.n one embodiment, throubh the search values and the predefined policies for a tar;eted participant for the workflow and the behavior as defined in XForms for validation.
(0036] The paekaainb of the forms application is provided by the mobile-foixns application desibner 34 as a simple installable application to any OS-enabled mobile devices (e.g., Windows NT/2000/XP/Tablet, Pocket PC, Win CE, ete.) or via a web-browser. The distribution of the fom~s application to system and non-system users via a BPEP 22a integrated with the policy-based mobile content engine 22 through push technoloby, SMTP, or a URl where the application can be downloaded, or rendered on the server and interacted with in a browser session.
[003'7] The plurality of translators 38 are adapted to transla#e the mobile forrrxs application instance data and content into a variety of formats (XML/1-1TML, PDF, SQL, CSV, Printers, Faxes, etc.) for fuxther importind/exportirtD or for data manipulation, termination, or storage. A
technique for form-based data superimposition recognition allows an author to define and automatically correlate the absolute positioning of form data, text, or irr~;age to be printed o.n a paper-based or electronic form template or layout.
[0038] A special desi ;n tool and document translator has been designed as part of this invention to facilitate the creation of a mobile forms application from existing papez-based forms. In typical paper-based processes, mobile workers collect data in paper fornns that are faxed or printed. A mobile forms application also needs to use electronic data to print or fax a hard copy to the client on the same paper-based form. Existing print SDKs require absolute positioninb of objects (e.b., text, images) in order to position and size the captured form data sent it to a local printer to be printed on a template paper-based foz'xt~-(00391 The paper form data superimposition recognition is a special design tool and document translator that can scan existing paper-forms to create a document template and then link it to the application data model-through simple drab and drop or definition of data controls via the mobile-forms application designer 34. The mobile forms application data for a spee~e application instance can then be used to populate the template that is ready for printing or faxinb_ 'fhe paper .forr~a data superimposition recognition allows a designer to arttomatically build a forms application for a given forms solution using a scatarted version of an existing paper-based farm. The model and DI can autotxaatieally be generated using the paper-based form. In some embodiments, the paper form data superimposition recognition zequires the desi~tcr to: (1) review the form and c'hangc the input fields to other types of fonn controls (e.g., text box chanbed to a date picker or a sinnature control); (2) deFne groups of repeated line items; etc.
[0040] The administration client 42 is adapted to allow an end-user administrator to setup the rights provided to a specific user or device, the groups the user or device belongs to, the content available to the user or device, the domains the user or device is able to access, etc. The administration client 42 is particularly useful in embodiments where a number o.f company's content and forms are located on the same policy-based mobile content engine 22. The end-user administrator can theta use the administration client 42 to allow access to the company's content only to, for example, company erxtployees. The administration client 42 transmits access rights to the policy-based mobile content engine 22 that then can limit the access to the content based ora th;e user or device information of the user device trying to access the various content.
[0041 ( Typically, when a mobile fon~ application is developed utilizing the mobile-forms application designer 34, the user information, groups, and access rights are generated as well.
However, as the access rights change over time, tine end-user administrator can utilize tb.e administration client 42 to adjust the access rights, users, or groups accordingly. This allows the end-user's IT depatrtmcnt to manage their content and resources in a secure, desirable, and efficient manner.
(0042] One or more enterprise content sotuces 46 are in communication with the policy-based mobile content engine 22. The one or more enterprise content sources 46 may also communicate with the rt~obile-forms application designer 34 or the mobile-farms application client 18. 'The one or more enterprise content sources 46 are integrated directly with the policy-based ~xzobile content engine 22, the mobile-forms applicatiozz designer 34, and the mobile-forms application client 18 via a plurality of connectors.
[0043] 'fhe policy-based mobile content engine 22 can access the content and information stored on the one or more entezprise content sources 46 and transmit it to the various user devicES based on the policies def7zaed by the mobile-forms application-definition files 14. The mobile-forms application client 18 can utilize the one or more enterprise content sources 46 for pushing or receiving forms as XIvIL files. Additionally, ttze mobile-forms application designer 34 can utilize the content contained with the one or more entezprise content sources 4G as a starting paint for designin? the nrzobile-forms application definition files 14.
[0044] Referring also to FIG_ 2, a mobile-forms based content management network GO is illustrated, according to one embodiment of the presexzt invention. The content rz~.anaacment network 60 allows the communication of the mobil~forms application client 18 with the policy-based mobile content engine 22 to transpozrt the mobile-fom~s application-definition ~fles 14 and all form data instances to and from a mobile device G4. The mobile-forrras application client I $
is primarily eoz'n.prised of a forms rendering enbine that can present a user interface G8 as defined by in the mobile-forms application-definition files 14. The mobile-fours application-definition tiles 14 describe the user interface{s) G8 using the mobile extensible forms markup lan;uage that the forxxzs rendering engines) intezprcts when displayin5 the user interface 6$_ [0045] The mobile-forms application client I$ is available on a wide variEty of OS-enabled mobile devices both as a native application 72 ("Thick Client") and as browser-enabled application 76 ("Thin Client"). It should be noted that even the browser-enabled applications are optimized to address the constraints of the devices they are operating on_ T7~e mobile-forms application client 18 communicates with the policy-based mobile content enbine 22 via a client Application Progt'amming Interface (AFI) to transport the mobile-forms application-definition files 1.4 and all form data instances 80 (associated XML data and eorztent) to and from the mobile device.
[0046] As illustrated in FIG. 2, the policy-based mobile content engine 22, via the transpozrt engine 26, delivers and receives the form data instances that are viewed and updated in the mobile-.forms application client 18 (via the forms rendering engine) on a variety of devices 64, 72. Botla "flick-client" 72 and "thin-client" 76 versions of the mobile-forms application client 18 leverage the transport engine 26 tv communicate with the policy-based mobile content server 22 over intenziittently connected networks 84 (sometimes onli.u,e, sotxtetimes of~ine). The connnurwication coTasists mainly of delivering an instance of mobile form data, as well as mabile-fonns application~definition tiles 14 to the mobile-forms application client 18 that determine how the mobile form data should be presented to the user. When the user updates the mobile form data instances 8U, using the mobile-forms application client 18, they are communicated back to the policy-based mobile content engine 22 via the transport engine 26.
,A,ny changes to any instances are first persisted to a file prior to transporting them to the policy-base mobile content engine 22. This is done to ensure the user can safely keep workizzg even if they are currently disconnected, to keep historical data on the device (if specified in the mobilE forms application definition), and to provide a backup capability in case of device failure including but not lizrited to power failure such as no more battery power left.
[0047] Referring also to FTG_ 3, the integration of the BPEP 22a with the policy-based mobile content engine 22 is further illustmtEd, according to one embodiment-A, business process workflow is defined in one or more mobile-forms application-definition files 14 that are processed in the policy-based mobile content engine 22 via the BPEP 22a, according to one embodiment. The BP1;P 22a is a component of the policy-based mobile content engine 22 that processes mobile forms applications and forms definitions. The mobile-forms application-defnition files 14 used by the BPEP 22a can be defined by th.e non-technical form author using the mobile-forms application designer 34. When utilizing the mobile-forms application designer 34 the form author defines the states, workflow, and composition of the fortxi data instance, the conditions that define.the next state to process (e.g., if the technician requires t.~ew parts then bo to state 'X'), axzd the actions to be processed on a given state in the form's data instance life cycle.
[0048] 1~or exazxtplc, the followinb sample actions are supported by the mobile-forms application designer 34 and are capable of being interpreted by the BPEP 22a and enforced by the policy-based mobile content engine 22. eoz~tcnt publication (e.g., add/move/eopy/dElete docum.exxt or form data) to an existing/new network folder or other services (This action takes into accouztt the user's access pern~issions to the document or form data on the tar;eted destination prior to publishing the content.); content auditing (auditing of user, device, and content it~forrraation updated via the policy-based mobile content engine 22);
eor~tez~t distribution via email, fax, SMS, print and content push via the policy-based mobile content engine 22;
content notification via email, fax, SMS, SNMP, SMPP, print, and/or other external web services; content teansfotmation that may contain any other previously deF~ned actions (lt is possible to transform the data prior to distributing it via email (e.g., make it a viewable HTML
document)); content validation (Some targeted devices might not support local validation against an XML schema. Therefore, the validation can be deed as an action and cause the document to be rerouted 'to the sender.); and network management (This action can require the sender to publish associated attachments to the data instance on a speci f c network type (e.g., EDGE/GPRS, UMTS, CI~MA I x, W-CDMA, WiFi, 802.13 aib/g, Bluetooth, LAN, cradle, etc.).).
f 0049] Aeeorditta to one embodiment, the communication protocol of the content management system 1(3 utilizes HTTP(S) as the preferred protocol to transport all farm data instance and attachments to the Policy-based Mobile Conteztt )vn~ne. The content management system 10 may utilize, as the preferred protocol to distribute and notify other internal or external resources (e.g., users, other machines, ere.), HTTP/HT'TPS, SyncML, ActiveSyne, SOAP, SMTP, FTP, SMS, SNMP, SMPP, RMI, IIOP, etc. Other communication protocols can be utilized without nullifying th;e key attributes of the above-described implementation. For example, web extensions such as SOAP and .NET can also be utilized, as well as proprietary corxizxtunication protocols. The policy-based mobile content engine 22 may also act as an authorizing proxy 'for each of these protocols that allows the mobile-fozms application client 18 to communicate in real time with one or more enterprise content sources 46 hosted behind the enterprise tircwall. For example, a drop down list in a mobile form could be dynamically generated by a SOAP request to an etaterprise content source 46- 'The policy-based mobile content engine 22 would apply appropriate policies both before and after routing the SOAP
request ti'om the mobile-forms application client 18 onto the enterprise content source 46_ [0050] The coxttezzt management system 10 may utilize Secure Socket Layer (SSL) to encrypt all communication between the clients, othez internal and external resources, and the policy based mobile content engine 22_ Other encryption techniques can be utilized without nullifying the key attributes of the invention_ For example, a VPN tunnel could be used to secure the conra~ction between the mobile-forzos application client 18 and the policy-based mobile content eta.ginc 22. Similarly, an s-mitx3,e technique could also be adopted where the target application is e-mail. Furthermore, the forms designer can specify that the data captured as an XML document on the mobile device may be encrypted using a public or secret-key eryptosystem {e.b., Kerberos, PKI, etc.) to properly secure the content on the tmobilc device if the device was stolEn or lost, or if the policy-based mobile content engine 22 was campraxniscd.
[0051 J The content management system 10 enables existing authentication such as existing hUAP and RADIUS servers (local or remote, outside or behind the firewall with support for "single sign on" schemas) among others, to be used 6y the policy-based mobile content ez~gi.ne 22 to authenticate users of tlZe mobile-forms application client 18, the mobile-application management client 30, and the administration client 42. The policy based mobile content engine 22 can either automatically detect the required authentication or the policy-based mobile content engizte 22 can be told by a system administrator to do so. Authorization providers are used to determine it the client is authorized based on their access permissions deternrzined, but not limited to, the client's role and/or roup access permission on the accessed resource (e.g. updating or creating a forms data instance), [005zJ The mobile-forms application desibner 34 provides the end-user with custom-built fo.rzxt applications available on a thick ox thin client. It also enables the forms designer to define all aspects of floe mobile-forms application-defnition files 14, target mobile devices, associate a test environment where the mobile-forms application-definition files 14 can be tested, associate business workflow, Foz~xt navigation, behavior, data capture and define how the mobile forms applications can be procured and haw they can be distributed, updated, or revoked from privileged users.
(0053) The content management system 10 provides superior end user, network, and client performance in several different ways. First, data coxnpression may be used both in downloadiztg newly dispatched and uploading updated form data instances. Furthermore, the policy-based mobile content engine 22 determines when file attachments associated with the mobile form application data instance should bE delivered using both the type of network and attachment size.
Additionally, the content managEment system 10 supports external model updates (e.g., customer list, price Iist, inventory list, ete.). These types of lists typically consist of a large amount of data that should only be updated at wen times or when netwozk availability permits.
Fox mare time critical updates to the list, byte level differencing and data compressiolt can be used to update the end-users list with the changes rather than the updated list. This can reduce the network data Ig constunption by over 80"~0 dependin ; on the changes made to the list_ Byte level differencing is done by transmitting only the changes between the old list and the new list (byte Level differences) and by applying those changes as an update to the old list on the mobile device to create tl~e new list on the mobile device. It can also be used to update an attacltment to a form data instance.
[0054] 'fhe content management system 10 provides superior availability to mobile workers by enabling offline form fillinj when cantined to areas with restricted network connectivity and by enabling ortline, near real time, updates of form data to the server.
Furthez, the content manabement system 10 helps to ensure that forms application and associated resources (e.g., external lists) are pushed as mandatory items. The content management system 10 controls delivery of captured data instances aa3d foi~ns application on a device based on, but not limited to, network connectivity, tithe, etc_ Near real time or scheduled updates to a mobile-forms application-definition file is enabled by, for example, using byte level differencing and data coznprcssion to reduce the size of tlxe markup transported to the mobile device. The content management system 10 further enables automatic calculations, comparisons, enforced fields, data input limitations, mandatory fields, contextual form behavior, read-only and pre-filling of form data, thus assisting in speeding up data capture and business process completion.
[0055] As discussLd above, the content management system for mobile forms applications 10 utilizes the mobile forms application markup language. The mobile forms application markup land abe can be utili?ed to define a number of enhanced fornZ controls_ For example, the mobile forms application markup lanb gage can defne controls for: viewing the defnition of a mobile-forms application-definition file 14 to better group controls and maximize display area of nnobile devices with limited viewing area; providing new appearances for repeat line item cozatrols;
providing controls to view attachments; providing attributes to determine how an attachment is attached to the data instance (e.g_, as a base 64 encoded, binary, ox as a URI); providing support to display images; providing support to display links allowing form-view navigation or web page launch; providing a trigger with a background image; providing a toolbar with menu items used as a trigger yr a submit XForrns eletxtent; providing a header definition that allows the grouping of repeated controls used on di Fferent views; providing a footer definition that allows the gouping of repeated controls used on different views; and providing toolbar, header', and footer references used in a form-view definition to maximize limited resources on given devices (e.g., PPC). These controls can also be bound to dynamic real-time requests that are routed to enterprise content sources 46, via the policy-based mobile content engine 22.
[OOSG] Twwing now to FTGr. 4, a process for creating a mobile forms application, traz~sznitting floe mobile fortes application, and receiving data via the mobile forms application is illustrated, according to one embodiment of the present invention. By utilizinb the mobile-forms application designer 34 (FIG. t), a non-technical user can define a mobile-forms application-definition file 14 (FXG. 1 ) at step I I U. The mobile-forms application-def nition file 14 defines tlxe data model, form navi ;anon, form validation, behavior, look and feel for the form application, and the various processing states that a fornn. document will transition through. A
mobile policy is also defizted wb.ich specifies the roles and policies about routing, distribution, notif canon / alerts, devices, authorization, etc. All of these are created using a wizard-based, point-and-click interface, which requires no coding, seriptinb or programming on the part of the designer. There are also special tools for defining form based user interfaces that end-users can used to interact with application data, as well as spECial tools for defining format translations to import and export application data from XML into other formats (HTML, plaF, SQL, CSV, ASCII, etc.) including sending to a printer or fax_ And there is a tool for importing, exporting, creating and editing XML sche~nas that define the structurE of the data supported by the mobile-forms application-definition client 18. The mobile-fogs application-definition file 14 is them stored to a hard disk.
(0057( The application data model, process states, folder structure, user groups, mobile policies, format translations, and user interfaces are all defined in XML-based mobile-forms application-definition files 14 that axe Generated onto the policy-based mobile content engine 22 at step 12U~ Th.e policy-based mobile content engine 22 serves as a gateway between mobile forms applications and existing business processes, enterprise content sources, and applications.
[0058] The policy-based mobile content engine 22 automatically or manually can be used to create and set up folder structures at step 120a and to create user groups at step l2Ub_ At stEp 120c, the mobile-forms application-definition file 14 its actually transferred to the policy-based mobile content engine 22. Infbrmation contained ixA the mobile-forms application-definition frle I4 is used to define a folder structure in the policy-based mobile content engine 22, which will store the content associated with each application, and to define the user groups in the poliey-z0 based mobile content engine 22, that will be allowed to access application data and content during the various processing states of an. application instance.
[0059] The policy-based mobile content engine 22 generates a plurality of searcla and trackin5 fields at step 120d that allow a forms nrtartager to look for and monitor the mobile foams applications that have been provided (and deployed) by the policy-based content management engine 22. At step 120e, the policy-based content trxanaaemEnt engine 22 generates client installation packages for. installinD the mobile form application onto the user devices. Routing and deployment policies are determined at step 120f by the policy-based content management engine 22 for the mobile form application based on the mobile-forms application-definition fIe 14. The policy-based content management engine 22 then generates a user's extensible-markup-langua~e file at step 1200.
[0060] The mobile forrms application created by the mobile-forms application designer 34, is deployed to the user devices at step 130 by die policy-based mobile content engine 22 (F1G. 1 ) and its associated transport enbine 26 (FIG. 1)_ The deployment activates the mobile forms application such that the application and associated files, user lists, etc.
will be pushed down to the user's mobile devices 64 (FIG. 2). Alternatively, the deploymexxt tnay be accomplished by generating a media card (e.g., a SD card, mini-SD, etc.) along with user configuration files. The media card may then be utilized to automatically and intelligently install the mobile forms application and configuration files onto an OS-enabled user device. The deployment process manages both forms application upgrades as well as data zr~i~-ation that may be required for existing form instances persistent on the policy-based mobile content engine 22 and mobile devices_ [0061] The mobile-fornas application client 18 (FIG. 1) is available on a wide variety of user devices (PC, Laptop, Tablet, PDA, Blackberry, Smartphone, Browser-based thin-client, etc.) that allows end-users to interact with application data and content. The wobile-application management client 30 (FIG_ 1 ) is also available which allows managers to create, assign, and monitor application instances. Document translators 3$ (FIG. 1) are used to view and print application data content, as well as transform it for use by other systerrzs_ [0062] The policies of the mobile contextt engine are applied in response to any content management event (including, but not limited to reconcile requests from clients, new or updated files, ales assi~ed to users, etc.). Policies are able to leverage whatever information is available to the content management engine tizxze in deciding what actions should occur (type of network, content or state of the files being transferred, users involved etc.). In particular, when a relevant state change is detected by the mobile application client 18 on a znobilE
device 64 (FIG. 2), the policy-based mobile content engine 22 is notified, and the policies for the particular mobile-forms application-defitzit.ion ale 14 are enforced at step 140_ The state change may be, fox example, the creation or modification of a form data instance $0 (FIG. 2) on the mobile device 64. The mobile-application z~anabement client 30 can be utilised at step 150 to create new Form data instances and assign them to users (both actions will result in content management events that txi~er the appropriate policies for the mobile forms application).
Further, at step 150, the mobile-application management client 30 cazz be utilized to track the status of all data instances (e.b., what state they are in, w.ho they are assigned to) using the search and tracking fields generated at step ] 20d.
[0063] Based on. the policies relevant to the state change, the new or rnodired data instance can be transferred between the policy-based mobile content engine 22 and the user devices at step 160. This information can further be transferred between. the policy-based mobile content en;ine 22 and tl~e other user devices within the particular user group_ The user or other users are then capable of interacting with the application data arzd content at step 170 once that information has been pushed to their user device by the policy-based mobile content engine 22.
[0064] This scenario is much more effective compared to other solutions that use data replication to synchronize databases on mobile devices with a central server database_ First, such databases quickly become too big in practice given the limited capabilities of mobile devices.
Second, a lot of. unnecessary information is moved back and forth. Policy-driven mobile forms applications are designed to minimi?e the exchange of data wirelessly (use right network at the right time, compression, byte-level differencin ;, check-point restart, caching and queuing of requests, autoxnatie and manual client/server interactions, ete.)_ [OU65] While the present invention has been described with reference to one or more particular embodiments, those skilled in the art will recognise that many changes may be zxzade thereto without departing from the spirit and scope of th.e present invention.
Each of these embodiments and obvious variations thereof is contemplated as falling within the scope of the claimed invention, which is set forth in the following claims.

Claims

WHAT IS CLAIMED IS:

1. A system for capturing data via an extensible markup language form, comprising.
a policy-based mobile content engine adapted to process a plurality of mobile-forms application definitions from one or more mobile-forms application definition files, the policy-based mobile content engine being adapted to translate the plurality of mobile forms application definitions into policies and actions, the policy-based mobile content engine being adapted to enforce the policies and actions that have been translated;
a mobile-forms application client having a plurality of rendering engines targeted for one or more mobile user device, the rendering engines utilizing a forms application definition markup language to render form controls and to process the forms-based application, the mobile-forms application client being operable on the one or more mobile user device and being adapted to capture the data, as one or more form data instances, both online or offline as an extensible-markup-language document;
and a transport engine adapted to transport mobile-forms applications, definition files, and the captured data through a transport layer between the policy-based mobile content engine and the mobile-forms application client.

2. The system of claim 1, wherein the mobile-forms application client is further adapted to capture and attach a wide variety of multi-media content to the captured data.

3. The system of claim 1, wherein the plurality of rendering engines of the mobile-forms application client is adapted to encode the captured data as an extensible-markup-language form data instance.

4. The system of claim 1, wherein the plurality of rendering engines of the mobile-forms application client is adapted to reference the inputted data to an opaque object.

5. The system of claim 1, wherein the management and distribution of the captured data is controlled by one or more policy translated from the plurality of mobile-forms application definitions.

6. The system of claim 1, wherein the rendered form controls are linked to and interact with one or more input devices provided on the mobile user device, the one or more input devices allowing for data capture and assisting with navigation of the forms-based application.

7. The system, of claim 1, wherein the policy-based mobile content engine routes the one or more mobile-forms application-definition files to the mobile-forms application client via the transport engine.

8. The system of claim 1, wherein the policy-based mobile content engine sends notifications as one or more data field within the mobile-forms application definition files is updated.

9. The system of claim 1, wherein the policy-based mobile content engine supports multiple security domains in a hosted environment that enables mobile forms applications, folder structures, user groups, user authentication, policies, and form data instances to be partitioned and kept wholly separate by security domain.

10. The system of claim 1, wherein the transport engine utilizes data compression to transmit the mobile-forms application definition files and the captured data through the transport layer between the policy-based mobile content engine and the mobile-forms application client.

11. The system of claim 1, wherein the transport engine utilizes byte-level differencing when retransmitting or updating large files that are part of the mobile-forms application through the transport layer between the policy-based mobile content engine and the mobile-forms application client.

12. The system of claim 1, wherein the transport engine utilizes check-point restarting when transmit the mobile-forms application definition files and the captured data through the transport layer between the policy-based mobile content engine and the mobile-forms application client.

13. The system of claim 1, wherein the transport engine uses caching and queuing of requests for transmitting the mobile-forms application definition files and the captured data through the transport layer between the policy-based mobile content engine and the mobile-forms application client.

14. The system of claim 1, wherein the transport engine is able to support communication between the mobile-forms application client and the policy-based mobile content engine both inside and outside of a corporate firewall.

15. The system of claim 1, wherein the transport engine is able to maintain a secure and robust user session between the mobile-forms application client and the policy-based mobile content engine over an intermittently connected network, via file caching, partial file transmission support, and a robust synchronization protocol.

16. The system of claim 1, wherein the rendered form controls are linked to and interact with one or more enterprise content sources in real-time, a request to the one or more enterprise content sources being communicated either directly or via the policy-based mobile content engine.

17. A method for defining and enforcing routing rules to define a business process workflow, comprising:
defining, via a mobile-forms application designer, a mobile-forms application-definition file that defines a mobile forms application by providing, (i) a mobile forms application definition markup language, (ii) an extensible-markup-language-based policy model that applies to one or more data instances that are to be captured, (iii) routing information specifying one or more targeted mobile user devices to deploy the mobile-forms application-definition file to, and (iv) a means of distribution of the forms-based application to targeted mobile users devices;
determining the routing rules for the business process workflow by reading, via a business process engine proxy, the mobile-forms application-definition file for the specified routing information and associated extensible-markup-language-based policy model; and enforcing, via a policy-based content management engine, the routing rules determined based on the defined and read mobile-forms application-definition file, wherein the deployment, form interaction, routing, and management of the mobile forms application is automatically supported by reading, deploying, and enforcing the mobile-forms application-definition file.

18. The method of claim 17, wherein the extensible-markup-language-based policy model specifies a business process workflow including, (i) definition of state attributes in terms of information contained in a mobile-forms application instance or information available at run time in the policy-based mobile content engine, (ii) events triggered by a change to a state of the mobile fortes application or requests to the policy-based mobile content engine, (iii) conditional evaluation and responses to events, and (iv) actions that can be processed either directly or via the policy-based mobile content engine, the actions including changing the state of the mobile-forms application client.

19. The method of claim 17 further comprising, allowing a manager to track the progress of a work request relative to the business process workflow by utilizing a mobile application manager client, the business process engine proxy, and the policy-based content management engine.

20. The method of claim 17 further comprising, sending dynamic alerts and notifications associated with a tracked business process workflow arid other events.

21. The method of claim 17, wherein the mobile forms application designer is adapted to modify the mobile-forms application-definition file.

22. The method of claim 17, wherein the mobile forms application designer is adapted to modify the extensible-markup-language-based policy model.

23. The method of claim 17, wherein the mobile forms application designer is adapted to test and package a mobile-forms application-definition file and the mobile-forms application-definition file's dependencies.

24. The method of claim 17, wherein the routing information specifying one or more targeted mobile user devices specifies one or more groups of users.

25. The method of claim 17, wherein the nobble-forms application-definition file is a self-extractable packaged file.

26. The method of claim 17 further comprising, updating the mobile-forms application-definition file and providing the updated mobile-forms application-definition file to the mobile user device, via the policy-based content management engine and an associated transport engine.

27. The method of claim 26, wherein the updated mobile-forms application-definition file is provided to the mobile user device utilizing wireless network connectivity.

28. The method of claim 26, wherein a form instance data definition modification can trigger data migration of existing form data instances persistent on the policy-based content management engine and the mobile user devices to validate against a new forms instance data definition via the business process workflow.

29. The method of claim 17 further comprising, mapping, via one or more translator, the mobile forms application from the extensible forms language into a format preferred by a user.

30. The method of claim 17 further comprising, mapping, via one or more translator, the mobile forms application from the extensible forms language into a format appropriate for the mobile user device the mobile forms application is deployed on.

3I. A method for recognizing data superimposed on a paper form comprising.
scanning a paper based form to create a paper-based form template;
capturing the location of a form data instance element overlaid on the paper-based form template;
capturing the size of a form data instance element overlaid on the paper-based form template;
creating an input field based on the location and size of the form data instance element;
linking the paper-based form, template to an application data model; and populating the paper-based form template with mobile-forms application data for a specific data instance in the input field.

32. The method of claim 31, wherein the input field.

33. The method of claim 32, wherein the form controlled field is a date picker.

34. The method of claim 32, wherein the form controlled field is a signature control.