Electronic form generator

• US 20060136810A1
• Filed: 02/09/2005
• Published: 06/22/2006
• Est. Priority Date: 12/22/2004
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Truong, Andre, Chen, Shuyuan, Mendicino, Vincent
• Application Number:
  US11/052,851
• Publication Number:
  US 20060136810A1
• Time in Patent Office: Days
• US Class Current: 715/222
• CPC Class Codes: G06F 40/174 Form filling; Merging

Abstract

An automated form generation service within a computer system dynamically creates form templates from a plurality of template documents. For each root node present in a first template document, the service determines whether a matching node is present in a second template and, if so, it merges node structure from corresponding locations within the first and second templates. The form generation service further renders the final electronic form based on available form formats and populates the form with dynamic content. The form generation service is a run-time service that may be called by another requesting application.

Claims

1. A form generation method, comprising:

responsive to a call identifying a master form template and a dynamic form template, comparing identifiers of root nodes within the dynamic form template to data items within the master form template,

when a match occurs, merging the root node with sub-ordinate data structures from the dynamic form template to a position within the master form template where the match occurred, and

storing a resultant structure as a completed form template.

2. The form generation method of claim 1, further comprising generating a rendered form from the completed form template and a dynamic content data item, wherein the rendered form includes data from the dynamic content data item at form positions in the completed form template according to metadata identifiers included in each.

3. The form generation method of claim 0, further comprising rendering the rendered form in a file format specified in the call.

4. The form generation method of claim 0, further comprising rendering the rendered form in a default file format unless another file format is specified in the call.

5. The form generation method of claim 0, further wherein the completed form template is stored in persistent storage dedicated for use by a form generator service.

6. A form generation method, comprising:

responsive to a call identifying a master form template, a dynamic form template, multiple instances of dynamic content data and a file format, comparing identifiers of root nodes within the dynamic form template to data items within the master form template,

when a match occurs, creating a completed form template by merging the root node with data structures from the dynamic form template to a position within the master form template where the match occurred,

generating multiple instances of rendered forms from the completed form template and respective instances of the dynamic content data, wherein the rendered form includes data from the dynamic content data item at form positions in the completed form template according to metadata identifiers included in each, and

rendering the rendered form in a file format specified in the call.

7. The form generation method of claim 6, further comprising storing the completed form template in storage allocated for performance of the method.

8. The form generation method of claim 7, wherein the generating includes, for each instance of rendered form, retrieving the completed form template from storage.

9. A form generator service, comprising:

an inbound adapter, responsive to service calls from requesters that identify a master template, a dynamic template and dynamic form content data,

a merger unit that generates a completed form template from a merger of master template data and dynamic template data, and

an outbound adapter that generates a rendered form from the completed form template and the dynamic form content data in a selected file format.

10. The form generator service of claim 9, wherein the selected file format is specified in the service call.

11. The form generator service of claim 9, wherein the selected file format is a default file format unless specified in the service call.

12. The form generator service of claim 9, further comprising persistent storage dedicated for storage of the master template and the dynamic template data.

13. The form generator service of claim 9, further comprising persistent storage dedicated for storage of the dynamic content data.

14. The form generator service of claim 9, wherein the service call includes pointers to the master template data and the dynamic template data in the requestor'"'"'s file system.

15. The form generator service of claim 9, wherein the merger unit:

compare identifiers of root nodes within the dynamic form template to data items within the master form template, and

when a match occurs, creates a completed form template by merging the root node with sub-ordinate data structures from the dynamic form template to a position within the master form template where the match occurred.

16. A computer readable medium storing program instructions that, when executed, invoke an instance of a form generator that:

in response to a call identifies a master form template and a dynamic form template, compare identifiers of root nodes within the dynamic form template to data items within the master form template,

when a match occurs, merges the root node and sub-ordinate data structures from the dynamic form template where the match occurred, and

stores resultant structure as a completed form template.

17. The medium of claim 16, wherein the instructions further cause the form generator to generate a rendered form from the completed form template and a dynamic content data item, wherein the rendered form includes data from the dynamic content data item at form positions in the completed form template according to metadata identifiers included in each.

18. The medium of claim 17, wherein the instructions further cause the form generator to generate the rendered form in a file format specified in the call.

19. The medium of claim 17, wherein the instructions further cause the form generator to generate the rendered form in a default file format unless another file format is specified in the call.

20. The medium of claim 17, wherein the instructions further cause the form generator to store the completed form template in persistent storage dedicated for use by the form generator.