JP2016170661A - Information processing system, server device, information processing device, control method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing system which allows a user to edit the layout of a document page in a Web browser, and to browse the document page using layouts before editing and after editing.SOLUTION: A document generation server 101 generates a document page by performing overlay output of form information and field data of a document. The document generation server 101 generates data for displaying an editing screen for editing the layout of the document page. The data includes a page information file 901. When a user performs an editing operation on a document browsing screen 1101 for editing of a client device 102, the client device 102 updates the page information file 901 on the basis of the editing operation. The document generation server 101 associates the updated page information file 901 with the form information indicating the layout of the document page before updating by a request URL table 2000.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information processing system, a server device, an information processing device, a control method, and a program.

  Increasingly, companies are replacing paper media information with document data for the purpose of improving business efficiency and saving resources by making paperless. For example, business forms that are operated in-house are often the target, especially because the forms output by the core system output a large number of pages and the operation cost becomes enormous. Is being actively promoted. Also, a method for creating a form document (form image) such as a PDF format by overlaying field data on the form information that forms the form template (flowing field data into the form and applying it). Has been proposed.

  In addition, cloud computing systems have begun to spread as a form of managing business data and various processes on the server computer side. The user accesses the web page of the cloud server computer via the Internet from the web browser of the client computer, and browses the document document digitized on the web page. Furthermore, it is conceivable to edit / print the document data being viewed according to the business flow. At this time, it is desirable to be able to edit the form information itself as a template of the form.

  Patent document 1 discloses a form management system in which a form setter designs an electronic form input form (form data) in a form design terminal device. Patent Document 1 describes that a screen (form form design screen) for editing an input form is displayed.

JP 2008-225932 A

  However, in Patent Document 1, it is necessary to use a dedicated GUI (Graphical User Interface) in order to edit the input form. The input form edited via the GUI is uploaded to the form data management server and provided to the data input person. That is, in order to provide the edited input form to the data input person, it is necessary to overwrite the input form before editing, and it is not possible to hold the layout of both the forms before and after editing. Although it is possible to save the input form after editing as another input form, both input forms before and after editing are not linked.

  SUMMARY OF THE INVENTION An object of the present invention is to provide an information processing system that enables editing of a layout of a form page in a Web browser and allows browsing of the form page using both the layout before and after editing. And

  An information processing system according to an embodiment of the present invention displays a form generation means for generating a form page by outputting the form information and field data of the form as an overlay, and an editing screen for editing the layout of the form page. Editing screen generation means for generating data for the data, the data includes at least screen part information related to the arrangement of the screen parts displayed on the editing screen, and when the editing operation is performed on the editing screen, based on the editing operation Update means for updating the screen component information, and association means for associating the updated screen component information with the form information indicating the layout of the form page before being updated.

  According to the present invention, the layout of a form page can be edited in a Web browser, and the form page can be viewed using both the pre-edited layout and the edited layout. As a result, the information processing apparatus is not limited to an information processing apparatus having dedicated editing software, and an information processing apparatus having a Web browser can edit and view a form page and can easily perform operations related to the form. Become.

It is a figure which shows the system configuration example of this embodiment. It is a figure which shows the hardware constitutions of information processing apparatus. It is a figure which shows the structural example of the software module which operate | moves with a form production | generation server. It is a figure explaining the form overlay process by a form production | generation server. It is a figure explaining the process which produces | generates edit form browsing screen data. It is a figure which shows an example of a login screen. It is a figure which shows an example of a form selection screen. It is a flowchart explaining an overlay output process. It is an example of a parts information file. It is a figure which shows a form browsing screen. It is a figure which shows the edit document browsing screen. It is a figure which shows an example of a completion screen. It is a flowchart explaining edit processing. It is a figure explaining the process which produces | generates form browsing screen data. It is an example of a parts information file. It is a figure which shows an example of a confirmation dialog. It is a figure which shows the result of having performed common edit operation to all the form pages. It is a flowchart explaining edit processing. It is a figure explaining the process which produces | generates form browsing screen data. It is a figure explaining the concept of a request URL table. It is a flowchart explaining a preservation | save process.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.
(First embodiment)
FIG. 1 is a diagram illustrating a system configuration example of the present embodiment.
The information processing system illustrated in FIG. 1 includes a form generation server 101 and a client device 102. The form generation server 101 is the server device of this embodiment. The form generation server 101 executes overlay output processing. That is, the form generation server 101 generates a form page by superimposing a field data file, which is text data, and a form information file including predetermined form information. In response to a request from the client apparatus 102, the form generation server 101 instructs the virtual printer to generate print data corresponding to the form page as an electronic file.

  Further, the form generation server 101 executes processing for generating editing form browsing screen data and form browsing screen data. The editing form browsing screen data is data for displaying a browsing screen (editing form browsing screen) for browsing and editing the layout (model) of the form page. In the present embodiment, the layout editing screen data includes at least a parts information file, an editable form page, and an editing program.

  The form browsing screen data is data for displaying a browsing screen (form browsing screen) for browsing a form page and editing field data displayed on the form page. In the present embodiment, the form browsing screen data includes at least an editable form page and a form browsing program. When the user views the form page with the layout of the form page edited by the user on the edit form view screen, the form view screen data includes a part information file. Details will be described later with reference to FIG.

  The part information file is a file (screen part information) in which information related to the arrangement of images such as screen parts included in the form page is described. Details will be described later with reference to FIG. The editing program is a control program for controlling browsing and editing of the layout of the form page. The form browsing program is a control program for controlling browsing and editing of the form page. In the present embodiment, the editing program and the form browsing program are web applications that can be distributed via a network and operate on a web browser.

  The editing program and the form browsing program are, for example, a mashup language (HTML) that represents a web page and an application program (Java program) that is operated by JavaScript that is a programming language that operates on a web browser. Note that Java and JavaScript are registered trademarks. In addition, the editing program and the form browsing program may be applications executed on a computer system other than a web application that operates on a web browser.

  In addition, the form generation server 101 generates only an electronic form file of a form page and a file representing part information. The client apparatus 102 may be configured to include an application that can execute a browsing / editing operation on a form page and a browsing / editing operation on a layout of a form page using these files.

  The form generation server 101 and the client device 102 are connected to be communicable via the network 100. The network 100 is, for example, the Internet, a LAN, 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. The network 100 may be realized by a combination of these.

FIG. 2 is a diagram illustrating a hardware configuration of an information processing apparatus that implements a form generation server and a client apparatus.
The apparatus shown in FIG. 2 includes CPUs (Central Processing Units) 201 to I / F 207, respectively. The CPU 201 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 (Read Only Memory) stores a BIOS (Basic Input Output System).

  A RAM (Random Access Memory) 203 is used as a work area of the CPU 201 or used as a temporary storage for loading a software module for realizing the present invention. An HDD (Hard Disk Drive) 204 stores an OS and software modules as basic software. Instead of the HDD 204, an SSD (Solid State Drive) may be provided.

  The input device 205 inputs information according to a user operation input. The input device 205 is, for example, a keyboard (not shown) or a pointing device. The output device 206 outputs information. A display is connected to the output device 206. The I / F is an interface for connecting to the network 100. After the apparatus is activated, 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 from the HDD 204 to the RAM 203 so as to be executable at any time according to the operation of the OS. Various software modules are executed and operated by the CPU 201. The I / F 207 is controlled by the CPU 201 according to the operation of the OS, and realizes communication with an external device.

FIG. 3 is a diagram illustrating a configuration example of a software module that operates on the form generation server.
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. The form generation server 101 includes an access control unit 301 to a part information DB 309. The access control unit 301 performs user authentication in response to a request from the client device 102.

  The page generation unit 302 generates a Web page for returning a response to the client device 102. The page generation unit 302 also generates files such as HTML and JavaScript necessary for the web application that is the editing program and the form browsing program, and returns them to the client apparatus 102. The page generation unit 302 also returns the part information file to the client device 102. The data access unit 303 performs access processing to each DB (305 to 309).

  The form generation unit 304 reads the form information file 401 from the form information DB 306 via the data access unit 303. Further, the form creation unit 304 reads the field data file 403 from the field data DB 307 via the data access unit 303. The form generation unit 304 generates a form page by superimposing the read form information indicated by the form information file 401 and the field data indicated by the field data file 403. Then, the form generation unit 304 generates an electronic file of the form page using software such as a virtual printer. In the present embodiment, the electronic file of the form page is in SVG (Scalable Vector Graphics) format.

  The form data DB (database) 305 stores form data. The form data indicates information such as form name and owner, and has information indicating from which form information file and field data file the form is generated. The form data has information indicating a form page that is a result of the overlay output process of the form. Further, the form data includes information that associates the layout of the form page before and after editing when the user edits the form page layout. Specifically, it has a request URL table that holds URLs corresponding to pairs of form information files and edited parts information files. Details will be described later with reference to FIG.

  The form information DB 306 stores form information files. The field data DB 307 stores field data files. A form page file generated by the form generation unit 304 is stored in the form page DB 308. The parts information DB 309 stores a parts information file.

FIG. 4 is a diagram for explaining overlay processing by the form generation server 101.
Form information is created using a dedicated form information design system. The form information is composed of a fixed figure (form figure) that does not depend on field data, and a figure (field figure) that displays received field data in accordance with a specified output format. In order to create a field graphic, it is necessary to create an item (field) for receiving field data in advance. When a field graphic is created, it is internally associated with the field from which it was created. In the case of a tabular field graphic (table graphic) 402, it is necessary to receive field data in record units, so a record field is created.

  The form generation server 101 reads a form information file 401 in which field graphics are defined and a corresponding field data file 403. The form generation server 101 executes overlay output processing by superimposing the read form information file 401 and the field data file 403. Reference numeral 404 in FIG. 4 shows an example of the overlay output processing result.

FIG. 5 is a diagram for explaining processing for generating editing form browsing screen data.
In step S <b> 501, the client apparatus 102 transmits a login request to the form generation server 101 in response to an operation on the login screen displayed on the Web browser of the client apparatus 102.

FIG. 6 is a diagram illustrating an example of a login screen.
The user inputs a user name and password in a user name input text box 602 and a password input text box 603 on the login screen 601 and presses a login button 604. As a result, the client apparatus 102 transmits a login request to the form generation server 101.

  Returning to the description of FIG. In step S <b> 502, the access control unit 301 of the form generation server 101 performs login processing based on the content of the login request received from the client device 102. If the access control unit 301 performs basic authentication and confirms that the user name and password are valid, the process advances to step S503. Note that the basic authentication is a general authentication process, and a description thereof will be omitted. In step S <b> 503, the page generation unit 302 of the form generation server 101 generates a form selection screen according to the logged-in user information.

FIG. 7 is a diagram illustrating an example of a form selection screen.
On the form selection screen 701, an area 702 displays the user name of the currently logged-in user. The drop-down list 703 displays a list of forms owned by the currently logged-in user. The information displayed in the drop-down list 703 is a form name of the form owned by the logged-in user, extracted from the form data DB 305 by the page generation unit 302 via the data access unit 303.

  A form operation button 704 is a button for executing a preview for the form corresponding to the form name selected from the drop-down list 703. A form operation button 705 is a button for previewing the form corresponding to the form name selected in the drop-down list 703 using the layout after the edit operation is performed on the edit form browsing screen. It is. A form operation button 705 is a button for editing the layout of the form page for the form corresponding to the form name selected from the drop-down list 703.

  Returning to the description of FIG. In step S <b> 504, the access control unit 301 of the form generation server 101 returns the form selection screen 701 generated in step S <b> 503 to the client apparatus 102 via the network 100. In step S <b> 505, the client apparatus 102 receives the form selection screen 701 from the form generation server 101, and the web browser displays the form selection screen 701.

  In step S <b> 506, the user selects the form name of the form to be operated from the drop-down list 703 in the form selection screen 701. In step S <b> 507, when the user presses the edit button 706 in the form selection screen 701, the client apparatus 102 transmits a generation request for the edit form browsing screen to the form generation server 101. The generation request for the edit form browsing screen has information that can specify the form to be viewed and edited.

  In step S <b> 508, the form generation unit 304 of the form generation server 101 acquires a form information file related to the form to be viewed / edited from the form information DB 306 via the data access unit 303. Further, the form generation unit 304 acquires a field data file related to the form to be viewed / edited from the field data DB 307 via the data access unit 303. In step S509, the form generation unit 304 of the form generation server 101 performs dummy field data file (dummy data) generation processing using the field data file acquired in step S508. In S510, the form generation unit 304 of the form generation server 101 performs overlay output processing using the form information file acquired in S508 and the dummy field data file generated in S509.

FIG. 8 is a flowchart for explaining generation of a dummy field data file and overlay output processing using the same in S509 and S510 of FIG.
In step S <b> 801, the form generation unit 304 determines whether the request accepted by the access control unit 301 is a form page layout editing request, a form page preview request, or a form page part addition preview request. If the request received by the access control unit 301 is a template page template editing request, the process advances to step S802. If the request received by the access control unit 301 is a form page preview or part addition preview request, the process advances to step S805.

  In step S802, the form generation unit 304 acquires the maximum number of characters that can be input to each field field from the field data file. In step S803, the form generation unit 304 creates a dummy field data file based on the maximum number of characters that can be input in each field acquired in step S802. In step S804, the form generation unit 304 performs overlay output processing using the form information file and the dummy field data file. In step S805, the form generation unit 304 performs overlay output processing using the form information file and the field data file.

  Returning to the description of FIG. In S511, the form generation unit 304 converts the PDF form page generated in S501 (specifically, S804 or S805) into an SVG form page. Since a PDF form page cannot be directly edited on the Web browser, it is converted into a format that can be edited (in the case of this embodiment, the SVG format). Next, the form generation unit 304 stores the generated SVG format form page in the form page DB 308 via the data access unit 303. Then, the form generation unit 304 adds information specifying the generated SVG format form page to the corresponding form record in the form data DB 305.

  In step S <b> 512, the form generation server 101 returns the URL of the edit form browsing screen for the target form requested in step S <b> 507 to the client apparatus 102. The URL to be returned includes information for specifying the form page in the SVG format generated in S510. In the case of this embodiment, the form name of the form data related to the form page is included in the URL to be returned. In step S <b> 513, the client apparatus 102 transmits a request (redirect request) for redirecting to the editing form browsing screen to the form generation server 101 using the URL returned in step S <b> 511.

  In step S514, the page generation unit 302 of the form generation server 101 functions as an editing screen generation unit, and generates editing form browsing screen data according to the content of the redirect request transmitted in step S512. The generated form viewing screen data for editing is required for the form page file of the requested form, the editing program that controls the viewing, editing, and saving operations of the form page file, and the editing and saving operations. Parts information file. Based on the form name in the redirect request, the page generation unit 302 acquires the form page file and the part information file related to the requested form from the form page DB 308 and the part information DB 309 and includes them in the edit form browsing screen data. .

FIG. 9 is an example of a parts information file according to this embodiment.
In the present embodiment, the part information file is in a JSON (Java Script Object Notation) format. A record 902 indicates an arrangement of SVG parts which are images (screen parts) or the like to be arranged on a form browsing screen (form page). A record 903 indicates the name of the SVG part. A record 904 indicates drawing position coordinates where the SVG parts are arranged.

  Returning to the description of FIG. In step S <b> 515, the form generation server 101 returns the edit form browsing screen data generated in step S <b> 514 to the client apparatus 102. In step S516, the client apparatus 102 receives the response from the form generation server 101, and displays the editing form browsing screen on the Web browser based on the editing form browsing screen data included in the response.

FIG. 11 is a diagram showing an editing form browsing screen in the present embodiment.
A form display area 1102 in the edit form browsing screen 1101 is an area for displaying an SVG form page. When the user performs a flick operation in the horizontal direction in the form display area 1102, switching to the previous or next form page can be performed. The SVG parts display area 1103 is an area for displaying SVG parts that can be arranged on the form page (form display area 1102). When the user performs a drag operation (drag and drop) on the SVG parts in the SVG parts display area 1103 within the area of the form display area 1102, the SVG parts can be arranged on the form page.

  When the user performs a drag operation in the form display area 1102, the editing program for the edit form browsing screen operates to perform the editing process (part addition process) described with reference to FIG. FIG. 11 shows a state in which the mail mark 1104 and the check box 1105 in the SVG parts display area 1103 are respectively arranged in 1107 and 1106 in the form display area 1102 by a drag operation. A save button 1108 is a button for saving the edited form page template in the form generation server 101. Processing for saving the edited form page template will be described later with reference to FIG.

FIG. 13 is a flowchart for explaining an editing process corresponding to an editing operation on the editing form browsing screen according to the present embodiment.
In step S <b> 1301, the user performs a drag operation on the SVG part from the SVG part display area 1103 on the edit form browsing screen 1101 to the form display area 1102.

  In S1302, the editing program included in the editing form browsing screen acquires the type of the SVG part dragged (arranged) in S1301. In S1303, the editing program acquires the position coordinates of the SVG parts arranged in S1301. In S1304, the editing program updates the part information file 901 based on the information acquired in S1302 and S1303. In step S1305, the editing program redraws the form display area 1102 based on the part information file 901 updated in step S1304.

FIG. 21 is a diagram for explaining a saving process (linking process) executed when the save button is pressed on the editing form browsing screen.
In step S <b> 2101, the user presses the save button 1108 on the edit form browsing screen 1101. In step S <b> 2102, the client apparatus 102 transmits a request (save request) to save the part information file 901 to the form generation server 101. The save request includes an updated parts information file, that is, a parts information file 901 held on the client device 102 side. The save request includes a form information file name.

  In step S <b> 2103, the form generation unit 304 of the form generation server 101 acquires an updated parts information file included in the save request. In S2104, the form generation unit 304 acquires the form information file name included in the save request. In step S <b> 2105, the page generation unit 302 generates a URL (uniquely specified) corresponding to the combination of the form information file and the updated parts information file. In step S2106, the form generation unit 304 updates the request URL table that links the part information file, the form information file, and the URL acquired in steps S2103 to S2105, respectively.

FIG. 20 is a diagram for explaining the concept of the request URL table.
The URL record 2001 included in the request URL table 2000 includes information for specifying the URL 2002, the form information file 2003, and the part information file 2004. A URL 2002 indicates a URL corresponding to (uniquely specified) the pair of the form information file and the updated parts information file generated in S2105. The form information file 2003 indicates the form information file associated with the URL 2002 acquired in S2104 or information for specifying the form information file. The part information file record 2004 indicates the part information file associated with the URL 2002 acquired in S2103 or information for specifying the part information file.

  Returning to the description of FIG. In step S2107, the page generation unit 302 of the form generation server 101 generates a save completion screen described with reference to FIG. The save completion screen includes the URL 2002 generated in S2105. In step S <b> 2108, the page generation unit 302 returns the storage completion screen generated in step S <b> 2107 to the client device 102 via the data access unit 303. In step S <b> 2109, the client apparatus 102 receives a response from the form generation server 101 and displays a storage completion screen included in the response.

FIG. 12 is a diagram illustrating an example of a save completion screen.
The save completion screen 1200 is a screen that is displayed after the save button 1108 of the edit form browsing screen 1101 is pressed. The save completion screen 1200 includes areas 1201 to 1206. The areas 1201 and 1203 to 1206 are the same as the areas 702 to 706 of the form selection screen shown in FIG. An area 1202 displays an URL necessary for the part addition preview, and displays the URL generated in S2105 of the storage process shown in FIG.

FIG. 14 is a diagram for explaining processing for generating form browsing screen data in the present embodiment.
The process for generating the form browsing screen data is executed when the preview button 704 or the part addition preview button 705 in the form selection screen 701 shown in FIG. 7 is pressed. In step S1401, the user presses the preview button 704 or the part addition preview button 705 in the form selection screen 701.

  In step S <b> 1402, the client apparatus 102 transmits a form page generation request to the form generation server 101. The form page generation request includes information that can specify a form to be viewed. When the part addition preview button 705 is pressed, the URL 2002 (request URL displayed in the area 1202 on the save completion screen) held on the client apparatus 102 side is designated as the generation request transmission destination. In step S <b> 1403, the form generation unit 304 of the form generation server 101 acquires a form information file related to the form to be viewed from the form information DB 306 via the data access unit 303. Further, the form generation unit 304 acquires a field data file related to the form to be viewed from the field data DB 307 via the data access unit 303. Then, the form generation unit 304 performs overlay output processing using the acquired form information file and field data file. Further, the form generation unit 304 converts the PDF form page generated by the overlay output process into an SVG form page.

  In step S <b> 1404, the form generation server 101 returns the URL of the form browsing screen of the target form requested in step S <b> 1402 to the client apparatus 102. Note that the URL of the form browsing screen is specifically the URL of the preview screen or the part addition preview screen. The preview screen is a screen that displays a form page in a layout before editing. The part addition preview screen is a screen for displaying a form page in the layout after editing. The URL to be returned includes information for specifying the SVG form page generated in S1403. In the present embodiment, the form name of the form data related to the form page is included in the URL to be returned. In step S <b> 1405, the client apparatus 102 transmits a request (redirect request) for redirecting to the preview screen or the part addition preview screen to the form generation server 101 using the URL returned in step S <b> 1404.

  In step S1406, the page generation unit 302 of the form generation server 101 generates form browsing screen data, specifically data for displaying a preview screen, according to the content of the redirect request transmitted in step S1405. That is, the page generation unit 302 functions as a form browsing screen generation unit. The generated form browsing screen data includes a form page file of a form that is a request target and a form browsing program. In step S <b> 1407, the access control unit 301 of the form generation server 101 determines whether the request is a preview screen generation request or a part addition preview screen request from the redirect request transmission destination transmitted in step S <b> 1405. If it is determined from the redirect request destination that the request is a preview screen generation request, the process advances to step S1410. If it is determined that the request is a part addition preview screen generation request from the redirect request transmission destination, the process advances to step S1408.

  In step S <b> 1408, the form generation unit 304 acquires a part information file associated with the URL 2002 that is the transmission destination of the redirect request and the request URL table 2000 via the data access unit 303. In step S <b> 1409, the form generation server 101 returns the form page file, the form browsing program, and the part information file to the client apparatus 102 as data for displaying the form browsing screen data, specifically, the part addition preview screen. . In step S <b> 1410, the form generation server 101 returns data for displaying the preview screen generated in step S <b> 1406 to the client apparatus 102. In step S1411, the client apparatus 102 receives the response from the form generation server 101, and displays a preview screen or a part addition preview screen based on the form browsing screen data included in the response. That is, when the part information file is included in the response, the part addition preview screen is displayed, and when the part information file is not included, the preview screen is displayed.

FIG. 10 shows a form browsing screen.
FIG. 10A is a form browsing screen displayed when the preview button 704 is pressed on the form selection screen 701 in FIG. That is, this is a screen for displaying the form page in the layout before the user performs the edit operation on the form page. FIG. 10B is a form browsing screen displayed when the part addition preview button 705 is pressed on the form selection screen 701 in FIG. That is, this is a screen for displaying the form page in the layout after the user performs the edit operation on the form page. In the form browsing screen 1002, a check box 1003 and a mail mark 1004 are added to the form browsing screen 1001 before the layout is edited.

  As described above, according to the present embodiment, the layout of the form page can be edited in the Web browser, and the form page can be viewed and edited using both the pre-edited layout and the edited layout.

(Second Embodiment)
In the first embodiment, the case of editing the layout of one form page has been described. In the present embodiment, a case where a common layout is edited for all of a plurality of form pages will be described. In addition, description is abbreviate | omitted about the part which is common in 1st Embodiment, and only a different part is demonstrated below.

FIG. 15 is an example of a parts information file according to this embodiment.
The part information file 1501 includes records 1502 to 1505. A record 1505 indicates whether or not to place the SVG part on all the form pages. The other records 1502 to 1504 of the parts information file are the same as the records 902 to 904 of the parts information file 901 (FIG. 9) of the first embodiment.

FIG. 18 is a flowchart for explaining an editing process (part addition process) corresponding to an editing operation on the editing form browsing screen in the present embodiment.
In S1801, the user operates the form page by dragging the SVG part of the SVG part display area 1103 into the area of the form display area 1102 on the edit form browsing screen 1101 as described with reference to FIG. SVG parts are arranged in Then, the user performs a double click operation on the placed SVG part. In this example, it is assumed that the SVG part 1107 is double-clicked. In S1802, the editing program included in the editing form browsing screen 1101 displays a confirmation dialog for confirming whether or not the SVG part 1107 double-clicked in S1301 is to be arranged on all the form pages.

FIG. 16 is a diagram illustrating an example of a confirmation dialog.
In this example, it is assumed that a drag operation and a double click operation of the SVG part are performed on the edit form browsing screen 1601. When there are a plurality of form pages, a plurality of form pages (1602 and 1603) can be displayed on the edit form browsing screen 1601 as shown in FIG. The confirmation dialog 1606 includes an SVG part 1607, a cancel button 1608, and an OK button 1609.

  An SVG part 1607 indicates an SVG part that is a target for checking whether or not to place the form on all form pages. A cancel button 1608 is a button to be pressed when the user cancels the operation, that is, when the SVG part 1607 is not arranged on all the form pages. An OK button 1609 is a button to be pressed when the user places the SVG part 1607 on all the form pages.

  Returning to the description of FIG. In step S1803, the user presses a button on the confirmation dialog 1606. In step S1804, the editing program determines in step S1803 what the user has input (whether the pressed button is the cancel button 1608 or the OK button 1609). If the user presses the cancel button 1608, the process ends. If the user presses the OK button 1609, the process proceeds to S1805.

  In S1805, the editing program acquires the position coordinates where the part 1605 double-clicked in S1801 is arranged. In step S1806, the editing program updates the record 1505 of the part information file 1501 to True. In step S <b> 1807, the editing program redraws the form display area of the edit form browsing screen based on the updated parts information file 1501. At this time, if the record 1505 of the part information file 1501 (record whose array element is “common”) is True, the editing program executes redrawing so that the target SVG part is arranged on all the form pages. Specifically, the position coordinates are set so that the target SVG part (specified by records 1503 to 1504) is arranged at the same position in all the form pages by using the record 1504 indicating the position coordinates. Calculate Then, the editing program places the target SVG part on all the form pages based on the calculated position coordinates.

FIG. 17 is an example of a screen showing a result of adding a common SVG part to all the form pages by the editing process shown in FIG.
As a result of the SVG part 1705 of the form display area 1702 of one form page being arranged on all the form pages, the SVG part 1706 is also arranged in the form display area 1703 of other form pages. It shows that.

FIG. 19 is a diagram for explaining processing for generating form browsing screen data in the present embodiment.
Since the processing of S1901 to S1910 is the same processing as the form browsing screen data in the first embodiment, description thereof is omitted. In step S 1911, the client apparatus 102 receives a response from the form generation server 101. If the part addition preview button 705 is pressed in step S1901, the process advances to step S1908 in step S1907. Therefore, the response includes the part information file 1501. When the part information file 1501 is not included in the response, the form browsing program included in the form browsing screen data displays a preview screen as in the first embodiment. When the part information file 1501 is included in the response, the form browsing program reads the part information file.

  In step S1912, the editing program determines whether there is an SVG part in which the record 1505 of the read part information file 1501 (the record whose array element is “common”) is True. If there is no SVG part whose record 1505 in the part information file 1501 is True, the process advances to S1914, and the form browsing program displays a part addition preview screen as in the first embodiment. If there is an SVG part whose record 1505 of the part information file 1501 is True, the process proceeds to S1913. In S1913, the form browsing program calculates the position coordinates of the placement destination so that the SVG part whose record 1505 in the parts information file 1501 is True is placed at the same position on all form pages. To do. In S1914, based on the position coordinates calculated by the editing program in S1913, the SVG parts are arranged on all the form pages, and the part addition preview screen is displayed.

  Thus, according to the present embodiment, the same effects as in the first embodiment can be obtained. Furthermore, according to this embodiment, when editing a common layout for a plurality of form pages, the edit operation can be applied to all pages without performing the edit operation for each form page. The form page editing operation can be performed more easily.

(Other embodiments)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  As mentioned above, although preferable embodiment of this invention was described, this invention is not limited to these embodiment, A various deformation | transformation and change are possible within the range of the summary.

101 Form generation server 102 Client device 901 Parts information file 2000 Request URL table

Claims (12)

A form generation means for generating a form page by overlaying the form information and field data of the form;
Editing screen generation means for generating data for displaying an editing screen for editing the layout of the form page,
The data includes at least screen part information related to an arrangement of screen parts displayed on the editing screen,
An update unit that updates the screen component information based on the editing operation when an editing operation is performed on the editing screen;
A linking means for linking the updated screen component information and the form information indicating a layout of the form page before being updated;
An information processing system characterized by this. A browsing screen generating means for generating data for displaying a browsing screen of the form page, including the form information and the screen component information linked to the form information according to selection;
Display means for displaying the browsing screen based on the data generated by the browsing screen generating means,
When the screen part information is included in the data generated by the browsing screen generation means, a browsing screen in which the layout of the form page is edited is displayed.
The information processing system according to claim 1. When it is selected to display the form page after the editing operation, the browsing screen generation means displays the screen part information associated with the form information and the browsing page of the form page. Included in the data
When it is selected to display the form page before the editing operation, the browsing screen generation means displays the screen part information linked to the form information and the browsing page of the form page. Not included in the data for
The information processing system according to claim 2.   The said display means updates the display of the said edit screen based on the updated screen component information, when the said update means updates the said screen component information. Information processing system. The form generation means uses dummy data having the maximum number of characters of each field as the field data when generating a form page to be displayed on the editing screen.
The information processing system according to any one of claims 1 to 4, wherein The editing operation on the editing screen is an operation of dragging and dropping the screen component onto the form page,
The update means updates the screen component information in response to drag and drop being performed.
The information processing system according to claim 1, wherein the information processing system is an information processing system.   The information processing system according to claim 1, wherein the association unit generates a URL corresponding to the set of the screen component information and the form information. In the editing screen, when an editing operation is performed on the form page, an application unit that applies the content of the editing operation to all the form pages is further provided.
The information processing system according to any one of claims 1 to 7. A form generation means for generating a form page by overlaying the form information and field data of the form;
Editing screen generation means for generating data for displaying an editing screen for editing the layout of the form page,
The data includes at least screen part information related to an arrangement of screen parts displayed on the editing screen,
When the screen component information is updated according to the editing operation on the editing screen,
A linking means for linking the updated screen component information and the form information indicating a layout of the form page before being updated;
The server apparatus characterized by the above-mentioned. First receiving means for receiving data for displaying an edit screen for editing the layout of the form page generated by overlaying the form information and field data of the form;
The data received by the first receiving means includes at least screen part information relating to the arrangement of screen parts displayed on the editing screen,
An update unit that updates the screen component information based on the editing operation when an editing operation is performed on the editing screen;
Request means for requesting that the updated screen component information and the form information indicating the layout of the form page before being updated are linked and stored;
Second receiving means for receiving data for displaying a view screen of the form page, including the form information and the screen component information associated with the form information according to selection;
Display means for displaying the browsing screen based on the data received by the second receiving means,
When the data received by the second receiving means includes the screen part information, a browsing screen in which the layout of the form page is edited is displayed.
An information processing apparatus characterized by that. A form generation process for generating a form page by overlaying the form information and field data of the form;
An edit screen generating step for generating data for displaying an edit screen for editing the layout of the form page,
The data includes at least screen part information related to an arrangement of screen parts displayed on the editing screen,
When an editing operation is performed on the editing screen, an update step of updating the screen component information based on the editing operation;
A linking step of linking the updated screen component information and the form information indicating a layout of the form page before being updated,
A method for controlling an information processing system.   The program for functioning a computer as each means with which the information processing system of any one of Claim 1 thru | or 8 is provided.

Images