JP2011197834A - Screen control system, server, and screen control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To appropriately control the display of a UI screen corresponding to each device.SOLUTION: In a screen control system in which an information processor, an image forming apparatus, and a server are connected to each other, the server is provided with: a first generation means for, when receiving the display request of a screen from the information processor, generating first screen information including UI definition information corresponding to a screen whose display request has been received and a program for acquiring display data to be displayed on a UI component included in the UI definition information by asynchronous communication; and a second generation means for, when receiving the display request of the screen from the image forming apparatus, acquiring the display data to be displayed on the UI component included in the UI definition information corresponding to the screen whose display request has been received by using a rendering function, and for generating second screen information for plotting a screen including the UI component and the display data to be displayed on the UI component.

Description

  The present invention relates to a screen control system, a server, and a screen control method for performing screen display control.

  In recent years, applications that use documents in business are increasing. For this reason, it is required to handle documents using a UI such as a business application instead of file management like a general Explorer.

  With multifunction peripherals (MFPs), the use of such business collaboration has increased, and the need to incorporate paper documents such as purchase orders and application forms from customers into the system has become apparent. It's getting on. Various documents are used in various businesses, but it can be said that, for example, a UI suitable for order management and a UI suitable for drawing management are different.

  For example, in Patent Document 1, in a multi-function peripheral, one or more keywords corresponding to a screen constituent element are assigned to each screen constituent element such as a button that can be arranged on the GUI. A technique for improving the efficiency of the editing operation by allowing the screen components to be extracted from the keywords by storing them is disclosed.

  On the other hand, as a Web application, iGoogle (registered trademark) of Google (registered trademark) for customizing UI on the Web application has been developed.

  However, in the above-described conventional business application, a DB (database) design is made in a form specialized for each business, and the application is developed. For example, a document management application stays at a level where metadata is assigned for each document type, and in order to change the UI according to business, customization such as a large-scale SI is required.

  When importing an image scanned from an MFP into the system, an application that operates on an individual MFP is developed, or a Web browser (hereinafter also referred to as an MFP browser) that operates on the operation panel of the MFP is used. There is a method of developing a Web screen for MFP, but neither is easy.

  In addition, Ajax (Asynchronous JavaScript (registered trademark) + XML) or the like can be used in the browser for the PC, but there are cases where the built-in browser such as the MFP browser can only perform simple HTML rendering.

  For example, in a backbone system in which a large number of devices are connected and handle a large amount of data in a short time, it is desirable to display an appropriate UI screen for each device, but saving all the various screens is inefficient. is there.

  Therefore, the present invention has been made in view of the above problems, and provides a screen control system, an information processing apparatus, and a screen control method capable of appropriately displaying and controlling a UI screen corresponding to each apparatus. With the goal.

  The screen control system according to one aspect of the present invention is a screen control system in which an information processing apparatus, an image forming apparatus, and a server are connected, and the server includes UI definition information in which UI parts of the screen are defined. For each screen, first storage means for storing display data, second storage means for storing display data to be displayed on the UI component, and when a screen display request is received from the information processing apparatus, First generation means for generating first screen information including corresponding UI definition information and a program for acquiring display data to be displayed on a UI component included in the UI definition information by asynchronous communication, and the image forming apparatus When a display request is received from the screen, display data to be displayed on the UI component included in the UI definition information corresponding to the screen that has received the display request is acquired using a rendering function, and the UI A second generation unit for generating second screen information for drawing a screen including display data to be displayed on the product and the UI component, and the first screen information generated by the first generation unit is transmitted to the information processing apparatus. Or transmission means for transmitting the second screen information generated by the second generation means to the image forming apparatus.

  A server according to another aspect of the present invention is a server connected to the information processing apparatus and the image forming apparatus, and stores UI definition information in which UI parts of the screen are defined for each screen. Storage means, second storage means for storing display data to be displayed on the UI component, UI definition information corresponding to the screen that has received the display request when receiving a display request for the screen from the information processing apparatus, A first generation unit that generates first screen information including a program for acquiring data to be displayed on a UI component included in UI definition information by asynchronous communication; and a screen display request from the image forming apparatus The display data to be displayed on the UI component included in the UI definition information corresponding to the screen for which the display request has been received is acquired using a rendering function, and the display data to be displayed on the UI component and the UI component is obtained. Second generation means for generating second screen information constituting the screen, and the first screen information generated by the first generation means is transmitted to the information processing apparatus or generated by the second generation means Transmitting means for transmitting the second screen information to the image forming apparatus.

  The screen control method according to another aspect of the present invention includes a first storage unit that is connected to the information processing apparatus and the image forming apparatus and stores UI definition information in which UI parts of the screen are defined for each screen. A screen control method in a server comprising second storage means for storing display data to be displayed on the UI component, wherein when a screen display request is received from the information processing apparatus, the screen corresponding to the display request is received A first generation step of generating first screen information including UI definition information to be performed and a program for acquiring data to be displayed on a UI component included in the UI definition information by asynchronous communication; and a screen from the image forming apparatus. When the display request is received, data to be displayed on the UI component included in the UI definition information corresponding to the screen that has received the display request is acquired using a rendering function, and the UI component and A second generation step of generating second screen information constituting a screen including data to be displayed on the UI component, and transmitting the first screen information generated by the first generation step to the information processing apparatus, or A transmission step of transmitting the second screen information generated by the second generation step to the image forming apparatus.

  ADVANTAGE OF THE INVENTION According to this invention, the screen control system, information processing apparatus, and screen control method which can display-control appropriately the UI screen corresponding to each apparatus can be provided.

The figure which shows an example of the screen control system in an Example. The block diagram which shows an example of the hardware of the server 110 in an Example. The block diagram which shows an example of the function of the server 110 in an Example. The figure which shows an example of the class relationship of the data model used in an Example. The figure which shows an example of the definition data of UI screen. The figure which shows an example of a part of display screen. The figure which shows an example of a display screen. The figure explaining cooperation of the parts of a display screen. The figure which shows an example of the drive program by an event. The figure which shows an example of the program of event generation. The figure which shows an example of the program which produces | generates URL when drawing UI components. The figure which shows an example of the definition data of a select box. The figure which shows an example of a select box. The figure which shows an example of the data acquired by API. The figure which shows an example of the definition data of a folder list. The figure which shows an example of a folder list. The figure explaining the example of rendering. The figure which shows an example of the tab setting for PC. FIG. 5 is a diagram illustrating an example of tab settings for an MFP. The figure which shows an example of the HTML source for PCs. The figure which shows an example of the screen for PC. FIG. 3 is a diagram illustrating an example of an HTML source for an MFP. FIG. 3 is a diagram illustrating an example of an MFP screen. The figure which shows an example of acquisition of JSON data, and drawing of UI components. The sequence diagram which shows an example of login. The sequence diagram which shows an example of the display process of a screen. The figure explaining the outline | summary of a folder hierarchy. The figure which shows an example of the data structure of the data regarding a folder hierarchy. The figure which shows an example of a hierarchy definition and metadata. The figure which shows the example of a screen of the data shown in FIG. The figure which shows an example of view set data. The figure which shows an example of view (tab) data. The figure which shows an example of the data for view formation. The figure explaining the example of screen switching of URL of a view, a view, and a view set. The figure explaining the difference in a screen by the difference in a tab. The figure which shows the relationship between a view set and a tab. The figure which shows an example of account information. The figure which shows an example of organization information. The figure which shows an example of user information. The figure which shows an example of view filter information. The figure which shows the example of API.

  Embodiments of a screen control system, an information processing apparatus (server), and a screen control method according to the present invention will be described below in detail with reference to the accompanying drawings.

  In the following embodiment, as an example of an image input device for inputting image data, an information processing device or a multifunction device having a printer function, a scanner function, a copy function, and a facsimile function mounted in one housing is taken as an example. explain. However, the present invention is not limited to these, and the present invention can be applied to any of a scanner device, a facsimile device, and a copy device having a display screen as long as image data can be input.

[Example]
<System and hardware>
FIG. 1 is a diagram illustrating an example of a screen control system 100 in the embodiment. As shown in FIG. 1, the screen control system 100 includes an MFP 101, a client device (PC) 103, a mobile terminal 105, an MFP 107, a server 110, a server 131, and a database (hereinafter also referred to as DB) 133.

  For example, the MFP 101 displays a display screen using an MFP browser. The PC 103 can use asynchronous communication such as Ajax on the browser. When a request for display data on the display screen occurs, the PC 103 can acquire display data by performing asynchronous communication with the server.

  The portable terminal 105 can use Ajax on the browser, like the PC 103. The MFP 107 acquires display data of the display screen using an API from an application dedicated to the MFP 107.

  Upon receiving a display screen display request from each of the devices 101, 103, 105, and 107, the server 110 transmits screen information (HTML format) that constitutes a display screen suitable for each device. Specifically, the server 110 includes a customization unit 111, a screen control unit 113, an interface unit 115, a template management unit 117, a metadata management unit 119, a screen data management unit 121, and an access management unit 123.

  The customization unit 111 customizes access rights to files and folders, metadata assigned to the files and folders, display screen layout, UI parts, and the like. The file is, for example, a document file (including an image file), and may be an audio file or a video file.

  The screen control unit 113 receives a display screen drawing request or display data acquisition request from each of the devices 101, 103, 105, and 107. The screen control unit 113 creates screen information (for example, information in HTML format) that defines a display screen suitable for the device that has received the request, and transmits the created screen information to the device. That is, the screen control unit 113 performs display control of a display screen suitable for each device.

  The interface unit 115 supports, for example, JSON (JavaScript (registered trademark) Object Notation) format, XML (Extensible Markup Language) format, and WebDAV (Web-based Distributed Authoring and Versioning). Each device acquires desired data using the API of the interface unit 115.

  The template management unit 117 stores and manages the metadata format of files and folders and the display screen template.

  The metadata management unit 119 holds “Cabinets” indicating the definition of the folder hierarchy, “Folders” indicating the information on the folder, “Entries” indicating the information on the file, and “Tags” indicating the definition of the metadata. Information managed by the metadata management unit 119 will be described later.

  The screen data management unit 121 manages information related to display screens displayed on the devices 101, 103, 105, and 107. “Smart View” is screen information of a display screen for a device capable of displaying the display screen using Ajax. “View Set” is screen information for a screen that groups one or more display screens. “MFP View” is screen information of a display screen for a device (for example, MFP) that cannot use Ajax. “Mobile View” is screen information of a display screen for a mobile terminal.

  The access management unit 123 manages information for restricting access to a file hierarchy (“Cabinets”), a folder (“Folders”), a file (“Entries”), and / or a view (“View”: screen). .

  The server 131 is a server that simply holds and manages files stored in each folder. The server 131 includes a storage unit (“Storage Cache”) that stores a URL of a file storage destination and an acquisition unit (API) that acquires a file. The DB 132 is a database that stores display screen definition data, UI component definition data, and the like of each device. DB 133 is a database that stores at least files. The server 131 and the DB 133 may be included in the server 110 or may be a single DB. In addition, there may be a user information management unit that manages user information.

  Next, the hardware configuration of the server in the embodiment will be described. FIG. 2 is a block diagram illustrating an example of a hardware configuration of the server 110 in the embodiment. As illustrated in FIG. 2, the server 107 includes a control unit 201, a main storage unit 203, an auxiliary storage unit 205, an external storage device I / F unit 207, and a network I / F unit 211.

  The control unit 201 is a CPU that controls each device, calculates data, and processes in a computer. The control unit 201 is an arithmetic device that executes a program stored in the main storage unit 203, receives data from the input device or the storage device, calculates and processes the data, and outputs the data to the output device or the storage device.

  The main storage unit 203 is a ROM (Read Only Memory), a RAM (Random Access Memory), or the like, and a storage device that stores or temporarily stores programs and data such as an OS and application software that are basic software executed by the control unit 201 It is.

  The auxiliary storage unit 205 is an HDD (Hard Disk Drive) or the like, and is a storage device that stores data related to application software and the like. The auxiliary storage unit 205 may store a predetermined program via a network. This predetermined program can be processed by being installed.

  The external storage device I / F unit 207 is an interface between the server 107 and a storage medium 209 (for example, a flash memory, an SD card, etc.) connected via a data transmission path such as a USB (Universal Serial Bus).

  Further, a predetermined program is stored in the storage medium 209, and the program stored in the storage medium 209 is installed in the server 107 via the external storage device I / F unit 207, and the installed predetermined program is stored in the server 107. Can be executed.

  The network I / F unit 211 has a communication function connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) constructed by a data transmission path such as a wired and / or wireless line. This is an interface between the device and the server 107.

  The server 107 may include an input unit and a display unit. The input unit includes a keyboard having cursor keys, numeric input, various function keys, and the like, and a mouse and a slice pad for selecting keys on the display screen of the display unit. The input unit is a user interface for a user to give an operation instruction to the control unit 201 or input data.

  The display unit is configured with a CRT, LCD, or the like, and displays according to display data input from the control unit 201.

<Function>
FIG. 3 is a block diagram illustrating an example of functions of the server 110 in the embodiment. In the example illustrated in FIG. 3, the server 110 includes a reception unit 301, a transmission unit 303, a screen generation unit 305, a user authentication unit 311, and an access control unit 313. The reception unit 301 and the transmission unit 303 are realized by the network I / F unit 211, and the screen generation unit 305, the user authentication unit 311, and the access control unit 313 can be realized by the control unit 201 and the main storage unit 303. The screen generation unit 305 corresponds to the screen control unit 113, and the access control unit 313 corresponds to the access management unit 123.

  The receiving unit 301 receives a display screen display request from each device or a display data acquisition request to be displayed on the UI component. The transmission unit 303 transmits screen information or display data to the requesting apparatus. The display screen display request is made by, for example, instructing identification information of the display screen or instructing a URL that holds the information of the display screen.

  The screen generation unit 305 includes a first generation unit 307 and a second generation unit 309. When receiving a screen display request from an apparatus having an asynchronous communication, for example, an Ajax-enabled browser, the first generation unit 307 generates first screen information for rendering a display screen in, for example, an HTML format. The generated first screen information is transmitted by the transmission unit 303 to the apparatus that has requested display. The first screen information includes UI definition data of a display screen that has received a display request, a program for acquiring display data to be displayed on a UI component included in the UI definition data, such as a JavaScript (registered trademark) program. Including. The UI definition data is data that defines the UI layout, UI parts, and the like of the display screen.

  When receiving a screen display request from an image forming apparatus that performs rendering using simple HTML, the second generation unit 309 generates second screen information for rendering the display screen in, for example, an HTML format. The generated second screen information is transmitted to the device that has requested display by the transmission unit 303. The second generation unit 309 acquires display data to be displayed on the UI component included in the UI definition data of the display screen that has received the display request using a rendering function, and includes the display data included in the acquired UI component. Second screen information for drawing the screen is generated.

  In determining whether or not the device that has requested display is capable of asynchronous communication, the screen generation unit 305 stores the identification information (for example, IP address) of the device in association with whether or not asynchronous communication is possible, and stores the device. Whether or not asynchronous communication is possible may be determined according to the identification information.

  Even when Ajax can be used in the MFP browser, rendering for the MFP by the second generation unit 309 can be considered due to the problem of rendering speed and screen size. At this time, the screen generation unit 305 performs device determination using the IP address of the device that has requested display. If the IP address indicates the information processing device (PC) 103, the screen generation unit 305 generates the first generation unit. The screen is generated using the means.

  The user authentication means 311 performs user authentication by acquiring a user ID and password from each device. Information regarding the authenticated user is output to the access control means 313. The information about the user includes at least one of user information including a user ID, a user name, organization information to which the user belongs, and metadata added to the user information.

  The access control means 313 restricts the display screen that can be displayed by restricting access to the display screen (view) for the logged-in user. Details of the access restriction will be described later.

(Model class relationship)
Next, a data model used in the embodiment will be described. FIG. 4 is a diagram illustrating an example of a class relationship of the data model used in the embodiment. The “Organization” class 401 is a class having an organization ID “rs_organization_id (or simply organization_id)”.

  A “Cabinets” class 409, a “Folder” class 411, an “Entry” (file) class 413, a “Tag” class 415, and a “Doctype” class 417 are classes of files and folders actually used by the user.

  The “ContentFilter” class 419 and the “ViewFiler” class 421 are classes for setting access rights for files and views. The “SmartView” class 423 and the “ViewSet” class 425 are classes for setting a UI for displaying folders and files in a format close to business contents. The “User” class 427 is a class for setting user information. The double enclosed class is a class that can be set by the user administrator.

(UI definition)
FIG. 5 is a diagram illustrating an example of UI definition data. “Rs Organization” illustrated in FIG. 5 indicates an organization ID. “Config” 501 indicates an example of UI definition data. Each UI component displayed on the display screen is defined in the UI definition data.

  For example, a line 511 indicates UI component identification information, and “inv_no_search” is defined. A line 513 indicates a component of the UI part, and “search_box” is defined.

  Line 515 indicates that the UI component is associated with the case where data is displayed on the UI component, and when a request is sent to a predetermined URL, the data included in the search result is returned. A line 517 indicates a predetermined display area, and “tab_left” is defined. A line 519 indicates a search key for searching the display data, and a search key “stag — 14” is defined. The line 521 defines a name when this UI component is displayed. Note that the data shown in FIG. 5 is stored in the DB 132, for example.

  FIG. 6 is a diagram illustrating an example of a part of the display screen. FIG. 6 is an example when the UI definition data shown in FIG. 5 is displayed. The title 601 shown in FIG. 6 displays “INV number search” on the line 521 shown in FIG. A search box 603 displays a UI component of the line 513. It should be noted that the UI definition data used in the embodiment displays the title 601 and the search box 603 shown in FIG. 6 only by describing the data related to the UI parts on the lines 511 to 521 shown in FIG. Thereby, UI customization is easy. The screen shown in FIG. 6 can be displayed on the PC 103, for example, when the first generation unit 305 generates the first screen information based on the UI definition data shown in FIG.

(screen structure)
Next, the configuration of the display screen used in the embodiment will be described. FIG. 7 is a diagram illustrating an example of a display screen. The solid line frame shown in FIG. 7 shows a pane (pane: predetermined display area), and the dotted line frame shows parts (parts: UI parts). One or more parts are defined in the pane. However, the part 711 in which an operation event such as a logo does not need to be defined in the pane. The pane 701 is a “tab_left” pane, the pane 703 is a “tab_main_top” pane, and the pane 705 is a “tab_main_bottom” pane.

  In the pane 701, parts such as a select box 713 and a search box 715 are defined. In the pane 703, parts of the document list 717 are defined. In the pane 705, parts of the document list 719 are defined.

Next, the cooperation of parts on a screen including panes and parts will be described. FIG. 8 is a diagram for explaining the cooperation of parts on the display screen.
(1) Based on the bindings defined in “Config”, it checks which pane's parameter change event is received and binds a function for redrawing to its own pane.
(2) When selected by a select box in a pane targeted for bindings, a trigger is applied to an event named “pane.event_name” from the pane to which the user belongs.
(3) The bind corresponding to the triggered event is executed.
(4) A redraw function called from bind redraws its own pane.

  Note that events such as parameter changes occur for each part. However, when an event occurs in a part, a trigger is applied in association with the pane name, so that the event notification side (function to be bound) is bound to the pane in advance. Event occurrence is detected on a per-pane basis. Bindings are performed on the pane. The binding event is not the UI component identification information (div_id name) but the pane name + data name. For example, “tab_left.layer_0 (pane name.data name)”. If you want to add a new UI part to the screen example shown in Fig. 8, you can add a part if it can be added inside the pane, or you can add a pane and define the part inside the added pane. Good.

  By adopting the part linkage as shown in FIG. 8, when an operation event occurs in another pane, the part in the own pane is redrawn. Therefore, the screen designer does not need to associate each part. In addition, the number of settings by this association can be reduced.

  FIG. 9 is a diagram illustrating an example of a drive program based on events. FIG. 9 is an example of a program corresponding to (1) and (3) in FIG. The function shown in FIG. 9 is a function for setting driving by an event. In addition, when an event of “pane name + data name” occurs, a setting for calling another function is performed in JavaScript (registered trademark). “Target.on_change ()” is a function called when the bind is executed.

  FIG. 10 is a diagram illustrating an example of an event generation program. FIG. 10 shows a program corresponding to (2) of FIG. The function shown in FIG. 10 is a function that generates an event in the UI component. In line 1001, an event of “pane name + data name” is generated. A function 1003 is a function for setting a value in a variable pane in a DOM (Document Object Model). Thereby, when an operation event occurs in the UI component, a trigger can be generated from the pane to which the UI component belongs. The JavaScript (registered trademark) source shown in FIGS. 9 and 10 is premised on the use of a library called jquery, but this is not restrictive.

  FIG. 11 is a diagram illustrating an example of a program that generates a URL when drawing a UI component. FIG. 11 shows a program corresponding to (4) of FIG. The function shown in FIG. 11 is a function for generating a URL when the browser draws a part. Here, the value set in “panes” in the DOM by “set_param” in FIG. 9 is acquired and set in the URL parameter. The data shown in FIGS. 9 to 10 is stored in the DB 132.

(UI parts setting)
Next, a setting example of UI parts (UI parts) will be described. FIG. 12 is a diagram illustrating an example of definition data of a select box. “Div_id” shown in a line 1201 in FIG. 12 is an ID of a UI part, and the ID indicates an example of “layer_1_select”. “Component” shown in a line 1203 is a UI component name to be used. In this example, the UI component name is “select_box”. “Relative_url” shown in a line 1205 is the URL of the API for acquiring data.

  “Display_fields” shown in a line 1207 is a field name in the data displayed in the select box. “Value_fields” shown in a line 1209 is a field of value data set in the pane when the select box is changed. “Pane” shown in a line 1210 is a pane to which this UI part belongs. In this example, the pane to which it belongs is an example of “tab_left”. A line 1211 is a name when set as a value of the pane, and shows an example of “layer_1”.

  FIG. 13 is a diagram illustrating an example of the select box. FIG. 13 shows an example of a select box for selecting a folder hierarchy. For example, “time” is the first hierarchy, and “HAWB number search” is the second hierarchy. This folder hierarchy will be described later.

  A select box 1301 shown in FIG. 13 is an example when the UI parts shown in FIG. 12 are displayed using a browser. For example, when the pull-down button of the select box is pressed, the PC 103 displays the data in “layer_1” acquired by the API URL of the line 1205 using, for example, Ajax.

  FIG. 14 is a diagram illustrating an example of data acquired by the API. For example, it is assumed that “2009.11”, “2009.12”, “2010.01”, and “2010.02” shown in the data 1401 are acquired. At this time, when the bull-down button shown in FIG. 13 is pressed, “2009.11”, “2009.12”, “2010.01”, and “2010.02” in the data 1401 are displayed on the screen. Note that “layer = layer_1” and “level = 1” indicate the same first layer folder.

  Next, setting examples of other UI parts will be described. FIG. 15 is a diagram illustrating an example of definition data of a folder list. The example shown in FIG. 15 includes a setting for redisplaying the list in response to the display of the folder list and the change of the select box. A variable 1501 is a variable that performs an association in which redrawing is performed by an event of “layer_0” to “stag_15” in the “tab_left” pane. Based on the information of the variable 1501, a function for redrawing is linked to an event by the function shown in FIG. 9, and a search parameter is generated by URL generation shown in FIG.

  FIG. 16 is a diagram illustrating an example of a folder list. A folder list 1601 shown in FIG. 16 is an example in which the UI part definition data shown in FIG. 15 is displayed. For example, when data is selected in the left select box, the folder list shown in FIG. 16 is redrawn accordingly.

(rendering)
Next, an outline of rendering on the PC 103 and rendering on the MFP 101 will be described using the above UI definition data and screen configuration. FIG. 17 is a diagram illustrating an example of rendering. FIG. 17A shows an outline of rendering on the PC 103.

  First, the PC 103 issues a display screen display request. The display request includes identification information indicating a display screen, an IP address of a request source, information of a user who has logged into the PC 103, and the like.

  When the receiving unit 301 of the server 110 receives a display request from the PC 103, the receiving unit 301 outputs the display request to the screen generating unit 305. The screen generation unit 305 determines which UI definition data should be used based on user information, display screen identification information, and the like. Further, the screen generation unit 305 determines which one of the first generation unit 307 and the second generation unit 309 to use from the IP address or the like. Here, it is assumed that the PC 103 can use Ajax that supports asynchronous communication.

  The first generation unit 307 acquires UI definition data on the display screen, and includes the acquired UI definition data, UI component information included in the UI definition data, and a JavaScript (registered trademark) program that uses Ajax. First screen information is generated in HTML format. The first generation unit 307 transmits the generated first screen information to the PC 103 via the transmission unit 303.

  The PC 103 executes a JavaScript (registered trademark) program included in the received HTML-format first screen information, and uses the UI component information to add a UI component to the HTML DOM. The PC 103 renders each UI component using JavaScript (registered trademark) on the browser. For example, in the case of UI parts that require display data, the PC 103 uses Ajax to acquire data from the API at the time of initial drawing or when an event occurs that the value (display data) of another UI part has changed. To do.

  In response to a data acquisition request from the PC 103, the first generation unit 307 of the server 110 searches the DB 132 for data required by the PC 103 by referring to the requested URL and parameters (metadata, hierarchy, etc.) Response data is generated in JSON format.

  When the PC 103 acquires the response data in the JSON format, the PC 103 performs a drawing process so that the acquired data is displayed on the UI component. When display data is required for a plurality of UI parts, the data can be acquired asynchronously by each UI part. The PC 103 repeatedly obtains and draws display data using the above API.

  FIG. 17B shows an outline of rendering in the MFP 101. First, the MFP 101 makes a display screen display request. The display request includes identification information indicating a display screen, an IP address of a request source, information on a user who uses the MFP 101, and the like.

  When receiving unit 301 of server 110 receives a display request from MFP 110, it outputs the display request to screen generation unit 305. The screen generation unit 305 determines which UI definition data should be used based on the user information and the display screen identification information. Further, since the screen generation unit 305 is a request from the MFP 101 that does not support asynchronous communication, the screen generation unit 305 determines to use the second generation unit 309.

  The second generation unit 309 calls a rendering function based on the UI component definition information included in the UI definition data on the display screen, and acquires display data to be displayed on each UI component. The second generation unit 309 searches for display data using UI definition data and parameters (metadata, hierarchy, etc.), and generates second screen information of a screen including UI parts for displaying the display data in the HTML format. At this time, the screen generation unit 309 transmits one page of HTML (second screen information) to the MFP 101. The MFP 101 renders a display screen using the acquired HTML.

  Further, when the display data of the displayed UI component is changed, the MFP 101 makes a display request to the server 110 again if another UI component needs to be redrawn. When the server 110 receives a display request again, the server 110 transmits third page information in HTML format for one page to the MFP 101 in the same manner as the above-described processing.

  Here, an example of view (tab) setting will be described. In an embodiment, each device can also switch views using tabs. FIG. 18 is a diagram illustrating an example of tab setting for a PC. FIG. 18 shows an example of a simple view that displays a “document list”. As shown in FIG. 18, a frame 1801 designates the URL of data for acquiring data to be displayed in this view. Here, it means that data stored in “cabinets / A_project / entries.json” is acquired. “Pane” indicates to which pane it belongs. “Per_page” indicates the number of data to be displayed on one page. In this example, it means that ten documents are displayed on one page.

  FIG. 19 is a diagram showing an example of view setting for the MFP. The type of display data to be acquired is designated in a frame 1901 shown in FIG. In the example illustrated in FIG. 19, a file (“entries”) stored in a folder “A_project” is acquired. A frame 1903 specifies a condition of display data to be acquired. In the example shown in FIG. 19, it means that five files are displayed on one page.

  Next, the relationship between the HTML source and the display screen will be described. FIG. 20 is a diagram illustrating an example of an HTML source for a PC. In a frame 2001 shown in FIG. 20, a JavaScript (registered trademark) program is read. In a frame 2003, UI component display data is embedded. In line 2005 or the like, a common part such as a logout button is defined. A line 2007 or the like is a portion for switching tabs. In a frame 2009, a DIV element in which a UI part is actually installed is defined. For example, the first generation unit 307 generates the screen information illustrated in FIG. 20 and issues an instruction to transmit it to the PC 103. The PC 103 receives screen information as shown in FIG. 20 and draws a display screen based on the received screen information. The screen information illustrated in FIG. 20 is generated by the first generation unit 307. The PC 103 receives screen information as shown in FIG. 20 and draws a display screen based on the received screen information.

  FIG. 21 is a diagram illustrating an example of a PC screen. FIG. 21 shows an example in which the screen information shown in FIG. 20 is drawn. On the screen shown in FIG. 21, “document list” of “title” in the frame 2003 shown in FIG. 20 is displayed, and “document name”, “Size”, and “update date / time” of “disp_fields” are sequentially displayed. Further, as shown in “per_page” in the frame 2003, a maximum of “10” files are displayed on one page.

  Next, FIG. 22 is a diagram illustrating an example of an HTML source for the MFP. A frame 2201 shown in FIG. 22 describes JavaScript (registered trademark) unique to the MFP for the print button. A frame 2203 represents a list of files embedded in HTML. That is, in this example, the document acquired by the frame 1901 shown in FIG. 19 is embedded in the frame 2203 shown in FIG. For example, the second generation unit 309 generates screen information illustrated in FIG. 22 and issues an instruction to transmit it to the MFP 101. The MFP 101 receives screen information as shown in FIG. 22 and draws a display screen based on the received screen information.

  FIG. 23 is a diagram illustrating an example of an MFP screen. FIG. 23 shows an example in which the screen information shown in FIG. 22 is drawn. In the screen shown in FIG. 23, “Title”, “Size”, and buttons in a frame 2203 shown in FIG. 22 are displayed. Further, as shown in a frame 1903 in FIG. 19, a maximum of five files are displayed on one page.

  Next, an example in which the PC 103 acquires display data using an API will be described. FIG. 24 is a diagram illustrating an example of acquiring JSON data and drawing UI components. The PC 103 renders display data acquired from the JSON-format URL at the bottom of FIG. 24 using Ajax on the browser. In the example shown in FIG. 24, the file stored at the position indicated by the URL is displayed. As described above, when data is selected in the select box, the PC 103 in the embodiment uses Ajax to acquire display data in the JSON format and redraws the display screen.

<Operation>
Next, the operation of the screen control system 100 will be described. FIG. 25 is a sequence diagram illustrating an example of login. In step S101 shown in FIG. 25, the PC 103 makes a page request to the server 110 using a browser.

  In step S102, the server 110 redirects to the user management server because the login ticket is not included in the request. In step S103, the user management server transmits a login screen to the PC 103.

  In step S104, the PC 103 transmits information for login to the user management server. The information for logging in includes organization information, user information, a password, and the like.

  In step S <b> 105, when the authentication is successful, the user management server transmits a login ticket to the PC 103 and instructs the PC 103 to redirect to the server 110.

  In step S106, the PC 103 makes a page request to the server 110 together with the login ticket. In step S107, the server 110 confirms the login ticket, and transmits the HTML source (see FIG. 20) of the requested page to the PC 103. Drawing processing by the browser will be described with reference to FIG. The user management server may be included in the server 110.

  FIG. 26 is a sequence diagram illustrating an example of a screen drawing process. In step S <b> 201 shown in FIG. 26, the PC 103 sends a page request including a login ticket to the server 110.

  In step S202, the server 110 transmits the HTML source of the requested page to the PC 103. The HTML source includes definition data for panes and UIs.

  In step S203, the PC 103 requests the server 110 for CSS (Cascading Style Sheets) and JavaScript (registered trademark) described in the header of the HTML source.

  In step S <b> 204, the server 110 transmits the requested CSS and JavaScript (registered trademark) to the PC 103. In step S205, the PC 103 performs screen rendering based on the acquired HTML source, CSS, and JavaScript (registered trademark). UI parts are initialized, and UI parts are drawn. At this time, when there are a plurality of UI parts, drawing is executed asynchronously using Ajax.

  In step S206, when there is display data in the UI component (for example, when a URL is described), the PC 103 requests the display data for the UI component from the server 110. In step S <b> 207, the server 110 generates the requested display data as data in the JSON format and transmits it to the PC 103.

  When acquiring the JSON data from the server 110, the PC 103 executes JavaScript (registered trademark) and redraws the screen.

  With the above configuration, the server 110 can change the generation method of screen information depending on whether or not the device that has requested the page supports asynchronous communication, and can generate screen information suitable for each device in the HTML format. .

<DB structure>
Next, an example of the data structure of data stored in the DB 132 will be described. Hereinafter, the data structure of the DB 132 to be described has a folder hierarchy, and the hierarchy has meaning. Further, it may be assigned to a folder of each hierarchy and metadata related to the meaning of the hierarchy may be assigned.

  By using this data structure, it becomes easy for the server 110 to customize the UI according to each business and to restrict access to the view.

  FIG. 27 is a diagram for explaining the outline of the folder hierarchy. As shown in FIG. 27, the folder hierarchy is defined as “cabinet”, and the hierarchy is defined for each cabinet. For example, the first hierarchy is “customer”, the second hierarchy is “drawing number”, and the third hierarchy is “item”. In addition, metadata related to the definition of the hierarchy can be assigned to the folder of each hierarchy. For example, “business type” and “district” are assigned to the folder of the first hierarchy as metadata related to “customer”, and “product type” is assigned to the folder of the second hierarchy as metadata related to “drawing number”. , “Material”, and “Matter status”, “Delivery date”, and “Number” as metadata related to “Matter” are assigned to the folder of the third hierarchy.

  Document files (documents) are stored in each folder. In addition, a document type is assigned to a document file, and metadata can also be assigned. For example, metadata of “document status” and “delivery status” is assigned to a document file of the document type “estimate”.

  It is also possible to define different levels for each cabinet. Further, each contract account can have a different cabinet. Also, by defining UI parts for each hierarchy, it is easy to generate a display screen according to the hierarchy.

  Next, data related to the folder hierarchy will be described. FIG. 28 is a diagram illustrating an example of a data structure of data related to a folder hierarchy. FIG. 28A shows an example of folder definition information.

  In the example shown in FIG. 28A, folder definition information is assigned to the folder definition information identifier 2800, organization ID 2801, folder hierarchy title, folder hierarchy definition 2802, and folders in each hierarchy, and is related to the definition of the hierarchy. A metadata definition 2803, a metadata definition 2804 assigned to the file, metadata 2805 assigned to the folder, metadata 2806 assigned to the file, and the like are included.

  In the folder hierarchy definition 2802, folders are defined in each hierarchy, and each hierarchy has a meaning. For example, in the folder definition information “2”, “Department name” in layer 1 (layer_0), “Sales person” in layer 2 (layer_1), “Customer name” in layer 3 (layer_2), and Layer 4 (layer_3) "Item name" is defined.

  The metadata definition 2803 assigned to the folder is assigned to each hierarchy, and metadata related to the definition of the hierarchy is defined. For example, in the example shown in FIG. 28A, “stag — 0” is assigned to the hierarchy 4. “Stag_0” indicates “processing state”. This means that metadata indicating a processing state (for example, unprocessed or processed) is assigned to the folder of the hierarchy 4.

  The definition 2804 of metadata attached to the file defines metadata attached to the file stored in the folder. For example, in the example shown in FIG. 28A, “e_stag_0” is added to the file. “E_stag — 0” is metadata indicating “document type”. This means that the file is provided with metadata indicating the document type (for example, quotation, order, etc.).

  The metadata includes metadata “stag (string-tag)” indicating a character string and metadata “dtag (data-tag)” indicating a date. Other metadata may include “ntag (number-tag)” and “btag (boolean-tag)”. Further, the metadata assigned to the folder and the metadata assigned to the file can be identified. Note that metadata assigned to a folder is associated with a file stored in the folder.

  FIG. 28B is a diagram showing an example of folder information. For each folder, folder information is assigned to a folder ID 2820, organization ID 2801, folder definition information identifier 2800, parent folder identifier 28021, level 2822 indicating which hierarchy, data 2823 corresponding to the definition of each hierarchy, and folder. Metadata 2824 corresponding to the definition of the metadata is included.

  Note that each level of folder information may hold data corresponding to a folder definition of a level higher than its own level. For example, “Tokyo headquarters” of “layer_0”, “Wakamoto” of “layer_1”, and “BBB Kogyo” of “layer_2” are held as folder information of the level “2”. As a result, when acquiring data corresponding to the definition of the upper-level folder, it is possible to easily acquire the data without following the parent folder. Further, data corresponding to the definition of the hierarchy may be the name of the folder of the hierarchy.

  The metadata 2824 is data corresponding to “stag — 0” 2805. Since “stag — 0” 2805 defines “processing state”, the metadata 2824 is data indicating the processing state. In the example illustrated in FIG. 28B, the metadata 2824 indicates “processed”.

  FIG. 28C is a diagram showing an example of file information. The file information includes a file ID 2840, an organization ID 2801, a folder ID 2820 indicating in which folder the file is stored, a file title 2841, a URL 2842 indicating the location where the file is stored, a file size 2843, a file metadata 2844, and the like. .

  The file metadata 2844 can be distinguished from the folder metadata 2824. For example, “e_” indicating the file metadata is added to the file metadata 2844, such as “e_stag”. This makes it possible to manage and search the folder metadata and the file metadata separately.

  By having the data structure shown in FIG. 28, it is possible to give meaning to a folder hierarchy and manage files by assigning metadata to folders in that hierarchy. The server 110 can define UI components for each layer, and can customize the UI in a format along the layer. Since a user often generates a folder hierarchy in accordance with the business contents, when a UI is customized in a form along the hierarchy, a UI linked to the business is generated.

  Next, the definition of a hierarchy and an example of metadata will be described. FIG. 29 is a diagram illustrating an example of a hierarchy definition and metadata. FIG. 29A shows the definition of a hierarchy. In the example shown in FIG. 29A, the first hierarchy is defined as “department”, the second hierarchy as “sales representative”, the third hierarchy as “customer name”, and the fourth hierarchy as “case name”. It has been. FIG. 29B is a diagram illustrating the definition of metadata assigned to folders in each hierarchy. In the example shown in FIG. 29B, “state” is defined as metadata in the folder of the fourth hierarchy. Note that metadata such as “location” may be defined in the first layer folder, and “business type” may be defined in the third layer folder.

  FIG. 30 is a diagram showing an example of the data screen shown in FIG. The display screen 3001 includes an area 3003 and an area 3005. In an area 3003, a folder structure described from folder definition information and folder information is drawn. The folder structure of the area 3003 is the folder structure of the identification information “2” of the folder definition information shown in FIG.

  For example, as shown in an area 3003 in FIG. 30, the Tokyo head office (first level), Wakamoto (second level), BBB Kogyo (third level), and instrument parts orders (fourth level) are drawn in hierarchical order. The The folder structure shown in the area 3003 is an example up to the third hierarchy.

  In an area 3005 in FIG. 30, a file structure described from file information is drawn. Referring to FIG. 28C, “quotation sheet.pdf”, “order sheet.pdf”, and “delivery sheet.pdf” are stored in the “instrument part order” folder of folder ID “4”. . As a result, “quotation sheet.pdf”, “order sheet.pdf”, and “delivery sheet.pdf” are drawn in the area 3005.

  In the case of the screen shown in FIG. 30, the first generation means 307 describes a URL indicating the folder storage location for each folder. The PC 103 detects an event by, for example, double-clicking on a folder, acquires display data from a URL corresponding to the double-clicked folder, and redraws the acquired display data in an area 3005. The display data in this case is a document file.

(Views and view sets)
Next, views and view sets will be described. A view set refers to a screen in which one or a plurality of views are grouped and the views in the group can be switched. In the embodiment, by defining a view set, the server 110 can easily switch a view that can be displayed for each department, for example.

  FIG. 31 is a diagram illustrating an example of view set data. As shown in FIG. 31, a view set includes a view set ID (id), an organization ID (organization_id), a URL path name (tiltle) for displaying a tab, a tab name (display_name) for display, and a UI component. Is associated with information (config), view type (view_type), skin (skin), and view order (view_order).

  For example, in the view set ID “2”, the path name “factory” of the URL, the tab name “for factory”, the view type “PC”, the skin “smoothness”, and the order “1, 4” are set. “Skin” is data for emphasizing the difference to the user by changing the color tone of the screen. For example, there are “smoothness” and “normal”. “Smoothness” is a tone that gives a smooth image by changing the brightness and saturation compared to “normal”. Further, common UI components such as a logo and a logout button are defined in “config” of the view set. In “view_order”, view identification information is set in the display order from the left. “*” Of “view_order” is interpreted to indicate all views having the same “view_type”.

  FIG. 32 is a diagram illustrating an example of view (tab) data. As shown in FIG. 32, the data structure of the view is the same as that of the view set. The “config” shown in FIG. 32 is set with, for example, document list definition data as shown in FIG. 15 when displaying a list. Here, “*” of “view_order” illustrated in FIG. 31 is interpreted as indicating the view ID “1, 2, 3, 4” of “PC” having the same “view_type”.

  FIG. 33 is a diagram illustrating an example of data for view formation. FIG. 33A shows data defined to form view set data as shown in FIG. In the example shown in FIG. 33A, data is defined according to the type (string, text, datetime, integer, etc.). For example, “view_type” is a character string format (string), “config” is a text format (text), and “view_order” is an integer format (integer).

  FIG. 33B shows data defined to form view data as shown in FIG. For example, “display_name” is in a character string format (string). As shown in FIG. 33, data is input to each data in a defined format.

FIG. 34 is a diagram for explaining an example of screen switching between the view URL, the view, and the view set. In the example illustrated in FIG. 34, the view set with id “2” of the view set illustrated in FIG. 31 will be described.
(1) When displaying the view set with the id “2” of the view set When the PC 103 displays the URL “https: // host_name / APP_name / view / factory”, for example, the view indicated by “factory” at the end of the URL Display the set. In the view set “factory”, the view id “1” is displayed at the top. In the view id “1”, according to the example shown in FIG. 32, “item list” is displayed.
(2) When displaying the second view of id “2” of the view set When the PC 103 displays the URL “https: // host_name / APP_name / view / factory / drawing”, for example, “drawing” at the end of the URL Is displayed.
(3) When the view set with the id “1” of the view set (display_name = Default) is displayed. When the PC 103 displays the URL “https: // host_name / APP_name / view / all”, for example, the lower part of FIG. A screen like The view set with the view set id “1” can display all views whose “view_type” is “PC”. At this time, the “item list” of “1” having the smallest id number of the view is displayed. Further, when the user presses the “unanswered list” tab, the view id “2” is displayed (see FIG. 32), so the browser of the PC 103 is acquired by the URL “.. ./View/all/to_be_respond”. The displayed display screen is displayed.

  The data structure of the view and view set as described above is saved in the DB 132. For example, even if the company is the same company, a “config” is created for each view (tab) and saved. Different ways of showing and using can be done.

  When receiving the view set display request, the screen generation unit 305 includes the URL of the tab as described above in the first screen information, so that the browser of the PC 103 uses Ajax to transmit each tab by asynchronous communication. Can be acquired.

  FIG. 35 is a diagram for explaining differences in screens due to differences in tabs. FIG. 35A shows an example of a screen displaying a tab for item search. FIG. 35B is an example of a screen that displays a tab for responding to an estimate request. In this way, even if they are the same company, they can be displayed differently (for example, skins) or used differently (number of components) depending on the tab.

  Further, as described with reference to FIG. 31, the server 110 in the embodiment can manage a combination of tabs as a set of views. For example, a tab set for sales department, a tab set for manufacturing department, a tab set for accounting, and the like.

  FIG. 36 is a diagram illustrating a relationship between a view set and a tab. Since FIG. 36A shows the “Advanced” set, all of the “Item” tab, the “Request for quotation request” tab, and the “Order by date of production schedule” tab can be displayed. Since FIG. 36B is a “Simple” set, only the “Item” tab can be displayed, and the item list of the item list is smaller than that in FIG. 36A. This can be achieved by reducing the number of components set in the UI definition data. As described above, UI definition data for each tab, definition data for the view set screen, and the like are stored in the DB 132.

  In the above example, an example of a view or a view set for the PC 103 is shown. However, based on FIG. 17, the server 110 that receives a tab switching request from the MFP 101 generates HTML for one page of the tab after switching. Then, it may be transmitted to the MFP 101. Therefore, the MFP 101 can display the view set stored in the DB 132.

<View restriction>
FIG. 37 is a diagram illustrating an example of account information. In the example shown in FIG. 4, the account information is associated with a user ID 3701, a login name 3703, a password 3705, and a group 3707 assigned to the user. For example, the user ID “1” has a login name “tanabe”. The user ID “3” has a login name “iwata” and belongs to the “managers” group.

  FIG. 38 is a diagram illustrating an example of organization information. In the example shown in FIG. 38, the organization information is associated with an organization ID 3801, an organization name 3803, a display name 3805 indicating the name displayed on the display, a time zone 3807 indicating the location, and a language 3809 indicating the language used. For example, the organization ID “1” is the organization name “CompanyA”, the display name on the display unit is “Company A”, the location is “Tokyo”, and the language used is “Japanese”.

  FIG. 39 is a diagram illustrating an example of user information. In the example shown in FIG. 39, the user ID 3701 is the same identification information as “id” shown in FIG. 37, and the organization ID 3801 is the same identification information as “id” shown in FIG.

  In the example shown in FIG. 39, user information is associated with a user ID 3701, an organization ID 3801, a login name 3901, a tag (first metadata) 3903, a tag (second metadata) 3905, and a group 3907. For example, the user ID “2” is the organization ID “3”, the login name is “wakamoto”, the first metadata “u_stag_0” is the “sales department”, and the second metadata is “ u_stag_1 "is" Saitama Factory ". Thus, metadata can be added to user information.

  The user authentication means 311 collates the login name and password acquired from the apparatus with the login name and password of the account information shown in FIG. If the verifications match, the user authentication unit 311 acquires the organization ID with reference to the user information shown in FIG. 38 based on the user ID, and includes the user ID, organization ID, and metadata in the authentication ticket. In the embodiment, access restriction is added to the view using these pieces of user information.

  FIG. 40 is a diagram illustrating an example of view filter information. 40 are associated with a filter id, an organization id (organization_id), a view set id (view_set_id), a title (title), a description (description), and a condition (user_condition).

  For example, the filter information of id “1” is the organization id “3”, the view set id is “1”, the title is “for administrative department”, and the condition is ““ u_stag_0 ”:“ management section ”. Is. This filter shows that the manager can see all PC views.

The access control unit 313 or the screen generation unit 305 performs view access restriction according to the following procedure.
a) Analyzing the request URL b) Obtaining login user information from the DB c) Obtaining the view set from the DB d) Obtaining the view filter from the DB e) Generating a list of view sets that can be viewed by the logged-in user (view set switching) (For select box)
f) Judgment whether the requested view set can be displayed (an error is returned if not permitted)
g) Acquiring views included in the view set from DB (for view switching tab)
h) Based on the “config” information of the requested view, screen information in HTML format including information on JavaScript (registered trademark) and UI parts is generated and returned to the apparatus.

  The screen generation unit 305 performs the processes a) to c). Next, in d), when the access control unit 313 acquires a view filter based on the login user's metadata, organization information, and the like, the access control unit 313 outputs the id of the view set that can be viewed by the login user to the screen generation unit 305. .

  In e), the screen generation unit 305 generates a view set list based on the view set id acquired from the access control unit 313. The access control unit 313 determines whether the view set of the URL requested in f) can be displayed. For example, the access control means 313 determines that the view set can be displayed if the path name of the URL of the view set of the requested URL matches the path name of the URL corresponding to the id of the acquired view set. . The screen generation means 305 performs the processes g) to h).

  The access control unit 313 can also obtain the view filter of d) first, and obtain a list of views that can be displayed from the DB of the view set under the restriction of the view filter.

  Accordingly, by using the view filter information, it is possible to restrict access to the view set using information related to the user. Information about the user includes user metadata, user organization information, user ID, and the like.

<API>
FIG. 41 is a diagram illustrating an example of an API. FIG. 41 is a diagram illustrating an example of an API (Application Program Interface) used in the server 110. A path 4101 “cabinets / {id} /folders.json” illustrated in FIG. 41 is an API for acquiring a list of folders. An example 4102 is an example of an API that acquires a folder list whose data corresponding to the definition of the layer “2” (second hierarchy) and the layer “0” is “JP”. At this time, the data corresponding to the definition of the hierarchy of layer 2 or higher is displayed in the folder list.

  A path 4103 “cabinets / {id} /layers.json” is an API for acquiring a list of folder names of a specified layer. Example 4104 is an example of an API that acquires a list of folder names of folders of layer “1” (first layer). At this time, for example, “2007.01” and “2007.02” are displayed in the folder name list.

  Note that “layers” is different from “folders” and is unique data. For example, if a folder is created with the name of the person in charge, a folder with the name of the person in charge is created for all years. At this time, if the hierarchy is specified by “folders”, the folder of the same person in charge is displayed many times, but if it is specified by “layers”, the folders of persons in charge of all different persons are displayed.

  A path 4105 “cabinets / {id} /entries.json” is an API for obtaining a file list. Example 4106 is an example of an API for acquiring a file list stored in a folder whose layer name is “00000012344891” of the layer “2” (second layer), and is stored in a folder whose folder ID is “2108”. It is an example of API which acquires the list of files that are stored. At this time, for example, the file ID, position, size, title, and the like are displayed in the file list.

  A path 4107 “cabinets / {id} /tags.json” is an API for acquiring a list of tag candidates. Example 4108 is an example of an API that acquires a list of tags that are candidates for “stag_2”. At this time, the cabinet ID, folder ID, tag name, tag type, and the like are displayed. Using the API shown in FIG. 41, the PC 103 can acquire various data.

  As described above, according to the embodiment, it is possible to appropriately display and control the UI screen corresponding to each device. Further, according to the embodiment, since an event occurrence is detected in units of panes, it is not necessary to associate each UI component. Further, according to the embodiment, by efficiently using view sets and tabs, for example, it is possible to easily switch a view that can be displayed for each department. Further, according to the embodiment, by using the view filter information, it is possible to appropriately limit the access of the view based on the information related to the user.

  Further, if Ajax can be used in the portable terminal, the screen generation unit 305 can generate screen information for mobile as well as for PC. At this time, since the display screen for mobile devices is small, UI components to be displayed may be reduced or items of display data may be reduced.

  The program executed by the server according to the embodiment has a module configuration including the above-described units. As actual hardware, the CPU (processor) reads the program from the storage medium and executes the program. Are loaded on the main memory, and the above-mentioned means are generated on the main memory.

  In addition, this invention is not limited to the said Example as it is, A component can be deform | transformed and embodied in the range which does not deviate from the summary in an implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments.

101 PC
103 MFP
105 Mobile terminal 107 MFP
110 Server 113 Screen Control Unit 115 Interface Unit 119 Metadata Management Unit 121 Screen Data Management Unit 133 DB
301 reception means 303 transmission means 305 screen generation means 307 first generation means 309 second generation means 311 user authentication means 313 access control means

JP 2009-4897A

Claims (9)

A screen control system in which an information processing apparatus, an image forming apparatus, and a server are connected,
The server
First storage means for storing, for each screen, UI definition information in which UI parts of the screen are defined;
Second storage means for storing display data to be displayed on the UI component;
When receiving a screen display request from the information processing apparatus, the UI definition information corresponding to the screen that has received the display request and the display data to be displayed on the UI component included in the UI definition information are acquired by asynchronous communication. First generation means for generating first screen information including a program;
When a screen display request is received from the image forming apparatus, display data to be displayed on a UI component included in UI definition information corresponding to the screen for which the display request has been received is acquired using a rendering function, and the UI component and the UI component Second generation means for generating second screen information for drawing a screen including display data to be displayed on the UI component;
Transmitting means for transmitting the first screen information generated by the first generating means to the information processing apparatus or transmitting the second screen information generated by the second generating means to the image forming apparatus;
A screen control system comprising: The first storage means
Further storing set screen definition information indicating screens in which one or more screens are grouped so as to be switchable;
The first or second generation means includes
2. The screen control system according to claim 1, wherein when the display request for the set screen is received, the screen included in the set screen is selectable and the first or second screen information is generated. The first generation means includes
When receiving an acquisition request for display data to be displayed on a UI component from the information processing apparatus using the API, the requested display data can be searched and the searched display data can be acquired using the API. The screen control system according to claim 1, wherein the screen control system is generated in a data format. The second generation means includes
When a redraw request is received from the image forming apparatus by changing the display data displayed on the UI component, the requested display data is retrieved and a screen including the UI component on which the retrieved display data is displayed is rendered. The screen control system as described in any one of Claims 1 thru | or 3 which produces | generates the 3rd screen information for.   In the screen, one or a plurality of predetermined display areas for displaying the UI parts are set. The display area is a UI of the self display area based on a change in display data of the UI parts in another display area. The screen control system according to any one of claims 1 to 4, wherein the screen control system is defined to redraw display data displayed on a component. The second storage means
Further storing filter information in which user authentication information and metadata including the user's affiliation and location are associated with the metadata and identification information of the set screen;
Access control means for acquiring identification information of a set screen corresponding to the metadata of a logged-in user with reference to the filter information and allowing the user to access a set screen based on the acquired identification information of the set screen The screen control system according to claim 2, further comprising: The second storage means
Folder definition data including a hierarchy definition indicating a definition of each folder hierarchy, and a metadata definition indicating a definition of metadata to be given;
For each folder in the folder hierarchy, folder data including data corresponding to a folder definition above the folder hierarchy, and metadata corresponding to a metadata definition assigned to the folder;
Storing a folder hierarchy in the folder hierarchy and a file associated with the metadata assigned to the folder;
The screen control system according to claim 1, wherein the display data is any one of the folder definition data, the folder data, and the file. A server connected to the information processing apparatus and the image forming apparatus;
First storage means for storing, for each screen, UI definition information in which UI parts of the screen are defined;
Second storage means for storing display data to be displayed on the UI component;
A program for acquiring, by asynchronous communication, UI definition information corresponding to a screen for which a display request has been received and data to be displayed on a UI component included in the UI definition information when a screen display request is received from the information processing apparatus First generation means for generating first screen information including:
When a screen display request is received from the image forming apparatus, display data to be displayed on a UI component included in UI definition information corresponding to the screen for which the display request has been received is acquired using a rendering function, and the UI component and the UI component Second generation means for generating second screen information constituting a screen including display data to be displayed on the UI component;
Transmitting means for transmitting the first screen information generated by the first generating means to the information processing apparatus or transmitting the second screen information generated by the second generating means to the image forming apparatus;
A server comprising A first storage unit that is connected to the information processing apparatus and the image forming apparatus and stores UI definition information in which UI parts of the screen are defined for each screen, and a second storage that stores display data to be displayed on the UI parts. A screen control method in a server comprising storage means,
A program for acquiring, by asynchronous communication, UI definition information corresponding to a screen for which a display request has been received and data to be displayed on a UI component included in the UI definition information when a screen display request is received from the information processing apparatus A first generation step of generating first screen information including:
When a screen display request is received from the image forming apparatus, data to be displayed on the UI component included in the UI definition information corresponding to the screen for which the display request has been received is acquired using a rendering function, and the UI component and the UI A second generation step of generating second screen information constituting a screen including data to be displayed on the component;
Transmitting the first screen information generated by the first generation step to the information processing apparatus, or transmitting the second screen information generated by the second generation step to the image forming apparatus;
A screen control method.

Images