JP2011215827A - Document generation device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem with form-overlaying data displayed on the picture (tab) of a cloud server for documentation, wherein a user may possibly select any erroneous form which is not suitable for the form generation of a specific picture (tab).SOLUTION: A document generation device communicable with services for management of data is configured to display a form corresponding to information for identifying a picture instructed in a service included in an instruction for overlaying data on the form as the object of selection of a form selection picture.

Description

  The present invention relates to a document generation apparatus capable of communicating with a service that manages data for overlaying a form.

  A form of managing business data and performing various processes on a cloud server has begun to spread. The user accesses the Web page of the cloud server computer via the Internet from the browser of the client computer, and displays business data desired to be browsed on the Web page. When a document creation instruction is issued from the screen, the user is redirected to the document generation server, and the user selects a form to be used for the form overlay on the screen returned from the document generation server. Then, the document generation server acquires business data on the cloud server and generates a document, and the document is downloaded to the browser or uploaded to the cloud server.

  As a conventional method of displaying a form in a selectable manner, there is a method in which display conditions (form paper size, printing orientation, etc.) are specified and only those that meet the conditions are displayed (for example, Patent Documents). 1).

JP 2003-015837 A

  The web page of the cloud server is composed of a plurality of types of screens (tabs), and business data having a different schema is displayed on each screen (tab). When a user documents business data displayed on a specific screen (tab), it is necessary to select a form to be used for documenting from many forms. For this reason, the user may select an incorrect form that is not suitable for documenting a specific screen (tab). The present invention has been made to solve the above-mentioned problems. When business data on a cloud server is documented by form overlay, only forms that can be used on the screen (tab) to be documented are selected. The purpose is to be able to.

  In order to solve the above problems, a document generation apparatus according to the present invention is a document generation apparatus that can communicate with a service that manages data for overlaying a form, and displays the form and a screen of the service. Management means for managing the information for identification in association with each other, receiving means for receiving an instruction for overlaying data managed by the service on the form, and form selection for selecting a form for overlaying the data Display control means for displaying a screen on a display means, acquisition means for acquiring data used for overlay from the service, and a form selected via the form selection screen, acquired by the acquisition means Overlay means for overlaying data, and the display control means includes the receiving means Included in only attached instructions, the form corresponding to the information for identifying the instruction is made the screen in the service, and wherein the displaying for selection of the form selection screen.

  According to the present invention, when data displayed on a screen (tab) of a cloud server is documented by form overlay, a form that is not suitable for the screen (tab) is not displayed on the form selection screen, and an incorrect form is displayed. Will not be selected.

It is a block diagram which shows an example of the system configuration applied to this invention. It is a figure which shows an example of a structure of each hardware applied to this invention. 1 is a diagram illustrating an overall configuration of a document generation system provided in an embodiment of the present invention. It is a software module block diagram of a cloud service. It is a software module block diagram of a Web server. It is a software module block diagram of a document generation server. It is a flowchart which shows the whole process of a web server. It is a flowchart which shows a form selection screen creation process. It is a flowchart which shows a data acquisition process. It is a flowchart which shows a document production | generation process. It is an example of a business screen of a cloud service. It is an example of the table structure of the business data of a cloud service. It is an example of definition information of a document creation button of a cloud service. It is a figure which shows the table structure of a form information table. It is an example of the query command and condition phrase registered in the form information record. It is a flowchart which shows a redirect URL creation process. It is an example of a form selection screen. 10 is a flowchart illustrating a form selection screen creation process according to the second embodiment. It is a figure which shows the process sequence which the document production | generation system in Example 1 performs. It is the figure which showed the screen flow displayed with a web browser. It is an example of a form information table. FIG. 10 is a configuration diagram of a software module of a Web server in Embodiment 2. It is a flowchart which shows form selection custom processing.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing a system configuration applied to an embodiment of the present invention. In the figure, reference numeral 101 denotes a client apparatus 101 that issues a request to a cloud service 102 described later and a document generation server 103 described later. In the figure, reference numeral 102 denotes a cloud service 102 that displays and updates data held in response to requests from the client apparatus 101 and the document generation server 103. In the figure, reference numeral 103 denotes a document generation server 103 which receives a request from the client apparatus 101 and generates a document. In the following description, the cloud service 102 is simply referred to as the cloud service 102.

  In addition, each of the above-described components is connected to be communicable via a network 100. The network is, for example, a LAN such as the Internet, a WAN, a telephone line, a dedicated digital line, an ATM, a frame relay line, a cable TV line, a data broadcasting wireless line, or the like. Moreover, it is what is called a communication network implement | achieved by these combination. The network only needs to be able to transmit and receive data. Therefore, the communication means from the client apparatus 101 to the cloud service 102 and the document generation service 304, the communication means from the document generation server 103 to the cloud service 102, and the communication means between the servers may be different.

  FIG. 2 is a block diagram illustrating a hardware configuration of the client device 101, the cloud service 102, and the document generation server 103 in FIG. In the figure, 201 is a CPU that directly or indirectly controls each device (ROM, RAM, etc. described later) connected by an internal bus and executes a program for realizing the present invention. A ROM 202 stores the BIOS. A RAM (direct storage device) 203 is used as a work area of the CPU 201 or used as temporary storage for loading software modules for realizing the present invention. Reference numeral 204 denotes an indirect storage device such as an HDD (hard disk drive) or an SSD (solid state drive) in which an OS or software module as basic software is stored. Reference numeral 205 denotes an input device such as a keyboard or pointing device (not shown). Reference numeral 206 denotes an output device to which a display is connected. Reference numeral 207 denotes an I / F for connecting to the network 100.

  In these hardware, after starting, the BIOS is executed by the CPU 201 and the OS is loaded from the HDD 204 to the RAM 203 so as to be executable. The CPU 201 loads various software modules (to be described later) from the HDD 204 to the RAM 203 in an executable manner according to the operation of the OS. Various software modules are executed and operated by the CPU 201 in cooperation with the above devices. The I / F 207 is connected to the network 100 and is controlled by the CPU 201 in accordance with the operation of the OS to realize communication by the communication means described above.

  FIG. 3 is a diagram showing an overall configuration of a document generation system (document generation apparatus) according to the embodiment of the present invention.

  In the figure, the client apparatus 101 includes a Web browser 301 as a user interface application. The cloud service 102 manages settings for performing management of users who use the cloud service, business data, and redirection to the document generation server 103 described later. The cloud service 102 is assumed to be used by a plurality of companies / organizations (generally referred to as multi-tenant), and the above-described user management, business data management, etc. are performed for each company / organization used. .

  The document generation server 103 includes a Web server 303 and a document generation service 304. The Web server 303 is configured to have a so-called Web application function, and the client 101 can access via the Web browser 301.

  The Web server 303 returns user interface information in response to a request from the Web browser 301. The web browser 301 renders and displays user interface information obtained from the web server 303. The displayed user interface information includes, for example, a list of forms managed by the document generation server 103 to be described later, an interface for requesting document generation, and the like. When the Web server 303 receives a document generation request from the Web browser 301, the Web server 303 acquires business data from the cloud service 102 and transmits a document generation request to the document generation service 304 together with the business data.

  The document generation service 304 performs overlay processing using the received data and a form managed by itself, and generates document data.

  FIG. 4 is a configuration diagram of software modules that operate on the cloud service 102. Each software module is stored in the HDD 204 shown in FIG. 2, and is loaded into the RAM 203 and executed by the CPU 201 as described above.

  In the figure, the cloud service 102 includes a transmission / reception unit 401, a control unit 402, a page generation unit 403, a session management unit 404, an authentication unit 405, a data management unit 406, a setting management unit 407, and a DB 408.

  The transmission / reception unit 401 processes communication with the Web browser 301 of the client apparatus 101 and the Web server 303 of the document generation server 103. The control unit 402 executes processing according to the received request. The page generation unit 403 generates a web page for returning a response to the web browser 301. The authentication unit 405 authenticates the user who has requested login. The session management unit 404 manages session information of a user who has been successfully authenticated by the authentication unit 405. The data management unit 406 retains business data in the DB 408 and acquires business data from the DB 408 or updates business data in response to a request. A setting management unit 407 holds settings for performing redirection to the document generation server 103. The cloud service 102 executes processing to be described later in cooperation with these components.

  In the figure, reference numeral 408 denotes a DB 408 that stores management user data and business data, and is stored in the HDD 204 shown in FIG. Management user data and business data are managed for each company / organization (hereinafter referred to as an organization). An organization ID is automatically assigned to each organization, and each data is managed together with the organization ID. At the time of user authentication, the organization ID of the organization to which the user belongs is acquired and stored in the session management unit 404. Subsequent processing such as data acquisition is performed based on the organization ID, and it is possible to refer only to data that matches the organization ID.

  The DB 408 also stores settings for performing redirection to the document generation server 103. Settings for redirecting to the business data stored in the DB 408 and the document generation server 103 are updated by the user (administrator) at an arbitrary timing via the Web browser 301.

  FIG. 5 is a configuration diagram of software modules that operate on the Web server 303 of the document generation server 103. Each software module is stored in the HDD 204 shown in FIG. 2, and is loaded into the RAM 203 and executed by the CPU 201 as described above.

  In the figure, the Web server 303 includes a transmission / reception unit 501, a control unit 502, a page generation unit 503, a data access unit 504, a form information management unit 505, and a session management unit 506.

  The transmission / reception unit 501 processes communication with the Web browser 301, the cloud service 102, and the document generation service 304 of the client apparatus 101. The control unit 502 executes processing according to the received request. The page generation unit 503 generates a web page for returning a response to the web browser 301. The data access unit 504 accesses the cloud service 102 and acquires business data. The form information management unit 505 manages a form information table described later. A session management unit 506 manages session information of the Web browser 301. The Web server 303 executes processing to be described later in cooperation with these components.

  FIG. 6 is a configuration diagram of software modules that operate on the document generation service 304 of the document generation server 103. Each software module is stored in the HDD 204 shown in FIG. 2, and is loaded into the RAM 203 and executed by the CPU 201 as described above.

  In the figure, the document generation service 304 includes a request reception unit 601, a control unit 602, a form management unit 603, a document generation unit 604, a document transmission unit 605, and a session management unit 506.

  The request receiving unit 601 receives a document generation request from the Web server 303. The control unit 602 executes processing according to the received request. The form management unit 603 manages form data. The document generation unit 604 performs overlay processing using the business data and form transmitted from the Web server 303 to generate document data. The document transmission unit 605 transmits the generated document data to the web server 303.

  FIG. 11 shows an example of a business screen 1101 when business data is displayed by accessing the cloud service 102 from the Web browser 301 of the client apparatus 101. FIG. 11 shows a state where the user has logged in to the cloud service 102. The business screen 1101 includes tabs 1102 such as “negotiation” and “customer”. The “negotiation” tab is actively displayed, and detailed information 1103 and a product 1104 of a certain negotiation record are displayed. Also, a document creation button 1105 that is set to redirect to the document generation server 103 is displayed. The document creation button 1105 can arbitrarily set the operation when the button is pressed, which tab (screen) is displayed, and the like, and is arranged on the screen by the user (administrator). In this specification, a tab is used as an example for switching the screen of the cloud service 102. However, a method other than a tab may be used.

  FIG. 12 is a diagram illustrating a table structure example of “business negotiation” data among the business data held by the data management unit 406 of the cloud service 102. In FIG. 12, the “negotiation” data table 1200 includes an negotiation table 1201 and a product table 1211.

  The negotiation table 1201 includes a record ID 1202 that is an identifier of the record, and a negotiation name 1203 in which an arbitrary name can be set so that the user can easily distinguish the record. The product table 1211 includes a business record ID 1212, a record ID 1213 that is an identifier of a record in the product table, a product name 1214, a quantity 1215, and a price 1216. The negotiation record ID 1212 is related to the record ID 1202 of the negotiation table.

  FIG. 13 is a diagram illustrating an example of document creation button definition information held by the setting management unit 407 of the cloud service 102. In FIG. 13, document creation buttons are defined in the “negotiation” tab and the “customer” tab. The setting information of the document creation button displayed on the “negotiation” tab includes the button display name 1303 and the document generation server 103. The parameter information for redirecting to is stored.

  The parameter 1304 is a document generation server URI 1304 that designates the URI of the document generation server 103 in the form of “http: //”. A parameter 1305 is a setting for acquiring the session ID of the logged-in user and adding the character string “sid = <session ID>” to the URL parameter. The parameter 1306 is a setting for acquiring a URL for the document generation server 103 to access the cloud service 102 and adding the character string “srv_url = <cloud service URL>” to the URL parameter. The URL for accessing the cloud service 102 is unique for each organization, and at the time of user authentication, the control unit 502 acquires a URL corresponding to the organization to which the user belongs and stores it in the session management unit 404.

  The parameter 1307 is a setting for acquiring the organization ID of the logged-in user and adding the character string “orgid = <organization ID>” to the URL parameter. The parameter 1308 is a setting for acquiring the record ID 1202 of the negotiation record displayed on the screen and adding the character string “recid = <record ID>” to the URL parameter. The parameter 1309 is a setting for adding the character string “tableid = opportunity” to the URL parameter. The parameter 1309 is information for identifying redirection from the “negotiation” tab. In the example, “opportunity” is used, but any character string can be specified as long as the character string uniquely identifies the tab.

  FIG. 14 is a diagram illustrating a table structure of a form information table held by the form information management unit 505 of the Web server 303. The form information table 1401 includes a plurality of form information records 1402. The form information record 1402 includes an organization ID 1403, a display name 1404, a form file name 1405, a query command 1406, a conditional phrase 1407, and a table ID 1408.

  The organization ID 1403 identifies the organization that is the owner of the record. A display name 1404 is a name displayed on the form selection screen. A form file name 1405 is a file name of a form managed by the form management unit 603 of the document generation service 304.

  A query command 1406 describes a query for acquiring data from the cloud service 102. The condition phrase 1407 is for specifying a record to be acquired from the cloud service 102. The table ID 1408 defines which tab on the cloud service 102 can be used.

  FIG. 21 is a diagram illustrating an example of a form information table held by the form information management unit 505 of the Web server 303. In the form information table 2101 of FIG. 21, an organization ID 2102, a display name 2103, a form file name 2104, a query command 2105, a conditional phrase 2106, and a table ID 2107 are registered.

  For example, a form that can be used by a user whose organization ID 2102 is “1001” is an estimate, a delivery note, and a name list, and a form that can be used by a user whose organization ID 2102 is “1002” is an invoice. In addition, the form file name 2104 of the estimate is Mitutori. fcp.

  FIG. 20 is a diagram showing a flow of a screen displayed on the Web browser 301 of the client apparatus 101 in the document generation system of FIG. The business screen 2001 is a screen created by the cloud service 102 and returned to the client device 101. For example, the business screen 1101 in FIG. 11 is displayed. A document generation button 2002 is a button for issuing a document generation request to the cloud service 102. When the document generation button 2002 is pressed, the cloud service 102 returns a URL to be redirected to the document generation server 103.

  When receiving the URL to be redirected, the Web browser 301 of the client apparatus 101 redirects to the document generation server 103 according to this URL. The document generation server 103 that has received the request through redirection returns a form selection screen 2003 to the Web browser 301 of the client apparatus 101. The form selection screen 2003 includes a form selection 2004 and an output method selection 2005. A form selection 2004 is a pull-down menu for selecting a form used for document generation. An output method selection 2005 is a pull-down menu capable of selecting whether a document created by the document generation server 103 is uploaded to the cloud service 102 or downloaded to the Web browser 301 of the client apparatus 101. Further, the Web browser 301 of the client apparatus 101 that has received the selection of the document creation button 2006 from the user transmits the selection results of the form selection 2004 and the output method selection 2005 to the document generation server 103.

  Receiving these pieces of information, the document generation server 103 acquires business data on the business screen 2001 from the cloud service 102. A data acquisition screen 2007 is displayed on the Web browser 301 of the client apparatus 101 while the document generation server 103 is acquiring business data from the cloud service 102. When the document generation server 103 completes the acquisition of business data from the cloud service 102, the document generation server 103 returns an acquisition data confirmation screen 2008 that can confirm the acquired data to the Web browser 301 of the client apparatus 101.

  The Web browser 301 of the client apparatus 101 that has received the selection of the creation button 2009 from the user transmits a document generation request to the document generation server 103. Upon receiving the document generation request, the document generation server 103 performs document generation processing using the selected form and the business data acquired from the cloud service 102. Then, the document is uploaded to the cloud service 102 or downloaded to the Web browser 301 of the client apparatus 101 according to the selected output method. In the figure, an example in which the document is downloaded to the Web browser 301 and the document is previewed is shown.

  Next, a document generation procedure using the document generation system according to the first embodiment of the present invention will be described in detail with reference to the drawings. In the following drawings, the cloud service is abbreviated as CPS.

  FIG. 19 shows the flow of processing performed by the document generation system in Embodiment 1 of the present invention. It is assumed that the user has already logged in to the cloud service 102 on a login screen (not shown). Further, it is assumed that the business record screen 1101 of the negotiation record shown in FIG. 11 is displayed on the Web browser 301, and the document creation button 1105 is set in advance as shown in FIG.

  First, the user presses the document creation button 1105 on the business screen 1101 displayed on the Web browser 301 of the client apparatus 101 (S1901). Then, in the cloud service 102, a redirect URL creation process described later is performed in S1902.

  FIG. 16 is a flowchart showing redirect URL creation processing of the cloud service 102 when the document creation button 1105 is pressed in S1902 of FIG. In this specification, the control unit 402 includes a CPU, RAM, ROM, HDD, and the like, and the procedure shown in the flowchart is stored in one of the storage units of the RAM, ROM, and HDD of the control unit 402 and executed by the CPU 201. .

  When the control unit 502 detects that the user has pressed the document creation button in step S1601, the control unit 502 acquires parameters set in the document creation button in step S1602. Next, in step S1603, the control unit 502 acquires the document generation server URI 1304. Next, in step S1604, the control unit 502 acquires a parameter 1305, acquires a session ID from the session management unit 404, and creates a character string “sid = <session ID>”.

  Next, in step S <b> 1605, the control unit 502 acquires a parameter 1306, acquires a URL for accessing the cloud service 102 from the session management unit 404, and creates a character string “srv_url = <URL>”. Next, in step S1606, the control unit 502 acquires the parameter 1307, acquires the organization ID from the session management unit 404, and creates the character string “orgid = <organization ID>”. Next, in step S1607, the control unit 502 acquires the parameter 1308, acquires the record ID 1202 of the negotiation record in FIG. 11, and creates a character string “recid = <record ID>”. Next, in step S1608, the control unit 502 acquires the parameter 1309.

  In step S1609, the control unit 502 generates a redirect URL based on the document generation server URI 1304 acquired in step S1603 and the character string acquired in steps S1604 to S1608. Then, a response for redirecting is returned to the browser (S1610). With the above processing, the cloud service 102 executes redirect URL creation processing.

  The above is the description of the redirect URL creation processing, and the description returns to FIG.

  In step S <b> 1903, the web browser 301 transmits the session ID of the cloud service 102, the URL for accessing the cloud service 102, the organization ID, the record ID 1202, and the parameter 1309 to the web server 303 of the document generation server 103. The ID acquired here is various parameters registered in the document creation button, as described with reference to FIG. The session ID is “sid = <session ID>”, and the URL for accessing the cloud service 102 is “srv_url = <URL>”. The organization ID is “orgid = <organization ID>”, the record ID 1202 is “recid = <record ID>”, and the parameter 1309 is “tableid = opportunity”. In this way, since the information for identifying the screen instructed is included in the overlay instruction transmitted from the cloud service 102, the document generation server selects the form corresponding to the instruction to be selected. Display control.

  In step S1903, the web server 303 that has received (accepted) the request from the web browser 301 performs form selection screen creation processing in step S1904.

  FIG. 8 is a flowchart showing the form selection screen creation processing of the Web server 303 in S1904 of FIG. In this specification, the control unit 502 includes a CPU, a RAM, a ROM, an HDD, and the like. .

  In step S <b> 801, the control unit 502 waits for reception of a request from the web browser 301. Upon receiving the request, the control unit 502 acquires a session ID of the cloud service 102, a URL for accessing the cloud service 102, an organization ID, a record ID 1202, and a parameter 1309 from the transmitted parameters in S802. The acquired information is stored in the RAM 203.

  Next, the control unit 502 determines whether or not the organization ID is included in the transmitted parameters (S803). If it is determined in S803 that the organization ID is included in the parameter, the control unit 502 acquires a record with the same organization ID 1403 value from the form information table 1401 via the form information management unit 505 in S805. To do. Next, the control unit 502 determines whether or not the parameter 1309 is included in the transmitted parameters (S806). If it is determined in S806 that the parameter 1309 is included, the table ID 1408 is acquired from the record acquired in S805, and it is determined whether the value of the parameter 1309 matches the table ID 1408 (S808). If it is determined that they match, the display name 1404 of the record is acquired and added to the form selection list, and the form selection list is stored in the RAM 203 (S809). Subsequently, in step S810, the control unit 502 determines whether there is another record. If there is another record, the control unit 502 performs the process again from step S807. If it is determined in S806 that the parameter 1309 is not included in the transmitted parameters, the display names 1404 of all records acquired in S805 are acquired and stored in the RAM 203 (S812).

  In step S <b> 814, the control unit 502 stores the session ID of the cloud service 102 stored in the RAM 203, the URL for accessing the cloud service 102, the organization ID, and the record ID 1202 in the session management unit 506.

  Next, in step S815, the control unit 502 acquires the form selection list stored in the RAM 203, requests the page generation unit 503 to generate the form selection screen 2003, and displays the generated form selection screen 2003 on the Web. It returns to the browser 301 (S816). With the above processing, the Web server 303 executes form selection screen creation processing. On the form selection screen generated by this processing, the display corresponding to the screen on which the overlay instruction is given by the cloud service 102 is selected and controlled.

  In this embodiment, when it is determined in S806 that the parameter 1309 is not included in the transmitted parameters, all forms are displayed on the form selection screen 2003. However, the present invention is not limited to this method, and an error may occur when the parameter 1309 is not included in the transmitted parameters.

  The above is the description of the form selection process, and the description returns to FIG. In step S1905, the user selects form selection 2004 and output method selection 2005 on the form selection screen 2003. When the document creation button is pressed, a document generation request is transmitted from the Web browser 301 to the Web server 303 together with the selected form selection 2004 and the selected output method selection 2005.

  In step S1905, when the Web server 303 receives a document generation request, the Web server 303 performs data acquisition processing described later.

  FIG. 9 is a flowchart showing data acquisition processing of the Web server 303 in S1906 to S1909 of FIG. In this specification, the control unit 502 includes a CPU, a RAM, a ROM, an HDD, and the like. .

  When the control unit 502 receives a request from the Web browser 301 (YES in S901), the control unit 502 determines whether the session is valid via the session management unit 506 in S802. When it is determined that the session is valid, the control unit 502 determines in step S904 whether the URI is a data acquisition request URI or a data acquisition status confirmation request URI. Since S1905 in FIG. 19 is a data acquisition request, it is determined here to be the URI of the data acquisition request. If it is determined that the URI is a data acquisition request, the control unit sets the next page transition destination to “data acquisition in progress” and stores the transition destination in the session management unit 506 in step S905. In step S <b> 906, the control unit 502 requests the page generation unit 503 to generate the data acquisition screen 2007, and the page generation unit 503 generates the data acquisition screen 2007. The data acquisition screen 2007 includes an auto-redirect URL for accessing the Web server 303 and confirming the data acquisition status. Then, the generated data acquisition screen 2007 is transmitted to the Web browser 301 (S1907 in FIG. 19).

  Next, in step S <b> 907, the control unit 502 acquires the session ID of the cloud service 102, the URL for accessing the cloud service 102, the organization ID, and the record ID 1202 from the session management unit 506.

  Next, in step S908, the control unit 502 acquires the transmitted form and output method information from the request. Next, in step S909, the control unit 502, via the form information management unit 505, from the form information table 1401, the organization ID 1403 matches the acquired organization ID, and the display name 1404 matches the form acquired from the request. Get the record to be executed. Then, the control unit 502 acquires a query command 1406 and a conditional phrase 1407 of the record. Further, the form file name 1405 of the record is acquired and stored in the RAM 203. Next, in step S <b> 910, the control unit 502 creates a query for acquiring data from the cloud service 102 from the acquired query command 1406, the acquired conditional phrase 1407, and the acquired record ID 1202.

  FIG. 15 shows an example of a query command 1406 and a conditional phrase 1407 registered in the form information record of the form information table 1401 and an example of a created query.

  FIG. 15A shows an example of the query command 1406. In this example, it is defined that the price 1216, the quantity 1215, the negotiation record ID 1212, and the product name 1214 are acquired from the product table 1211. The product table 1211 corresponds to the OpportunityLineItems 1505, the price 1216 corresponds to the UnitPrice 1501, and the quantity 1215 corresponds to the Quantity 1502. In addition, the negotiation record ID 1212 is “OpportunityId1503”, and the product name 1214 is “Product. Name 1504 corresponds to each. Further, “‘ Opportunity 1.Id ’” indicates that a character string is replaced at the time of execution.

  FIG. 15B is an example of the conditional phrase 1407. In this example, the character string “Opportunity1.Id” specified in the query command 1406 is replaced with the value of the recid parameter. FIG. 15C is an example of a query created in S910 when the Web server 303 receives a data acquisition request together with the parameter “recid = 1345”.

  Subsequently, the control unit 502 connects to the cloud service 102 using the session ID of the cloud service 102 acquired in S907 and the URL for accessing the cloud service 102 (S911). In S912, the created query is executed to make a data acquisition request (S1906 in FIG. 19). Next, in step S913, the control unit 502 determines whether data acquisition has been successful. When it is determined that the data acquisition is successful (YES in S913), the control unit 502 sets the next page transition destination to “data confirmation” in S914 and stores the transition destination in the session management unit 506. In step S915, the control unit 502 stores the data acquired in step S912, the form file name 1405 stored in the RAM 203, and the output method acquired in step S908 in the session management unit 506.

  If it is determined that the data acquisition has failed (NO in S913), the control unit 502 sets the next page transition destination to “error” in S916 and stores the transition destination in the session management unit 506.

  19, when the Web browser 301 receives the data acquisition screen 2007 generated in S906, it is automatically redirected, and a request for confirming the data acquisition status is transmitted from the Web browser 301 to the Web server 303 (FIG. 19). S1908).

  In FIG. 9, when the control unit 502 of the Web server 303 receives a request for confirming the data acquisition status (YES in S901), in S902, it is determined whether the session is valid via the session management unit 506. When it is determined that the session is valid, the control unit 502 determines in step S904 whether the URI is a data acquisition request URI or a data acquisition status confirmation request URI. Note that since S1908 in FIG. 19 is a data acquisition status confirmation request, it is determined here to be the URI of the data acquisition status confirmation request. When it is determined that the URI is the data acquisition status confirmation request, the control unit 502 acquires the next transition destination from the session management unit 506 in S917. Further, the acquired transition destination is determined. If “data acquisition is in progress”, the data acquisition screen 2007 is transmitted again to the web browser 301 (S923). When the transition destination is “data confirmation”, in step S920, the control unit 502 acquires the data acquired in step S912 from the session management unit 506, and requests the page generation unit 503 to generate the acquisition data confirmation screen 2008. The page generation unit 503 generates an acquisition data confirmation screen 2008 (S921). Then, the control unit 502 transmits the generated acquisition data confirmation screen 2008 to the Web browser 301 (S1909 in FIG. 19). When the transition destination is “error”, the control unit 502 requests the page generation unit 503 to generate an error screen in S919, the page generation unit 503 generates an error screen, and the control unit 502 displays the error screen on the Web. Send to browser 301. With the above processing, the Web server 303 executes data acquisition processing.

  When the user presses the creation button on the acquired data confirmation screen 2008 returned to the Web browser 301 in S1909, a document generation request is transmitted from the Web browser 301 to the Web server 303 (S1910).

  In step S1910, when the Web server 303 receives a document generation request, a document generation process described later is performed.

  FIG. 10 is a flowchart showing document generation processing of the Web server 303 in S1910 to S1912 of FIG. In this specification, the control unit 502 includes a CPU, a RAM, a ROM, an HDD, and the like. .

  When the control unit 502 receives a request from the Web browser 301 (YES in S1001), in S1002, the control unit 502 determines whether the session is valid via the session management unit 506. If it is determined that the session is valid, the control unit 502 acquires acquired data, a form file name 1405, and an output method from the session management unit 506 in S1003. Next, in step S1004, the control unit 502 makes a document creation request to the document generation service 304 together with the acquired data and the form file name 1405 (S1911 in FIG. 19). In step S <b> 1005, the control unit 502 acquires a response from the document generation service 304 and determines whether the document creation is successful. When it is determined that the document creation is successful (YES in S1005), the control unit 502 determines the value of the output method (S1006). If upload is specified in the output method, the control unit 502 acquires a document included in the response from the document generation service 304 and uploads the document to the cloud service 102 in step S1008. If download is specified in the output method in S1006, the control unit 502 acquires a document included in the response from the document generation service 304 in S1007, and transmits the document to the Web browser 301 (FIG. 19 S1912).

  If it is determined in S1002 that the session is not valid (NO in S1002), or if it is determined in S1005 that the document creation has been successful (NO in S1005), the control unit 502 generates a page so as to generate an error screen. Request to the unit 503. The page generation unit 503 generates an error screen, and the control unit 502 transmits the error screen to the web browser 301. With the above processing, the Web server 303 executes document generation processing.

  Note that since the document creation processing (overlay processing using a form) in the document creation service 304 of the document creation server 103 is known, the description thereof is omitted in this embodiment. In the document generation process of this embodiment, a response is returned to the Web browser 301 after the document generation process of the document generation service 304 is completed. However, the present invention is not limited to this method, and it is of course possible to return the screen indicating that the document is being created to the Web browser 301 for automatic redirection as in the case of data acquisition processing.

  FIG. 17 shows an example of the form selection screen created by the form selection screen creation processing described in the present embodiment and displayed on the Web browser 301. In the form selection screen of FIG. 17, the Web server 303 holds the form information table shown in FIG. 21, and the user with the organization ID “1001” presses the document creation button 1105 from the business screen 1101 shown in FIG. It is a form selection screen displayed at the time. In FIG. 17, it can be seen that only forms (estimate, delivery note) that can be used on the business screen 1101 are displayed to be selectable.

  In the present embodiment, the processing of the entire system has been described with reference to FIG. 19, but the operation of the Web server 303 alone is as shown in the flowchart shown in FIG. In step S701, the control unit 502 waits for a request, and in step S702, confirms the URL of the request. And the control part 502 performs each process of S703, S704, and S705 according to URL. Here, the form selection process of S702 corresponds to the flowchart of FIG. 8, the data acquisition process of S703 corresponds to the flowchart of FIG. 9, and the document generation process of S704 corresponds to the flowchart of FIG.

  In the first embodiment, the form selection screen is displayed even when only one form is displayed to be usable on the form selection screen. Depending on the organization, there is a case where a document created by the document generation server 103 is uploaded to the cloud service 102 or downloaded to the Web browser 301 of the client apparatus 101 as an output method.

  In organizations that operate with a fixed output method, there is no need to display the form selection screen when there is only one form available, and the form selection screen can be displayed simply by performing an extra user operation (button press). It is inefficient to display. In this embodiment, when only one form can be used, data acquisition is automatically performed without displaying a form selection screen.

  FIG. 22 is a configuration diagram of software modules that operate on the Web server 303 of the document generation server 103 in this embodiment. Since the description here is substantially the same as in FIG. 5 described above, only the different parts will be described below. In the figure, reference numeral 2206 denotes a custom processing management unit 2206 that manages custom processing for each organization in association with the organization ID. When it is desired to customize the form selection process, data acquisition process, etc., for each organization, the custom process is registered in the custom process management unit 2206 together with the organization ID by the user (manager) in advance.

  FIG. 18 is a flowchart showing the form selection screen creation process of the Web server 303 in this embodiment. Since the description here is substantially the same as FIG. 8 of the above-described embodiment, only different parts will be described below. In FIG. 18, in step S1805, the control unit 502 transmits an organization ID to the custom processing management unit 2206, and inquires whether an organization-specific custom processing is registered. Upon receiving the response from the custom process management unit 2206, the control unit 502 determines whether an organization-specific custom process is registered (S1805), and if an organization-specific custom process is registered (YES in S1805). The custom process is executed. The process after the custom process unique to the organization is not registered (NO in S1805) is the same as FIG.

  FIG. 23 is a flowchart showing the form selection custom processing of the Web server 303 in this embodiment. Since the description here is substantially the same as FIG. 8 of the above-described embodiment, only different parts will be described below.

  In S2311, the form selection list stored in the RAM 203 is acquired, and it is determined whether or not there is one element included in the list. When it is determined that the number of elements included in the list is one (YES in S2311), the control unit 502 acquires an element in the list (form display name 1404) and sets the acquired element as a request (S2314). . Next, in step S2315, the control unit 502 acquires an output method and sets the output method to a request. And the control part 502 performs a data acquisition process according to the flow as described in FIG. 9 (S2316).

  In this embodiment, the form selection custom process of the organization that wants to operate with a fixed output method is registered in the custom process management unit 2206, and is defined to acquire a fixed output method in S2315 in the custom process. ing. As another output method acquisition method, it is also possible to include it as a parameter in the redirect URL from the cloud service 102.

  In the first embodiment, the form selection screen is displayed even when there is no form that can be displayed on the form selection screen. If there is no form to be displayed that can be used, a screen for uploading each item of the form and the form information record 1402 is generated and returned to the Web browser 301. Then, each item of the form and the form information record 1402 may be uploaded from the Web browser 301. It is also possible to perform data acquisition from the cloud service 102 and document generation processing using each item of the uploaded form and form information record 1402.

DESCRIPTION OF SYMBOLS 103 Document generation server 303 WEB server 304 Document generation service 502 Control part 503 Page generation part 504 Data access part 505 Form information management part 605 Document generation part

Claims (1)

A document generation device capable of communicating with a service for managing data for overlaying a form,
A management means for managing the form in association with information for identifying the service screen;
Receiving means for receiving an instruction to overlay the data managed by the service on the form;
Display control means for displaying on the display means a form selection screen for selecting a form to overlay the data;
Obtaining means for obtaining data used for overlay from the service;
Overlay means for overlaying the data acquired by the acquisition means for the form selected via the form selection screen;
The display control unit displays a form corresponding to information for identifying a screen on which the instruction is performed in the service, included in the instruction received by the receiving unit, as a selection target of the form selection screen. A document generation device characterized by the above.

Images