System, method, and program
Patent Information
- Application Number
- JP2022103544
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-06-28
- Publication Date
- 2025-03-14
- Estimated Expiration
- 2042-06-28
Smart Images

Figure 0007645548000001 
Figure 0007645548000002 
Figure 0007645548000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a system, a method, and a program. [Background technology]
[0002] In recent years, technology for linking a plurality of applications has been studied. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] International Publication No. 2021 / 132483 Summary of the Invention [Problem to be solved by the invention]
[0004] Generally, the development of a product that realizes the above-mentioned integration requires detailed investigation of the specifications of each application, which places a heavy burden on the vendor developing the product.
[0005] One of the problems that the present disclosure aims to solve is to provide a system, method, and program that can facilitate the development of a product that realizes collaboration between multiple applications. [Means for solving the problem]
[0006] One example of a system disclosed herein is a system for providing an information processing function based on the collaboration of multiple applications, and includes a first construction unit that constructs, in response to input by an implementer of the information processing function, an event of a first application that triggers the collaboration and steps including an action to be executed by a second application in response to the occurrence of the event, and constructs a flow of information processing to be executed by the multiple applications in the collaboration, and a second construction unit that constructs, in response to input by the implementer, a user screen to be provided to a user of the information processing function, and the first construction unit constructs the events and steps based on first variable data predetermined in association with each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen.
[0007] Another example method of the present disclosure is a method for providing an information processing function based on the collaboration of multiple applications, comprising: a first construction step of constructing, in response to input by an implementer of the information processing function, an event of a first application that triggers the collaboration and a step including an action to be executed by a second application in response to the occurrence of the event, and constructing an information processing flow to be executed by the multiple applications in the collaboration; and a second construction step of constructing, in response to input by the implementer, a user screen to be provided to a user of the information processing function, wherein the first construction step constructs the events and steps based on first variable data predetermined in association with each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen.
[0008] Furthermore, as yet another example of a program of the present disclosure, in order to provide an information processing function based on the collaboration of multiple applications, a program for causing a computer to execute a first construction step of constructing an information processing flow to be executed by the multiple applications in the collaboration, in response to input by an implementer of the information processing function, including an event of a first application that triggers the collaboration and an action to be executed by a second application in response to the occurrence of the event, and a second construction step of constructing a user screen to be provided to a user of the information processing function in response to input by the implementer, wherein the first construction step constructs the events and steps based on first variable data predetermined in association with each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is an exemplary schematic block diagram illustrating a configuration of an information processing system according to an embodiment. [Diagram 2] FIG. 2 is an exemplary schematic block diagram illustrating an example of a usage mode of application cooperation according to the embodiment. [Diagram 3] FIG. 3 is an exemplary schematic flowchart for explaining a procedure for establishing application linkage according to the embodiment. [Figure 4] FIG. 4 is an exemplary schematic diagram for explaining a solution editor according to the embodiment. [Diagram 5] FIG. 5 is an exemplary schematic diagram for explaining a trigger according to an embodiment. [Figure 6] FIG. 6 is an exemplary schematic diagram for explaining the addition of a step according to the embodiment. [Figure 7] FIG. 7 is an exemplary schematic diagram for explaining the first variable according to the embodiment. [Figure 8]FIG. 8 is an exemplary schematic diagram for explaining a second variable according to the embodiment. [Figure 9] FIG. 9 is an exemplary schematic diagram for explaining the creation of a second variable according to the embodiment. [Figure 10] FIG. 10 is an exemplary schematic diagram for explaining setting of an action using a second variable according to the embodiment. [Figure 11] FIG. 11 is an exemplary schematic diagram for explaining the wizard editor according to the embodiment. [Figure 12] FIG. 12 is an exemplary schematic diagram for explaining a method of arranging an interface for performing authentication settings for an application used in a solution and an interface for receiving input of a second variable on a screen according to an embodiment. [Figure 13] FIG. 13 is an exemplary schematic diagram for explaining a method for specifying an input format of a second variable according to an embodiment. [Figure 14] FIG. 14 is an exemplary schematic diagram for explaining an example of an assist as an example of an input format of a second variable that can be specified in the embodiment. [Figure 15] FIG. 15 is an exemplary schematic diagram for explaining an outline of a method for setting the assist shown in FIG. [Figure 16] FIG. 16 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG. [Figure 17] FIG. 17 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG. [Figure 18] FIG. 18 is an exemplary schematic diagram for explaining an outline of a method for setting an assist that is different from the example shown in FIG. [Figure 19] FIG. 19 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG. [Figure 20]FIG. 20 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG. [Figure 21] FIG. 21 is an exemplary schematic diagram showing a check box as another example of an input format for a second variable that can be specified in the embodiment. [Figure 22] FIG. 22 is an exemplary schematic block diagram illustrating a hardware configuration of a computer that constitutes the information processing device according to the embodiment. [Diagram 23] FIG. 23 is an exemplary schematic block diagram showing an example of a usage mode of application cooperation according to the modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, embodiments (and modifications) of the present disclosure will be described with reference to the drawings. The configurations of the embodiments described below, and the actions and effects brought about by the configurations, are merely examples and are not limited to the contents described below.
[0011] In addition, in this disclosure, ordinal numbers such as "first" and "second" are used as necessary, but these ordinal numbers are used for convenience of identification and do not indicate any particular priority order.
[0012] <Embodiment> FIG. 1 is an exemplary schematic block diagram illustrating a configuration of an information processing system according to an embodiment.
[0013] 1, an information processing system according to an embodiment includes a server device 100. The server device 100 is configured to provide an information processing function based on the cooperation of a plurality of SaaS (Software as a Service) applications 200 (hereinafter referred to as application cooperation) in response to an input from an information processing device 50 of a vendor that provides products to general organizations such as companies. The server device 100 is an example of a "system" in the present disclosure.
[0014] The server device 100 has a solution construction unit 101, a wizard construction unit 102, and a display processing unit 103 as functions for providing application linkage. The solution construction unit 101 is an example of a "first construction unit" in the present disclosure, and the wizard construction unit 102 is an example of a "second construction unit" in the present disclosure. Details of each of these functions will be described later.
[0015] In the embodiment, the vendor incorporates a function for executing application linkage according to the end user's request into the vendor product provided to the end user by inputting various information into the server device 100 in response to the request from the end user in the general organization. Such application linkage is used by the end user in the manner shown in FIG. 2, for example.
[0016] FIG. 2 is an exemplary schematic block diagram illustrating an example of a usage mode of application cooperation according to the embodiment.
[0017] 2, a vendor product 212 incorporating a function for executing the above-mentioned application linkage is installed in an information processing device 211 of an end-user system 210. This allows an end user to obtain the benefits of application linkage by using the vendor product 212.
[0018] Application integration can be achieved, for example, by following the steps shown in Figure 3.
[0019] FIG. 3 is an exemplary schematic flowchart for explaining a procedure for establishing application linkage according to the embodiment.
[0020] 3, in the embodiment, first, in S301, the server device 100 constructs a solution indicating the content of application cooperation to be provided to the end user, such as a specific event occurring in one application being a trigger to cause another application to execute a specific action, in response to an input from an implementer of application cooperation (vendor engineer). Specific examples of the solution will be described later, so further description will be omitted here.
[0021] Then, in S302, the server device 100 constructs a wizard as a screen interface (user screen) to be provided to an end user who is a user of the solution constructed in the above S301, in response to an input from an implementer of application linkage.
[0022] The solution and wizard constructed in the above-mentioned processes of S301 and S302, respectively, are incorporated into the vendor product 212 by an implementer of the application integration, thereby providing the application integration to the end user.
[0023] Here, the process of S301 described above is executed by the solution construction unit 101 (see FIG. 1) of the server device 100. That is, in response to an input by an implementer of application cooperation, the solution construction unit 101 constructs an event of a first application that triggers cooperation, and steps including an action to be executed by a second application in response to the occurrence of the event. Then, the solution construction unit 101 constructs a flow of information processing to be executed by multiple applications in the cooperation.
[0024] The process of S302 described above is executed by the wizard construction unit 102 (see FIG. 1) of the server device 100. That is, the wizard construction unit 102 constructs a user screen to be provided to an end user, who is a user of the application cooperation, in response to an input by an implementer of the application cooperation.
[0025] The display processing unit 103 (see FIG. 1) of the server device 100 is a function that provides a screen that accepts input (operation input) by an implementer for constructing the above-mentioned solution and wizard. For example, the display processing unit 103 outputs a solution editor as shown in the following FIG. 4 as a first construction screen that accepts input by an implementer for constructing a solution.
[0026] FIG. 4 is an exemplary schematic diagram for explaining a solution editor according to the embodiment.
[0027] 4 is an example of an image output as a solution editor by the display processing unit 103. The image 400 includes three areas 410, 420, and 430.
[0028] Area 410 is the first area for setting an event that will be a trigger for collaboration and steps to be executed in response to the trigger. The implementer can set events and steps by setting (selecting or inputting) each item in this area 410.
[0029] For example, in the area 410 shown in Fig. 4, a step is set to execute an action "send message" in an application "SaaS_A". Also, in the area 410 shown in Fig. 4, a variable "channel" indicating the destination to which the message is to be sent and a variable "record|Step 3" indicating the contents of the message to be sent are set in the "settings" column as variable data (hereinafter simply referred to as variables) referenced in relation to the action "send message". Here, the variable "channel" is a variable that is determined in advance in relation to an application "SaaS_A", for example, and the variable "record|Step 3" is a variable for reference to the result of the third process in the flow diagram displayed in the area 420 described next.
[0030] Area 420 is a second area for displaying a flow diagram showing the flow of information processing including events and steps constructed according to the input received by area 410. By selecting each step in area 420, the implementer can display the setting items for that step in area 410.
[0031] Area 430 is an area for displaying variables available for setting events and steps using the solution editor. In the embodiment, two types of variables are used: a first variable that is predetermined according to the application, and a second variable that is arbitrarily defined by the implementer to receive input by the end user via the above-mentioned wizard (user screen). Details of these variables will be described later, so further description will be omitted here.
[0032] In the example shown in Fig. 4, the contents of the step are set in area 410, but not only the step but also the event that will be the trigger for the link can be set in area 410. When setting an event, area 410 will have a form such as the example shown in Fig. 5 below.
[0033] FIG. 5 is an exemplary schematic diagram for explaining a trigger according to an embodiment.
[0034] 5 is an example of the area 410 when setting an event that will be a trigger for collaboration. The image 500 includes a plurality of areas 510, 520, 530, and 540.
[0035] Area 510 is an area where an application to be set is displayed. The implementer can switch between displaying and hiding an interface for selecting an application to be set by operating button 511. Area 520 is an area where an outline of an event that will trigger the linkage is displayed. The implementer can switch between displaying and hiding an interface for selecting an outline of an event that will trigger the linkage by operating button 521. Area 530 is an area where setting items related to an event that will trigger the linkage are displayed. The implementer can switch between displaying and hiding an interface for setting the setting items in detail by operating button 531.
[0036] Moreover, the area 540 is an area where the contents that limit the trigger condition of the event displayed in the area 520 are displayed. The implementer can switch between displaying and hiding the interface for limiting the trigger condition of the event displayed in the area 520 by operating the button 541. For example, the area 540 shown in FIG. 5 has a limitation set such that when the value of the variable "Is Folder|Step 1" becomes "equal" to "False", that is, when a folder is not created in the first process in the flow of information processing shown in the area where the corresponding flow diagram is displayed, such as the above-mentioned area 420 (= when a file is created instead of a folder). The implementer can further add contents that limit the trigger condition of the event displayed in the area 520 by operating the button 542.
[0037] In the embodiment, the step to be set can be added via area 420, as shown in FIG.
[0038] FIG. 6 is an exemplary schematic diagram for explaining the addition of a step according to the embodiment.
[0039] 6 includes an area 610 displaying a step "Post a message," and buttons 621, 622, and 623 for determining the next processing flow of the step. Button 621 is a button for setting a step that causes an application to execute some action after the step displayed in area 610. Button 622 is a button for setting a branch after the step displayed in area 610, and button 623 is a button for setting a loop after the step displayed in area 610.
[0040] As mentioned above, area 430 is an area for displaying variables that can be used to set events and steps using the solution editor, and the variables are of two types: first variables that are predetermined according to the application, and second variables that are arbitrarily defined by the implementer.
[0041] The first variable predetermined depending on the application is, for example, as shown in FIG.
[0042] FIG. 7 is an exemplary schematic diagram for explaining the first variable according to the embodiment.
[0043] 7 includes an area 410 and a third area 430. Area 410 includes an area 710 in which an application to be set is displayed, an area 720 in which an action to be executed by the application displayed in area 710 is displayed, and an area 730 in which setting items related to the action displayed in area 720 are displayed.
[0044] Items such as "File", "Upload Folder ID", "File Name", and "MIME Type" displayed in area 730 are first variables determined in advance according to the application displayed in area 710. When setting these first variables, the third area 430 can be used.
[0045] 7 includes an area 750 in which a list of first variables predetermined according to the application displayed in area 710 is displayed. In this area 750, a plurality of first variables such as "file name" that can be referenced when setting an action via area 410 is displayed together with their respective types (e.g., "ABC" indicating a character string). The implementer can reflect a first variable selected from this area 750 in area 730 of area 410.
[0046] On the other hand, the second variables arbitrarily defined by the implementer are as shown in the following FIGS.
[0047] FIG. 8 is an exemplary schematic diagram for explaining a second variable according to the embodiment.
[0048] An image 800 shown in Fig. 8 is an example of the third area 430 in which an "end user variable" is displayed as a second variable. By operating a button 810 in this image 800, the implementer can additionally define (create) a second variable via an interface as shown in the following Fig. 9.
[0049] FIG. 9 is an exemplary schematic diagram for explaining the creation of a second variable according to the embodiment.
[0050] 9 includes an area 901 for receiving input of the name of a second variable, and a selection interface 902 in which a list of selectable types of the second variable is displayed. An implementer can create a second variable by inputting an arbitrary name in the area 901 and then selecting the type in the selection interface 902. The second variable created in this way is used to set a step via a solution editor, for example, in the form shown in the following FIG. 10.
[0051] FIG. 10 is an exemplary schematic diagram for explaining setting of a step using a second variable according to the embodiment.
[0052] An image 1000 shown in Fig. 10 includes an area 410 and a third area 430. In the example shown in Fig. 10, a second variable created via the image 900 shown in Fig. 9 is displayed in the third area 430. The implementer can use the second variable displayed in the third area 430 as one of the setting items of the step in the area 410.
[0053] As described above, the display processing unit 103 has not only the function of providing a screen for accepting inputs from an implementer for constructing a solution, but also the function of providing a screen for accepting inputs from an implementer for constructing a wizard. For example, the display processing unit 103 outputs a wizard editor as shown in the following Fig. 11 as a second construction screen for accepting inputs from an implementer for constructing a wizard.
[0054] FIG. 11 is an exemplary schematic diagram for explaining the wizard editor according to the embodiment.
[0055] 11 is an example of an image output by the display processing unit 103 as a wizard editor. The image 1100 includes four areas 1110, 1120, 1130, and 1140. The image 1100 also includes a button 1101 for switching the wizard editor to the above-mentioned solution editor.
[0056] Areas 1120, 1130, and 1140 are a fourth area that accepts input from the implementer regarding the screen design of the wizard, and area 1110 is a fifth area that displays screen 1111 as an image that constitutes the wizard constructed in response to the input accepted by these areas 1120, 1130, and 1140.
[0057] For example, in the example shown in FIG. 11, area 1120 is an area (right pane) for inputting setting items for screen 111, such as a title to be displayed on screen 1111. Area 1130 is an area (left pane) for displaying setting items for screen 1111. Area 1130 includes a button 1131 for creating a new screen other than screen 1111. Area 1140 is an area for displaying setting items for an end user. For example, area 1140 is used to set on which screen an interface for setting authentication for an application used in the solution and an interface for accepting input of a second variable by an end user are to be placed, as shown in the following FIG. 12.
[0058] FIG. 12 is an exemplary schematic diagram for explaining a method of arranging an interface for performing authentication settings for an application used in a solution and an interface for receiving input of a second variable on a screen according to an embodiment.
[0059] Image 1200 shown in FIG. 12 is an example of area 1140 that displays setting items for an end user. Applications used in a solution are displayed in this image 1200. By operating buttons 1211 and 1221, the implementer can set on which screen in the wizard the authentication settings for the corresponding application are to be placed. In addition, a list of predefined second variables is also displayed in this image 1200. By operating buttons 1212 and 1222, the implementer can set on which screen in the wizard the second variables are to be placed.
[0060] Here, in an embodiment, as shown in Figures 13 to 21 below, when an interface that accepts input of a second variable by an end user is placed on a screen, it is possible to specify the input format in which the end user is to input the second variable.
[0061] FIG. 13 is an exemplary schematic diagram for explaining a method for specifying an input format of a second variable according to an embodiment.
[0062] In image 1300 shown in Fig. 13, area 1120 includes area 1320 as a sixth area for selectively specifying the input format of a second variable called "end user variable A" on screen 1311 from among a plurality of predetermined input formats. In area 1320 shown in Fig. 13, as an example, an input format called "select" is specified for allowing the end user to select data to be input as the second variable from among fixed options.
[0063] In addition, in the embodiment, in addition to the above-mentioned input format "select", many other input formats can be specified. For example, in the embodiment, as a characteristic input format other than "select", an input format "assist" as shown in the following FIG. 14 can be specified.
[0064] FIG. 14 is an exemplary schematic diagram for explaining an example of an assist as an example of an input format of a second variable that can be specified in the embodiment.
[0065] Image 1400 shown in Fig. 14 includes an area 1410 that presents options according to the above-mentioned "Assist" setting. Unlike the above-mentioned "Select," "Assist" is an input format that allows the end user to select data to be input as a second variable from dynamic options according to the application, rather than from fixed options. Such "Assist" can be set, for example, in the manner shown in Figs. 15 to 17 below.
[0066] FIG. 15 is an exemplary schematic diagram for explaining an outline of a method for setting the assist shown in FIG.
[0067] 15 shows an example of the sixth region when "assist" is selected as the input format. In this image 1500, an interface 1510 is displayed for selecting what kind of "assist" is to be provided, that is, which application and which data is to be referenced to present dynamic options.
[0068] 15, an option called "Spreadsheet Sheet List" is one of the options displayed on interface 1510. Generally, the sheets of a spreadsheet depend on a parent spreadsheet (also called a workbook), so in order to present a list of sheets by "assist," it is necessary to specify the parent spreadsheet from which the list of sheets is to be obtained, as shown in the following FIG.
[0069] FIG. 16 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG.
[0070] An image 1600 shown in Fig. 16 is an image that is displayed when "Spreadsheet Sheet List" is selected in the interface 1510 of the above image 1500. This image 1600 includes an area 1610 for specifying a parent spreadsheet from which to obtain a list of sheets. In this area 1610, the parent spreadsheet is specified, for example, in the form shown in the following Fig. 17.
[0071] FIG. 17 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG.
[0072] 17 shows an image 1700 that is displayed when the second variable "Spreadsheet" placed on "Screen 1" in the above image 1600 is specified as the parent spreadsheet. When "Assist" of "Spreadsheet Sheet List" is set for the second variable "Spreadsheet", a list of sheets included in the spreadsheet is displayed as options in response to information about the spreadsheet being input by the end user via the wizard.
[0073] It should be noted that the assist that can be set in the embodiment is not limited to the example shown in FIG.
[0074] FIG. 18 is an exemplary schematic diagram for explaining an outline of a method for setting an assist that is different from the example shown in FIG.
[0075] An image 1800 shown in Fig. 18 is an example of the sixth area when "assist" is selected as the input format, which is different from Fig. 14. This image 1800 includes an interface 1810 in which an option "folder list" is displayed as one of the options for configurable assist.
[0076] Here, when selecting a target folder from among a large number of folders, convenience would be improved if it were possible to provide assistance (which could be described as selection assistance, for example) in which, rather than having to select from all of the large number of folders, the user only needs to input part of the string indicating the name of the target folder (whether it is a forward match, partial match, or backward match) and a list of folders having folder names containing the input string is displayed.
[0077] Therefore, in the embodiment, the above selection assist is realized by using an option of "folder list" displayed in the interface 1810 shown in Fig. 18. The selection assist is realized, for example, in the form shown in Fig. 19 and Fig. 20 below. The examples shown in Fig. 19 and Fig. 20 below are examples of selection assist for a second variable called "SaaS_B folder".
[0078] FIG. 19 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG.
[0079] 19 includes an interface 1910 including an area 1911 that accepts an input of a folder name by an end user, and an area 1912 that displays a list of candidates for the folder name. According to the above-mentioned selection assist, by simply inputting a part of a desired folder name in area 1911, the candidates displayed in area 1912 can be narrowed down as shown in the following FIG.
[0080] FIG. 20 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG.
[0081] Image 2000 shown in Fig. 20 corresponds to the case where "1" is entered in area 1911 in image 1900 shown in Fig. 19. Therefore, in the example shown in Fig. 20, the only folder name candidates displayed in area 1912 are "Assist 10" and "Assist 1," which contain the character "1" entered in area 1911. In this way, selection assist can reduce the effort required to select (enter) a target folder, improving convenience.
[0082] In addition, in the embodiment, as an input format of a second variable different from the above-mentioned "select" and "assist", an input format of "check box" as shown in the following FIG. 21 can also be specified.
[0083] FIG. 21 is an exemplary schematic diagram showing a check box as another example of an input format for a second variable that can be specified in the embodiment.
[0084] 21 is an example of an image output when setting an input format called "checkbox" in the wizard editor. In this image 2100, a screen 2111 including an interface 2112 that presents options in a checkbox format is displayed in an area 1110, and an image 2120 including interfaces 2121, 2122, and 2123 for setting the display contents of the screen 2111 is displayed in an area 2120. The interface 2121 is for specifying the input format called "checkbox," and the interfaces 2122 and 2123 are for inputting options to be presented on the screen 2111 in a checkbox format.
[0085] When the settings of the solution and the wizard are completed as described above, the implementer tests whether or not the settings are correct as intended. Then, the implementer deploys the solution and the wizard after confirming that the settings are correct as intended.
[0086] As described above, the server device 100 according to the embodiment is configured to provide application cooperation as an information processing function based on cooperation between a plurality of SaaS applications 200. The server device 100 has a solution construction unit 101 as a first construction unit and a wizard construction unit 102 as a second construction unit. The solution construction unit 101 constructs an event of a first application that triggers cooperation and a step including an action to be executed by a second application in response to the occurrence of the event, in response to an input by an implementer of application cooperation, and constructs a flow of information processing to be executed by a plurality of applications in the cooperation. In addition, the wizard construction unit 102 constructs a wizard as a user screen to be provided to a user of the application cooperation in response to an input by the implementer.
[0087] Here, in the embodiment, the solution construction unit 101 constructs events and steps based on first variables that are predetermined in relation to each of the multiple applications and second variables that are arbitrarily defined by the implementer to receive user input via a wizard. With this configuration, it is possible to facilitate development of a product that realizes cooperation between multiple applications using the server device 100. At this time, not only the predetermined first variables but also the second variables that are arbitrarily defined by the implementer can be used, thereby increasing the flexibility of development.
[0088] Finally, the hardware configuration of the server device 100 (see FIG. 1) according to the above-mentioned embodiment will be described. The server device 100 according to the embodiment is configured as a computer 2200 having a hardware configuration as shown in the following FIG.
[0089] FIG. 22 is an exemplary schematic block diagram showing a hardware configuration of a computer 2200 constituting the server apparatus 100 according to the embodiment.
[0090] 22, a computer 2200 includes a processor 2210, a memory 2220, a storage 2230, an input / output interface (I / F) 2240, and a communication interface (I / F) 2250. These hardware components are connected to a bus 2260.
[0091] The processor 2210 is configured as, for example, a CPU (Central Processing Unit), and controls the overall operation of each part of the computer 2200 .
[0092] Memory 2220 includes, for example, Read Only Memory (ROM) and Random Access Memory (RAM), and provides volatile or non-volatile storage of various data such as programs executed by processor 2210, and provides a working area for processor 2210 to execute programs.
[0093] The storage 2230 includes, for example, a hard disk drive (HDD) or a solid state drive (SSD), and stores various types of data in a non-volatile manner.
[0094] The input / output interface 2240 controls the input of data to the computer 2200 from input devices (not shown) such as a keyboard and mouse, and the output of data from the computer 2200 to output devices (not shown) such as a display and speakers.
[0095] Communications interface 2250 enables computer 2200 to communicate with other devices.
[0096] The functional configuration (see FIG. 1) of the server device 100 according to the embodiment is realized as a group of functional modules by cooperation between hardware and software as a result of the processor 2210 executing a program pre-stored in the memory 2220 or the storage 2230. However, in the embodiment, some or all of the group of functional modules shown in FIG. 1 may be realized only by hardware such as a dedicated circuit.
[0097] It should be noted that the above-mentioned programs do not necessarily need to be stored in advance in the memory 2220 or the storage 2230. For example, the above-mentioned programs may be provided as a computer program product recorded in an installable or executable format on a computer-readable medium, such as various magnetic disks such as a flexible disk (FD) or various optical disks such as a digital versatile disk (DVD).
[0098] The above-mentioned program may be provided or distributed via a network such as the Internet. In other words, the above-mentioned program may be provided in a state where it is stored on a computer connected to a network such as the Internet and is available for download via the network.
[0099] <Modification> In the above-described embodiment, a configuration is exemplified in which the function for realizing application linkage is incorporated in the vendor product 212 (see FIG. 2). However, as a modified example, a configuration in which the function for realizing application linkage is provided in a hosting format as shown in the following FIG. 23 is also conceivable.
[0100] FIG. 23 is an exemplary schematic block diagram showing an example of a usage mode of application cooperation according to the modified example.
[0101] 23, a function for realizing application cooperation constructed in the same procedure as in the above-described embodiment is installed in the hosting server 2310, not in a vendor product (not shown) of the end-user's information processing device 2320. In this case, the hosting server 2310 can provide each function of application cooperation as a web service. This allows an implementer on the end-user's side to use each function of application cooperation in a web application-like manner by accessing the hosting server 2310 using the information processing device 2320.
[0102] Although the embodiments and modifications of the present disclosure have been described above, these embodiments and modifications are presented as examples and are not intended to limit the scope of the invention. These new embodiments and modifications can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]
[0103] 101 Solution Construction Department (First Construction Department) 102 Wizard Construction Section (Second Construction Section) 103 Display processing unit
Claims
1. A system for supporting implementers in incorporating information processing functions based on the collaboration of multiple applications into products for users, comprising: a first construction unit that constructs a step including an event of a first application that triggers the cooperation in response to an input by an implementer of the information processing function and an action to be executed by a second application in response to the occurrence of the event, and constructs a flow of information processing to be executed by the plurality of applications in the cooperation; a second construction unit that constructs a user screen to be provided to a user of the information processing function in response to an input by the implementer; a display processing unit that outputs a first construction screen including a first area that receives input from the implementer regarding construction of the events and the steps, and a second area that displays a flow diagram showing a flow of the information processing including the events and the steps constructed in response to the input received in the first area; Equipped with the first construction unit constructs the events and the steps based on first variable data predetermined in association with each of the plurality of applications and second variable data arbitrarily defined by the implementer to receive input from the user via the user screen; the first construction unit constructs the events and the steps in response to an input by the implementer via the first construction screen; the display processing unit further outputs a second construction screen including a fourth area for receiving input from the implementer regarding a screen design of the user screen, and a fifth area for displaying the user screen constructed in response to the input received in the fourth area; the second construction unit constructs the user screen in response to an input by the implementer via the second construction screen, The fourth area includes a sixth area for selectively specifying the input format of the second variable data in an input interface provided on the user screen to accept input of the second variable data by the user from among a plurality of predetermined input formats.
2. the first construction screen further includes a third area for defining the second variable data in response to an input by the implementer; The system of claim 1 .
3. the third region includes a selection interface for allowing the implementer to select a type of the second variable data from a plurality of preset types; The system of claim 2.
4. A method for supporting an implementer in incorporating an information processing function based on cooperation of a plurality of applications into a product for users, comprising: a step including an event of a first application that triggers the linkage in response to an input by an implementer of the information processing function, and an action to be executed by a second application in response to the occurrence of the event, and a first construction step of constructing an information processing flow to be executed by the plurality of applications in the linkage; a second construction step of constructing, by the computer, a user screen to be provided to a user of the information processing function in response to an input by the implementer; a display processing step of outputting, by the computer, a first construction screen including a first area for receiving an input from the implementer regarding construction of the events and the steps, and a second area for displaying a flow diagram showing a flow of the information processing including the events and the steps constructed in response to the input received in the first area; Equipped with The first construction step constructs, by the computer, the events and the steps based on first variable data predetermined in association with each of the plurality of applications and second variable data arbitrarily defined by the implementer to receive input from the user via the user screen; The first construction step includes constructing, by the computer, the events and the steps in response to an input by the implementer via the first construction screen; The display processing step further includes outputting, by the computer, a second construction screen including a fourth area for receiving input from the implementer regarding a screen design of the user screen, and a fifth area for displaying the user screen constructed in response to the input received in the fourth area; The second construction step comprises constructing the user screen by the computer in response to an input by the implementer via the second construction screen; The method, wherein the fourth area includes a sixth area for selectively specifying an input format of the second variable data in an input interface provided on the user screen to accept input of the second variable data by the user from among a plurality of predetermined input formats.
5. To help implementers incorporate information processing functions based on the collaboration of multiple applications into products for users, a step including an event of a first application that triggers the linkage in response to an input by an implementer of the information processing function, and an action to be executed by a second application in response to the occurrence of the event; and a first construction step of constructing a flow of information processing to be executed by the plurality of applications in the linkage; a second construction step of constructing a user screen to be provided to a user of the information processing function in response to an input by the implementer; a display processing step of outputting a first construction screen including a first area for receiving an input from the implementer regarding construction of the events and the steps, and a second area for displaying a flow diagram showing a flow of the information processing including the events and the steps constructed in response to the input received in the first area; A program for causing a computer to execute the above, The first construction step constructs the events and the steps based on first variable data predetermined in relation to each of the plurality of applications and second variable data arbitrarily defined by the implementer to receive input from the user via the user screen; The first construction step constructs the events and the steps in response to an input by the implementer via the first construction screen; the display processing step further includes outputting a second construction screen including a fourth area for receiving input from the implementer regarding a screen design of the user screen, and a fifth area for displaying the user screen constructed in response to the input received in the fourth area; The second construction step constructs the user screen in response to an input by the implementer via the second construction screen, The fourth area includes a sixth area for selectively specifying the input format of the second variable data in an input interface provided on the user screen to accept input of the second variable data by the user from among a plurality of predetermined input formats.
Citation Information
Patent Citations
Information processing apparatus, server, processing method thereof, and program
JP2018010628A
Application linkage method, computer program, and application linkage system
WO2021132483A1