Abstract:
A method of document generation includes, in response to a call from an application, getting an interface and interface description of a template used to create a document, determining whether a method exists for filling all elements of the interface, making a dynamic call to invoke the method for filling all elements of the interface if the method exists, decomposing the interface into further elements if a method does not exist for filling all elements of the interface, repeating the steps of determining whether a method exists, making a dynamic call and decomposing the interface, until all elements of the interface are accounted for.

Description:
BACKGROUND OF THE DISCLOSURE  
       [0001]     1. Field of the Disclosure  
         [0002]     The present disclosure relates generally to document generation and in particular, to systems and methods for extensible document generation.  
         [0003]     2. Description of the Related Art  
         [0004]     Computer software such as computer applications often provide feedback to a user via displayed screen messages. These screen messages are generally temporary and will disappear after a certain amount of time. Some applications also have notification or correspondence capabilities for notifying or corresponding with a user and/or one or more third parties. These types of applications generally provide the notification or correspondences on a predefined communication channel. Examples of types of communication channels that may be used include printer, facsimile, mail, SMS/MMS, etc.  
         [0005]     The contents of the notification or correspondence may include, for example, confirmation that an action has been taken or directions instructing the user what they should do next. Sometimes, an action may result in a number of notifications or correspondences having to be output to one or more parties. An example might be if a user purchases an item in a buyer portal and their manager wants to confirm the transaction. In this case, the user may get a notification such as a confirmation acknowledging receipt of the purchase request and the manager may get a notification that they need to accept the transaction.  
         [0006]     The connection between business processes and the notifications that are to be provided is often customizable. For example, customers can often predefine what content is sent on a certain communication channel to a particular user group for certain business processes. Some applications provide no fixed document generation at all and customers need to create their own documents or tailor existing documents to their own needs. Examples of these types of applications include those that provide functionality to “buy” or “request” items from the system. An example would be a portal such as a learning portal. The learning portal may provide a learning catalog with learning material like class-room courses, web-based or computer-based training, etc. Users (e.g., employees) can look through the catalog and enroll or buy training sessions. The user&#39;s manager may request a list of all training sessions in which the user participates. Another example would be an application that provides tracking information, for example, for tracking the status of an item being shipped. Although there may not be any change in the status of a delivery, someone may still request the current status on an item being shipped. In this case, in response to a user request, the application will read the current status of the order, and generate and return to the user a document indicating the current status.  
         [0007]     In general, correspondence is a very generic service of an application. In fact, often many different processes may call a generic correspondence service to, for example, send a confirmation. Accordingly, although the correspondence service&#39;s functionality itself is independent of the particular process making the call to it, the content of the correspondence generated by the correspondence service depends on the process making the call.  
         [0008]     Accordingly, in general a static document is not sent out for all cases. Instead, systems are generally designed to generate a document for each request. The same is true, for example, for requesting pages from a web server. The document generation process is generally template driven. A Template is a document containing both static text and empty spaces or place holders (e.g., attributes) for dynamic content which will be defined at execution time. During document generation, the attributes are filled in by the application with values from the business process. Examples of values that may be filled in include item ID, date, the receiver, etc. Getting the business data into the document being generated can be performed, for example, using interactive forms based on Adobe software. This system uses a template that provides an interface. The interface describes the different fields in the template that need to be filled in order to generate the document. An application generating the document calls the interface of the template and provides the attributes as interface values.  
         [0009]     One short coming of present systems is that since the correspondence service is a generic service and there may be many different templates and different interfaces for each business process, the correspondence service has to be aware of every single template that might be called and every single interface. This makes it very difficult to change the template, the interface or add a business process. For example, to add a new field to a template, a new field will need to be added to the interface. In addition, if a new business process is added which requires a new template, it will have to be introduced to the correspondence service so that the correct interface can be generated.  
         [0010]     Usually, there is a data provider responsible for filling in the template&#39;s interface attribute on a single field level. Accordingly, there may be a different method used for each field.  
         [0011]     From the template&#39;s point of view, the template depends on the particular business process (e.g., buying, cancellation, etc.) Accordingly, different templates have different interfaces and thus, the application has to know every single interface.  
         [0012]     From an application&#39;s point of view, it would be a good idea to have different templates that use the same attributes and interfaces. The benefit would be that different documents could be generated by the system if the interface is the same in one generic correspondence service. Accordingly, many of these correspondence services predefine an interface with an enumeration of all possible attributes. Thus, the correspondence service becomes a generic application service. One drawback however, is that the application no longer knows what attributes are actually used in a template. The application always has to fill all fields of the interfaces and this reduces system performance.  
         [0013]     In addition, customers may want to enrich the functionality of the correspondence service by adding customer made attributes. For example, a customer may want to add their own branding and/or some additional data to the correspondence. As the attributes are exposed in the interface, adding a new attribute would change the interface which would require changes in the generic correspondence service. These changes may require a substantial amount of code changes. Accordingly, this is quite inflexible from the customer&#39;s point of view.  
         [0014]     An example of a system having a hard dependency between application, template interface and template is shown  FIG. 1 . An application  10  makes calls to template interface specific data provider interfaces  12  and  14  to fill the attributes of templates  16 ,  18 , respectively. Data provider interfaces  12 ,  14  are each responsible for calling data provider  20  and for filling the template interface attributes on a single field level. Accordingly, data provider interfaces uses a specific method for filling each field. Calls by data provider interfaces  12  and  14  are answered by data provider  20  utilizing the data stored in database  22 .  
         [0015]     One major shortcoming of the above-noted systems is that there are two relationships, one from the application to the template and the other from the application to the data provider. Every change in the template requires an adaptation of the application and every change in the application requires the template to be adapted.  
       SUMMARY  
       [0016]     The present disclosure describes tools (in the form of methodologies, apparatuses, and systems) for document generation. The tools may be embodied in one or more computer programs stored on a computer readable medium or program storage device and/or transmitted in the form of a computer data signal in one or more segments via a computer network or other transmission medium.  
         [0017]     A method of document generation comprises in response to a call from an application, getting an inter-face and interface description of a template used to create a document, determining whether a method exists for filling all elements of the interface, making a dynamic call to invoke the method for filling all elements of the interface if the method exists, decomposing the interface into further elements if a method does not exist for filling all elements of the interface and repeating the steps of determining whether a method exists, making a dynamic call and decomposing the interface, until all elements of the interface are accounted for.  
         [0018]     A system for document generation comprises a system for, in response to a call from an application, getting an interface and interface description of a template used to create a document, a system for determining whether a method exists for filling all elements of the interface, a system for making a dynamic call to invoke the method for filling all elements of the interface if the method exists, a system for decomposing the interface into further elements if a method does not exist for filling all elements of the interface and a system for repeating the steps of determining whether a method exists, making a dynamic call and decomposing the interface, until all elements of the interface are accounted for.  
         [0019]     A computer recording medium including computer executable code for document generation comprises code for, in response to a call from an application, getting an interface and interface description of a template used to create a document, code for determining whether a method exists for filling all elements of the interface, code for making a dynamic call to invoke the method for filling all elements of the interface if the method exists, code for decomposing the interface into further elements if a method does not exist for filling all elements of the interface and code for repeating the steps of determining whether a method exists, making a dynamic call and decomposing the interface, until all elements of the interface are accounted for. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0020]     A more complete appreciation of the present disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:  
         [0021]      FIG. 1  is a block diagram showing the hard dependency between application, template interface and template of background systems;  
         [0022]      FIG. 2  is a block diagram of a system according to an embodiment of the present disclosure;  
         [0023]      FIG. 3  is a flow chart for describing operation of the system according to an embodiment of the present disclosure;  
         [0024]      FIG. 4  is a diagram for describing the process of decomposing interfaces according to an embodiment of the present disclosure; and  
         [0025]      FIG. 5  is a block diagram of a computer system capable of implementing various aspects of the embodiments of the present disclosure.  
     
    
     DETAILED DESCRIPTION  
       [0026]     The following exemplary embodiments are set forth to aid in an understanding of the subject matter of this disclosure, but are not intended, and may not be construed, to limit in any way the claims which follow thereafter. Therefore, while specific terminology is employed for the sake of clarity in describing some exemplary embodiments, the present disclosure is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents which operate in a similar manner.  
         [0027]      FIG. 5  shows an example of a computer system  100  which may implement the methods and systems of the present disclosure. The systems and methods of the present disclosure may be implemented in the form of a software application running on a computer system, for example, a mainframe, personal computer (PC), handheld computer, server, etc. The software application may be stored on a recording media locally accessible by the computer system, for example, floppy disk, compact disk, hard disk, etc., or may be remote from the computer system and accessible via a hard wired or wireless connection to a network, for example, a local area network, or the Internet.  
         [0028]     The computer system  100  can include a central processing unit (CPU)  102 , program and data storage devices  104 , a printer interface  106 , a display unit  108 , a (LAN) local area network data transmission controller  110 , a LAN interface  112 , a network controller  114 , an internal bus  116 , and one or more input devices  118  (for example, a keyboard, mouse etc.). As shown, the system  100  may be connected to a database  120 , via a link  122 .  
         [0029]     The computer system  100  is merely exemplary. The specific embodiments described herein are illustrative, computer system(s) as referred to herein may include(s) individual computers, servers, computing resources, networks, etc., and many variations can be introduced on these embodiments without departing from the spirit of the disclosure or from the scope of the appended claims.  
         [0030]     The present disclosure relates to systems and methods for extensible document generation. According to various embodiments of the present disclosure, a system is provided that does not rely on the use of template interface specific interfaces and does not make a hard dependency between application and template. For example, according to an embodiment of the present disclosure, the system will make a dynamic call to the template to get the interface and interface description of the template. The system will make a dynamic call to get the appropriate data provider interface(s) for filling the templates interface. The system will dynamically call the appropriate data provider for each field so that all attributes for the template can be filled. The application can thus query the interface of a template and dynamic calls can be generated to generate the templates document. The application will make the dynamic calls to fill the templates interface using Run Time Type Information (RTTI) also known as Reflections in JAVA.  
         [0031]      FIG. 2  is a block diagram showing an embodiment of the present disclosure. As shown, dynamic template component system  32  replaces the template interfaces specific data providers shown in  FIG. 1 . Accordingly, the present disclosure allows application  30  to operate independently from the template interfaces specific data providers shown in  FIG. 1 . For example, upon a call by application  30 , dynamic template component system  32  will make a dynamic call to interface  33  of template  34  to determine the appropriate signature of the template&#39;s interface. System  32  will then dynamically call the appropriate data provider interface  35  to obtain data from data provider  36  (via database  40 ) for filling in attributes of the template. The same procedure will be performed on template  38  and interface  37 .  
         [0032]     Dynamic template component system  32  uses run time type information (RTTI) to analyze the interfaces  33  and  37  and to filter all attributes to be filled. Each attribute has a method assigned that is used to fill it. These methods have the same type of signature so that the system is able to call each method in a uniform way. The present system traverses the attributes of the template&#39;s interface. For every attribute, RTTI services are used to query the kind (e.g., single field, complex structure or table), the name of the attribute and its elements.  
         [0033]     If the attribute is a complex structure or table, the system looks for a method to fill the complete structure. If there is no such method available, it breaks the structure down into its elements, starting at the template&#39;s interface (root) and terminates on data primitives like single fields (leafs). Filling a node is supported on each level of the tree by assigning a reader method to a structure or a data primitive.  
         [0034]      FIG. 3  is a flow chart for describing operation of the dynamic template component system ( 32 ) according to an embodiment of the present disclosure. In response to a template call from an application  30 , the system  32  gets the interface and interface description of the template (Step S 2 ). Loop limit symbols S 4  and S 16  form a loop in which each attribute of the interface is examined. Using RTTI, the system gets the “NAME” and “TYPE” of the attribute (Step S 6 ). An attribute is created using the “TYPE” (Step S 8 ). A determination is made whether the “NAME” is a registered textvalue (Step S 10 ). That is, a determination is made whether a method exists for filling each attribute of that type. If the “NAME” is a registered textvalue (Yes, Step S 10 ), a dynamic call is used to invoke the textvalue reader to fill the attribute (Step S 12 ) and the loop is repeated for the next attribute. If the “NAME” is not a registered textvalue (No, Step S 10 ), a determination is made whether the “TYPE” is a structure. If “TYPE” is not a structure (No, Step S 14 ), the loop is repeated for the next attribute. If the “TYPE” is a structure (Yes, Step S 14 ), using RTTI, the structure is decomposed into its elements (or attributes) (Step S 20 ), and the loop is repeated for the next attribute. After all attributes have been examined, a dynamic call is made invoking the templates interface (Step S 18 ).  
         [0035]      FIG. 4  is an example of an interface being analyzed according to an embodiment of the present disclosure. Template interface T 1  and template interface T 2  are shown. Template interface T 1  is made up of structure S 1  and structure S 2 . Template interface T 2  is made up of structure S 2  and S 3 . As shown, structure S 1  is made up of field F 1 , field F 2  and field F 3 . Structure S 2  is made up of field F 4  and field F 5 . Structure S 3  is made up of field F 6 , field F 7  and field F 8 .  
         [0036]     According to an embodiment of the present disclosure, dynamic template component system  32  will analyze template interface T 1  to determine whether it can find a method to fill all the elements of the template interface T 1 . If it cannot, the system will perform a first decomposition (Step  1 ) of the interface into structures S 1  and S 2 . Assuming it can not find a method to fill all of structure S 1 , the system will perform a further decomposition (Step  2 ) of the attribute structure into single fields F 1 , F 2  and F 3 . Upon finding methods to fill fields F 1 , F 2  and F 3 , the system will map field F 1  to data provider F 1 , field F 2  to data provider F 2  and field F 3  to data provider F 3  (Step S 3 ) so that the attributes for those fields can be filled.  
         [0037]     As further shown in  FIG. 4 , after the first decomposition (Step  1 ) of template interface T 1  into structure S 1  and structure S 2 , the system will also analyze structure S 2  to determine whether it can find a method to fill all of structure S 2 . In this case, a method is found that can fill all of structure S 2 . Accordingly, structure S 2  is mapped to data provider S 2  so that all attributes of the structure S 2  can be filled for template interface T 1 .  
         [0038]     After the system determines that it cannot find a method that can fill all of structure S 3  of template interface T 2 , the system will perform a decomposition of template interface T 2  into structures S 2  and S 3  (Step  1 ). Structure S 2  of template interface T 2  is the same as the structure S 2  of template interface T 1 . Accordingly, the system will use the same method to fill structure S 2  again. Structure S 2  is thus mapped to data provider S 2 .  
         [0039]     Dynamic template component  32  will analyze structure S 3 . Assuming it can not find a method to fill all of structure S 3 , the system will perform a further decomposition (Step  2 ) of the attribute structure into single fields F 6 , F 7  and F 8 . Upon finding methods to fill fields F 6 , F 7  and F 8 , the system will map field F 6  to data provider F 6 , field F 7  to data provider F 7  and field F 8  to data provider F 8  so that the attributes for those fields can be filled.  
         [0040]     From an application point of view, the embodiments of the present disclosure are capable of calling the templates interface. However, the system is no longer restricted to a special data provider interface. That is, it is able to call different data provider interfaces. Accordingly, there is no longer a need to create one interface supporting all different templates. A template can now have different interfaces with only those attributes they are actually displaying.  
         [0041]     The present system provides a substantial performance improvement because the number of methods called to fill the interface attributes is less then that needed in previous systems. In addition, the present system supports complex data structures to that these is no need for data mapping.  
         [0042]     Another advantage of the present system is from a customer&#39;s point of view. Customers can create new templates and new interfaces or they can extend existing ones. There is no need to change their application to adopt the interfaces changes. Since everything is called dynamically and the attributes are created and filled dynamically, the application won&#39;t even notice the change. Accordingly, users only need to use a new attribute and register a method to fill it. The bridge between the template and the method used to fill the attributes is no longer hard coded and inflexible but is now called dynamically.  
         [0043]     Embodiments of the present disclosure can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The system can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.  
         [0044]     Method steps associated with the present system can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the present disclosure can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).  
         [0045]     Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example, semiconductor memory devices, e.g., EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; CD-ROMs (Compact Disc Read-only Memory) and DVD-ROMs (Digital Versatile Disc Read-only Memory). The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.  
         [0046]     To provide for interaction with a user, the present disclosure can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to t he user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.  
         [0047]     The present system can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middle-ware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the computing system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.  
         [0048]     The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on respective computers and having a client-server relationship to each other.  
         [0049]     The present system has been described in terms of particular embodiments. Other embodiments are within the scope of the following claims.  
         [0050]     Numerous additional modifications and variations of the present disclosure are possible in view of the above-teachings. It is therefore to be understood that within the scope of the appended claims, the present disclosure may be practiced other than as specifically described herein. For example, elements and/or features of different illustrative embodiments maybe combined with each other and/or substituted for each other within the scope of this disclosure and appended claims.  
         [0051]     Numerous additional modifications and variations of the present disclosure are possible in view of the above-teachings. It is therefore to be understood that within the scope of the appended claims, the present disclosure may be practiced other than as specifically described herein.