JP7645548B2 - System, method, and program - Google Patents

Description

This disclosure relates to a system, a method, and a program.

In recent years, technology that allows multiple applications to work together has been under study.

International Publication No. 2021/132483

In general, the development of a product that achieves the above-mentioned integration requires detailed investigation of the specifications of each application, which places a heavy burden on the vendor developing the product.

One of the problems that this disclosure aims to solve is to provide a system, method, and program that can facilitate the development of products that realize the integration of multiple applications.

A system as an example of the present disclosure 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 relation to each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen.

Another example of a method disclosed herein is a method for providing an information processing function based on the collaboration of multiple applications, comprising: a first creation step of creating a flow of information processing to be performed by the multiple applications in the collaboration in response to input by an implementer of the information processing function, the first creation step creating an event of a first application that triggers the collaboration and a step including an action to be performed by a second application in response to the occurrence of the event; and a second creation step of creating a user screen to be provided to a user of the information processing function in response to input by the implementer, the first creation step creating the event and the step based on first variable data predetermined in relation to each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen.

In addition, a further example of a program of the present disclosure is a program for causing a computer to execute a first construction step of constructing a flow of information processing to be executed by the multiple applications in the cooperation in response to input by an implementer of the information processing function, the first construction step constructing a step including an event of a first application that triggers the cooperation and an action to be executed by a second application in response to the occurrence of the event, in order to provide an information processing function based on the cooperation of multiple applications, 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, the first construction step constructing the events and steps based on first variable data predetermined in relation to each of the multiple applications and second variable data arbitrarily defined by the implementer to receive user input via the user screen.

FIG. 1 is an exemplary schematic block diagram illustrating a configuration of an information processing system according to an embodiment. FIG. 2 is an exemplary schematic block diagram illustrating an example of a usage mode of application cooperation according to the embodiment. FIG. 3 is an exemplary schematic flowchart for explaining a procedure for establishing application linkage according to the embodiment. FIG. 4 is an exemplary schematic diagram for explaining a solution editor according to an embodiment. FIG. 5 is an exemplary schematic diagram for explaining a trigger according to an embodiment. FIG. 6 is an exemplary schematic diagram for explaining the addition of a step according to the embodiment. FIG. 7 is an exemplary schematic diagram for explaining a first variable according to the embodiment. FIG. 8 is an exemplary schematic diagram for explaining a second variable according to the embodiment. FIG. 9 is an exemplary schematic diagram for explaining the creation of a second variable according to the embodiment. FIG. 10 is an exemplary schematic diagram for explaining the setting of an action using a second variable according to the embodiment. FIG. 11 is an exemplary schematic diagram for explaining the wizard editor according to the embodiment. 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. FIG. 13 is an exemplary schematic diagram for explaining a method for specifying the input format of a second variable according to an embodiment. 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. FIG. 15 is an exemplary schematic diagram for explaining an outline of a method for setting the assist shown in FIG. FIG. 16 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG. 14. In FIG. FIG. 17 is an exemplary schematic diagram for explaining details of the method for setting the assist shown in FIG. 14. In FIG. FIG. 18 is an exemplary schematic diagram for explaining an outline of a method for setting the assist that is different from the example shown in FIG. FIG. 19 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG. FIG. 20 is an exemplary schematic diagram for explaining the assist achieved through the example shown in FIG. 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. FIG. 22 is an exemplary schematic block diagram illustrating a hardware configuration of a computer that constitutes the information processing apparatus according to the embodiment. FIG. 23 is an exemplary schematic block diagram showing an example of a usage mode of application cooperation according to the modified example.

Embodiments (and variations) of the present disclosure will be described below with reference to the drawings. The configurations of the embodiments described below, as well as the actions and effects brought about by said configurations, are merely examples and are not limited to the contents described below.

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.

<Embodiment>
FIG. 1 is an exemplary schematic block diagram for explaining a configuration of an information processing system according to an embodiment.

As shown in FIG. 1, the information processing system according to the embodiment includes a server device 100. The server device 100 is configured to provide information processing functions based on the collaboration of multiple SaaS (Software as a Service) applications 200 (hereinafter referred to as application collaboration) 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" of the present disclosure.

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 integration. 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.

In an embodiment, the vendor incorporates a function for executing application integration 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 within the general organization. Such application integration is used by the end user in a manner such as that shown in the following Figure 2.

Figure 2 is an exemplary schematic block diagram showing an example of how application collaboration is used in an embodiment.

In the example shown in FIG. 2, a vendor product 212 incorporating a function for executing the above-mentioned application integration is installed in the information processing device 211 of the end-user system 210. This allows the end user to obtain the benefits of application integration by using the vendor product 212.

Application integration is established, for example, by following the steps shown in Figure 3 below.

Figure 3 is an exemplary schematic flowchart for explaining the procedure for establishing application integration according to an embodiment.

As shown in FIG. 3, in this embodiment, first, in S301, the server device 100 creates a solution that indicates the content of the application integration to be provided to the end user, such as causing a specific action to be executed in another application when a specific event occurs in one application, in response to input from an implementer of the application integration (vendor engineer). Specific examples of the solution will be described later, so further description will be omitted here.

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 S301 above, in response to input from the implementer of the application integration.

The solution and wizard constructed in the above steps S301 and S302, respectively, are incorporated into the vendor product 212 by the application integration implementer. This allows the application integration to be provided to end users.

The process of S301 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 the first application that triggers cooperation, and a step including an action to be executed by the 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.

The process of S302 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 the end user, who is the user of the application integration, in response to input from the implementer of the application integration.

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.

Figure 4 is an exemplary schematic diagram illustrating a solution editor according to an embodiment.

Image 400 shown in FIG. 4 is an example of an image output by display processing unit 103 as a solution editor. Image 400 includes three regions 410, 420, and 430.

Area 410 is the first area for setting the event that will trigger the linkage and the steps to be executed in response to that trigger. The implementer can set the events and steps by setting (selecting or inputting) each item in this area 410.

For example, in area 410 shown in FIG. 4, as an example, a step is set to cause an application called "SaaS_A" to execute an action called "send message". Also, in the "Settings" column in area 410 shown in FIG. 4, a variable called "Channel" indicating the destination to which the message is to be sent and a variable called "Record | Step 3" indicating the contents of the message to be sent are set as variable data (hereinafter simply referred to as variables) referenced in relation to the action "send message". Here, the variable called "Channel" is a variable that is determined in advance in relation to an application called "SaaS_A", for example, and the variable called "Record | Step 3" is a variable for referencing the result of the third process in the flow diagram displayed in area 420, which will be described next.

Area 420 is a second area for displaying a flow diagram showing the flow of information processing including events and steps constructed in response to the input received by area 410. By selecting each step in this area 420, the implementer can display the setting items for that step in the above area 410.

Area 430 is an area for displaying variables that can be used to set 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). The details of these variables will be explained later, so further explanation will be omitted here.

In the example shown in FIG. 4, the step contents are set in area 410, but in area 410, not only steps but also events that will trigger collaboration can be set. When setting an event, area 410 will have a shape like the example shown in FIG. 5 below.

Figure 5 is an exemplary schematic diagram for explaining a trigger according to an embodiment.

Image 500 shown in FIG. 5 is an example of area 410 when setting an event that will trigger collaboration. This image 500 includes multiple areas 510, 520, 530, and 540.

Area 510 is an area where the application to be configured is displayed. The implementer can operate button 511 to toggle between displaying and hiding an interface for selecting the application to be configured. Area 520 is an area where an overview of the event that will trigger the collaboration is displayed. The implementer can operate button 521 to toggle between displaying and hiding an interface for selecting the overview of the event that will trigger the collaboration. Area 530 is an area where setting items related to the event that will trigger the collaboration are displayed. The implementer can operate button 531 to toggle between displaying and hiding an interface for configuring the setting items in detail.

Area 540 is an area where the content that limits the trigger condition of the event displayed in area 520 is displayed. The implementer can switch between displaying and hiding the interface for limiting the trigger condition of the event displayed in area 520 by operating button 541. For example, area 540 shown in FIG. 5 has a limitation set 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 information processing flow shown in the area where the corresponding flow diagram is displayed, such as area 420 described above (= when a file is created, not a folder). The implementer can further add content that limits the trigger condition of the event displayed in area 520 by operating button 542.

In an embodiment, the step to be set can be added via area 420, as shown in FIG. 6 below, for example.

Figure 6 is an exemplary schematic diagram for explaining the addition of a step according to an embodiment.

Image 600 shown in FIG. 6 includes an area 610 displaying a step called "Post a message," and buttons 621, 622, and 623 for determining the next processing flow for that 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.

As mentioned above, area 430 is an area for displaying variables that can be used to set events and steps using the solution editor. These variables are of two types: first variables that are predefined according to the application, and second variables that are arbitrarily defined by the implementer.

The first variable that is predetermined depending on the application is, for example, as shown in Figure 7 below.

Figure 7 is an exemplary schematic diagram for explaining the first variable according to the embodiment.

Image 700 shown in FIG. 7 includes area 410 and third area 430. Area 410 includes area 710 in which the application to be set is displayed, area 720 in which the action to be executed by the application displayed in area 710 is displayed, and area 730 in which setting items related to the action displayed in area 720 are displayed.

The items displayed in area 730, such as "File," "Upload Folder ID," "File Name," and "MIME Type," are first variables that are predefined according to the application displayed in area 710. The third area 430 can be used to set these first variables.

More specifically, the third area 430 shown in FIG. 7 includes an area 750 that displays a list of first variables that are predetermined according to the application displayed in area 710. In this area 750, a number of first variables, such as "file name" that can be referenced when setting an action via area 410, are listed together with their respective types (such as "ABC" indicating a character string). The implementer can reflect a first variable selected from this area 750 in area 730 of area 410.

On the other hand, the second variables that are arbitrarily defined by the implementer are as shown in Figures 8 to 10 below.

Figure 8 is an exemplary schematic diagram for explaining the second variable according to the embodiment.

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 button 810 in this image 800, the implementer can additionally define (create) a second variable via an interface such as that shown in the following FIG. 9.

Figure 9 is an exemplary schematic diagram for explaining the creation of a second variable according to an embodiment.

Image 900 shown in FIG. 9 includes an area 901 that accepts input of the name of a second variable, and a selection interface 902 that displays a list of selectable types of second variables. The implementer can create a second variable by entering an arbitrary name in area 901 and then selecting the type in selection interface 902. The second variable created in this way is used to set steps via the solution editor, for example, in the form shown in the following FIG. 10.

Figure 10 is an exemplary schematic diagram for explaining step setting using a second variable according to an embodiment.

Image 1000 shown in FIG. 10 includes area 410 and third area 430. In the example shown in FIG. 10, the second variable created via image 900 shown in FIG. 9 is displayed in third area 430. The implementer can use the second variable displayed in third area 430 as one of the setting items for the step in area 410.

As mentioned above, the display processing unit 103 not only has the function of providing a screen that accepts input from an implementer for building a solution, but also has the function of providing a screen that accepts input from an implementer for building a wizard. For example, the display processing unit 103 outputs a wizard editor as shown in the following Figure 11 as a second construction screen that accepts input from an implementer for building a wizard.

Figure 11 is an exemplary schematic diagram illustrating a wizard editor according to an embodiment.

Image 1100 shown in FIG. 11 is an example of an image output by display processing unit 103 as a wizard editor. Image 1100 includes four areas 1110, 1120, 1130, and 1140. Image 1100 also includes a button 1101 for switching the wizard editor to the solution editor described above.

Areas 1120, 1130, and 1140 are the fourth area that accepts input from the implementer regarding the screen design of the wizard, and area 1110 is the fifth area that displays screen 1111 as an image that constitutes the wizard constructed in response to the input accepted by areas 1120, 1130, and 1140.

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 separate from screen 1111. Area 1140 is an area for displaying setting items for the end user. For example, area 1140 is used to set on which screen to place an interface for setting authentication for applications used in the solution and an interface for accepting input of a second variable by the end user, as shown in the following FIG. 12.

Figure 12 is an exemplary schematic diagram illustrating a method for arranging an interface for performing authentication settings for applications used in a solution and an interface for accepting input of a second variable on a screen according to an embodiment.

Image 1200 shown in FIG. 12 is an example of area 1140 that displays end user setting items. This image 1200 displays the applications used in the solution. By operating buttons 1211 and 1221, the implementer can set which screen in the wizard the authentication settings for the corresponding application will be placed on. This image 1200 also displays a list of predefined second variables. By operating buttons 1212 and 1222, the implementer can set which screen in the wizard the second variables will be placed on.

Here, in an embodiment, as shown in Figures 13 to 21 below, when placing an interface on the screen that accepts input of the second variable by the end user, it is possible to specify the input format in which the end user is to input the second variable.

Figure 13 is an exemplary schematic diagram illustrating a method for specifying the input format of a second variable according to an embodiment.

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 to allow the end user to select data to be input as the second variable from among fixed options.

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 distinctive input format other than "select", it is possible to specify an input format called "assist" as shown in the following FIG. 14.

Figure 14 is an exemplary schematic diagram for explaining an example of an assist as an example of an input format for a second variable that can be specified in an embodiment.

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 the data to be entered as the 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 FIG. 15 to FIG. 17 below.

Figure 15 is an exemplary schematic diagram for explaining an overview of the assist setting method shown in Figure 14.

Image 1500 shown in FIG. 15 is an example of the sixth area when "assist" is selected as the input format. This image 1500 displays an interface 1510 for selecting what kind of "assist" to provide, that is, which application's data to refer to to present dynamic options.

In the example shown in FIG. 15, one of the options displayed on interface 1510 is "Spreadsheet Sheet List." 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 FIG. 16 below, for example.

Figure 16 is an exemplary schematic diagram for explaining the details of the assist setting method shown in Figure 14.

Image 1600 shown in FIG. 16 is the image that is displayed when "Spreadsheet Sheet List" is selected in interface 1510 of image 1500 above. This image 1600 includes an area 1610 for specifying the parent spreadsheet from which the list of sheets is to be obtained. In this area 1610, the parent spreadsheet is specified, for example, in the form shown in the following FIG. 17.

Figure 17 is an exemplary schematic diagram for explaining the details of the assist setting method shown in Figure 14.

Image 1700 shown in FIG. 17 is an image 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.

Note that the assists that can be set in this embodiment are not limited to the example shown in FIG. 14 above.

Figure 18 is an exemplary schematic diagram for explaining an overview of a method for setting an assist that is different from the example shown in Figure 14.

Image 1800 shown in FIG. 18 is an example different from FIG. 14 of the sixth area described above when "assist" is selected as the input format. This image 1800 includes an interface 1810 that displays the option "folder list" as one of the available assist options.

When selecting a target folder from among many folders, it would be more convenient if it were possible to provide assistance (which could be called selection assistance, for example) by allowing the user to enter only a portion of the string indicating the target folder's name (whether it is a forward match, partial match, or backward match) instead of having to select from all of the folders.

Therefore, in this embodiment, the above selection assistance is realized using an option called "Folder List" displayed in the interface 1810 shown in FIG. 18. The selection assistance is realized, for example, in the form shown in FIG. 19 and FIG. 20 below. The example shown in FIG. 19 and FIG. 20 below is an example of selection assistance for the second variable "SaaS_B Folder".

Figure 19 is an exemplary and schematic diagram to explain the assistance achieved through the example shown in Figure 18.

Image 1900 shown in FIG. 19 includes an interface 1910 including an area 1911 that accepts input of a folder name by an end user, and an area 1912 that displays a list of candidates for that folder name. With the above selection assist, by simply inputting 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. 20.

Figure 20 is an exemplary and schematic diagram to explain the assistance achieved through the example shown in Figure 18.

Image 2000 shown in FIG. 20 corresponds to the case where "1" is entered into 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 into area 1911. In this way, selection assist can reduce the effort required to select (enter) the target folder, improving convenience.

In addition, in the embodiment, as an input format for a second variable different from the above-mentioned "select" and "assist", an input format called "checkbox" as shown in the following Figure 21 can also be specified.

Figure 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 an embodiment.

Image 2100 shown in FIG. 21 is an example of an image output when setting an input format called "checkboxes" in the wizard editor. In this image 2100, area 1110 displays screen 2111 including interface 2112 that presents options in checkbox format, and area 2120 displays image 2120 including interfaces 2121, 2122, and 2123 for setting the display content of screen 2111. Interface 2121 is for specifying the input format called "checkboxes," and interfaces 2122 and 2123 are for inputting options to be presented in checkbox format on screen 2111.

When the solution and wizard settings are complete as described above, the implementer tests whether the settings are correct as intended. Then, after confirming that the solution and wizard settings are correct as intended, the implementer deploys them.

As described above, the server device 100 according to the embodiment is configured to provide application collaboration as an information processing function based on collaboration between multiple 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. In response to input by an implementer of the application collaboration, the solution construction unit 101 constructs an event of the first application that triggers the collaboration and a step including an action to be executed by the 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. In addition, the wizard construction unit 102 constructs a wizard as a user screen to be provided to a user of the application collaboration in response to input by the implementer.

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 the wizard. With this configuration, it is possible to use the server device 100 to facilitate the development of a product that realizes the linkage of multiple applications. 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.

Finally, the hardware configuration of the server device 100 (see FIG. 1) according to the above-described 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 FIG. 22 below, for example.

Figure 22 is an exemplary schematic block diagram showing the hardware configuration of a computer 2200 constituting a server device 100 according to an embodiment.

As shown in FIG. 22, the 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 pieces of hardware are connected to a bus 2260.

The processor 2210 is configured, for example, as a CPU (Central Processing Unit) and provides overall control over the operation of each part of the computer 2200.

Memory 2220 includes, for example, ROM (Read Only Memory) and RAM (Random Access Memory), 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.

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.

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.

The communication interface 2250 enables the computer 2200 to communicate with other devices.

The functional configuration (see FIG. 1) of the server device 100 according to the embodiment is realized as a group of functional modules through the cooperation of 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 specially designed circuit.

The above-mentioned program does not necessarily have to be stored in advance in memory 2220 or storage 2230. For example, the above-mentioned program 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).

The above-mentioned program may also 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.

<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.

Figure 23 is an exemplary schematic block diagram showing an example of a usage mode of application collaboration according to a modified example.

In the modified example shown in FIG. 23, the function for realizing application integration constructed in the same procedure as in the above-described embodiment is installed in the hosting server 2310, rather than 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 integration as a web service. This allows the end-user implementer to use each function of application integration as a web application by accessing the hosting server 2310 using the information processing device 2320.

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 novel embodiments and modifications can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents as set forth in the claims.

101 Solution Construction Unit (First Construction Unit)
102 Wizard construction unit (second construction unit)
103 Display processing unit

Claims (5)

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, in response to an input by an implementer of the information processing function, a step including an event of a first application that triggers the cooperation 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. 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 . 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. 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 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 a first construction step of constructing an information processing flow to be executed by the plurality of applications in the cooperation;
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 comprises 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. In order 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.

Images