Forms conversion and deployment system for mobile devices

• US 10,664,651 B2
• Filed: 01/09/2017
• Issued: 05/26/2020
• Est. Priority Date: 03/01/2007
• Status: Active Grant

• Current Assignee: Formrc, Inc.
• Original Assignee: Romrc Incorporated
• Inventors: Neagu, Adriana, Divringi, Lale, Dinu, Bogdan Valentin, Jeaca, Dafina-Maria, Matei, Adrian
• Primary Examiner(s): Zhen, Wei Y
• Assistant Examiner(s): Bourzik, Brahim
• Application Number:
  US15/402,082
• Publication Number:
  US 20180024979A1
• Time in Patent Office: 1,233 Days
• Field of Search: 717106
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A method and system for automatically converting forms generated using a desktop forms development tool to be compatible with mobile devices, for deploying the converted forms to the mobile devices, and for running converted forms on the mobile devices is provided. A forms system provides a conversion component, a deployment component, and a device component. A forms file is generated to be processed by a forms display program on a variety of devices. The forms system transforms the forms file to a target form file designed for execution by a target forms display program on a device of the target device type.

Claims

1. One or more computing systems for generating a target form definition file designed for execution by a target forms display program on a device of the target device type, the one or more computing systems comprising:

one or more non-transitory computer-readable storage mediums storing computer-executable instructions for controlling the one or more computing systems to;

provide a generic form definition file generated by a desktop form development tool for execution by the target forms display program on a variety of devices, the generic form definition file including a view file and other forms data, the view file for being applied to data to generate a view of the data and tailored to characteristics of the device of the target device type; and

for each of a plurality of different target forms display programs;

apply a transform to the view file to create a transformed view file that is compatible with that target forms display program by converting elements of the view file that are not supported by that target forms display program to elements supported by that target forms display program, such that whenever a field is changed, controls affected by the change are incrementally updated;

add menu items and items of a drop-down list directly to the transformed view file to avoid overhead of locating and retrieving those items by the device of the target device type;

generate an information file that records information extracted from the other forms data, the information file including mappings of controls to data, web services information, rules information, and custom validation information, the information file being a single repository for storing the extracted information in a format that is different from a format output by the desktop form development tool and allows the device of the target device type to retrieve and process the extracted information more efficiently at runtime; and

package the transformed view file with the information file into a forms package for distribution to a device of the target device type that executes that target forms display program, the forms package not including information not extracted from the other forms data; and

one or more processors for executing the computer-executable instructions stored in the one or more non-transitory computer-readable storage mediums.

2. The one or more computing systems of claim 1 wherein the transform applied to the view file transforms body elements and textbox elements.

3. The one or more computing systems of claim 1 wherein the transform applied to the view file adds elements within control elements for highlighting the control upon occurrence of an error.

4. The one or more computing systems of claim 1 wherein the transform applied to the view file adds an identifier and name attribute to controls to identify the data of the controls.

5. The one or more computing systems of claim 1 wherein the transform applied to the view file ensures that whenever data of the form is modified, the modified data is persistently stored in the device.

6. The one or more computing systems of claim 1 wherein the packaging includes packaging a launch executable for distribution, the launch executable for launching a runtime component to process a form defined by the forms package.

7. A method performed by one or more computing systems for converting a form definition file designed for execution by a forms display program on a variety of devices to a target form definition file designed for execution by a target forms display program on a device of the target device type, comprising:

providing the form definition file generated by a desktop form development tool for execution by the forms display program on a variety of devices, the form definition file including a manifest file, a schema file, and a view file, the view file for being applied to data to generate a view of the data and tailored to characteristics of the device of the target device type;

applying a transform to the view file to create a transformed view file that is compatible with the target forms display program, wherein the transform transforms elements of the view file that are not supported by the target forms display program to elements supported by the target forms display program, such that whenever a field is changed, controls affected by the change are incrementally updated;

adding menu items and items of a drop-down list directly to the transformed view file to avoid overhead of locating and retrieving those items by the device of the target device type;

generating an information file that records information extracted from the manifest file and the schema file, the information file including mappings of controls to data, web services information, rules information, and custom validation information, the information the being a single repository for storing the extracted information in a format that is different from a format output by the desktop form development tool and allows the device of the target device type to retrieve and process the extracted information more efficiently at runtime; and

packaging the transformed view file, the schema file, and the information file into a forms package for distribution to a device of the target device type that executes the target forms display program, the forms package not including the manifest file.

8. The method of claim 7 wherein the transform applied to the view file transforms body elements and textbox elements, adds elements within control elements for highlighting the controls upon occurrence of an error, and adds an identifier and name attribute to controls to identify the data of the controls.

9. The method of claim 7 wherein the transform adds onchange attributes to controls for handling custom validation and rules.

10. The method of claim 7 wherein the provided forms definition file is compatible with InfoPath.

11. The method of claim 7 wherein the target forms display program includes a web browser of the device of the target device type.

12. The method of claim 7 wherein the target device type is selected from the group consisting of a personal digital assistant and a cell phone.