JP2023110498A - Information processing device, information processing system, information processing method, and program - Google Patents

Abstract

To make it possible to display log information that allows viewing of input/output data that is permitted to be viewed.SOLUTION: An information processing device capable of communicating with a first information processing terminal and a second information processing terminal via a network includes: a management unit that stores log information that has recorded input/output data related to a series of processes in a storage unit; a receiving unit that receives control information permitting viewing of input/output data from the second information processing terminal; and a screen providing unit that transmits to the first information processing terminal screen information representing a viewing screen that displays the log information in which input/output data that is not permitted to be viewed is kept confidential based on the control information.SELECTED DRAWING: Figure 4

Description

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

2. Description of the Related Art An information processing system is used in which a series of processes connecting a plurality of processes is registered as a flow, and an arbitrary flow is selected from the registered flows and executed. In such an information processing system, it is possible to develop an application that calls a registered flow as part of its function.

For example, Patent Document 1 discloses an information processing system in which an application including one main flow and a plurality of subflows is registered, and parameters can be set when calling subflows from the main flow.

However, in the conventional technology, there is a problem that failure analysis of an application may be difficult. For example, if personal information is included in the input/output data of each process included in the flow, the input/output data is masked so that it cannot be viewed when displaying the log information from the viewpoint of personal information protection. . In this case, the developer cannot obtain sufficient information, making failure analysis difficult.

SUMMARY OF THE INVENTION In view of the technical problems described above, an object of an embodiment of the present invention is to display log information that allows viewing of input/output data that is permitted to be viewed.

In order to solve the above problems, an information processing apparatus according to one embodiment of the present invention is an information processing apparatus capable of communicating with a first information processing terminal and a second information processing terminal via a network, a management unit that stores log information that records input/output data related to a series of processes in a storage unit; a reception unit that receives control information for permitting viewing of the input/output data from the second information processing terminal; and a screen providing unit configured to transmit, to the first information processing terminal, screen information representing a browsing screen displaying log information in which input/output data that is not permitted to be browsed is concealed.

According to one embodiment of the present invention, it is possible to display log information that allows viewing of input/output data that is permitted to be viewed.

It is a figure showing an example of the whole information processing system composition in one embodiment. It is a figure which shows an example of the hardware constitutions of the computer in one embodiment. 1 is a diagram illustrating an example of a hardware configuration of an MFP in one embodiment; FIG. It is a figure showing an example of functional composition of an information processing system in a 1st embodiment. It is a figure which shows an example of the flow in 1st Embodiment. It is a figure which shows an example of the browsing application process in 1st Embodiment. FIG. 7 is a diagram showing an example of a job list screen in the first embodiment; FIG. It is a figure which shows an example of the parameter information in 1st Embodiment. It is a figure which shows an example of the browsing application screen in 1st Embodiment. It is a figure which shows an example of the execution result information in 1st Embodiment. It is a figure which shows an example of the browsing application data in 1st Embodiment. It is a figure which shows an example of the browsing permission process in 1st Embodiment. It is a figure which shows an example of the standby screen in 1st Embodiment. 4 is a diagram showing an example of job-related information in the first embodiment; FIG. It is a figure which shows an example of the input source search process in 1st Embodiment. It is a figure which shows an example of the dictionary information in 1st Embodiment. 4 is a diagram showing an example of permission request data in the first embodiment; FIG. FIG. 7 is a diagram showing an example of a viewing permission screen in the first embodiment; FIG. FIG. 10 is a diagram showing another example of a viewing permission screen in the first embodiment; FIG. 4 is a diagram showing an example of browsing permission data in the first embodiment; FIG. FIG. 7 is a diagram showing an example of job information browsing processing in the first embodiment; FIG. 5 is a diagram showing an example of a job information browsing screen in the first embodiment; FIG. It is a figure which shows an example of the browsing application screen in 2nd Embodiment. It is a figure which shows an example of the browsing application data in 2nd Embodiment. FIG. 12 is a diagram illustrating an example of browsing permission processing in the second embodiment; FIG. FIG. 12 is a diagram showing an example of permission request data in the second embodiment; FIG. FIG. 11 is a diagram showing an example of a viewing permission screen in the second embodiment; FIG. It is a figure which shows an example of the browsing application process in 3rd Embodiment. It is a figure which shows an example of the application information in 3rd Embodiment. It is a figure which shows an example of the browsing application data in 3rd Embodiment. It is a figure which shows an example of the browsing application process in 4th Embodiment. It is a figure which shows an example of the execution result information in 4th Embodiment. It is a figure showing an example of functional composition of an information processing system in a 5th embodiment. It is a figure which shows an example of the flow in 5th Embodiment. FIG. 22 is a diagram showing an example of inspection parameter registration processing in the fifth embodiment; FIG. 21 is a diagram showing an example of an inspection parameter registration screen in the fifth embodiment; FIG. It is a figure which shows an example of the browsing application process in 5th Embodiment. It is a figure which shows an example of the flow in 6th Embodiment. FIG. 21 is a diagram showing an example of output data in the sixth embodiment; FIG. It is a figure which shows an example of the browsing request process in 6th Embodiment. It is a figure which shows an example of the browsing application screen in 6th Embodiment. FIG. 21 is a diagram showing an example of application information in the sixth embodiment; FIG. FIG. 22 is a diagram illustrating an example of input source search processing in the sixth embodiment; It is a figure which shows an example of the browsing application data in 6th Embodiment. FIG. 21 is a diagram showing an example of a viewing permission screen in the sixth embodiment; FIG. It is a figure which shows an example of the application execution screen in 6th Embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, constituent parts having the same function are denoted by the same numbers, and redundant explanations are omitted.

[First embodiment]
A first embodiment of the present invention is an information processing system in which a service providing system provides a service for executing an application including one or more flows to devices via a network. A flow is information that defines a series of processes in which arbitrary functions are selected from multiple functions and connected. Each process included in the flow is implemented by parts called components.

The service providing system in this embodiment provides a graphical development tool for developers to develop applications. The development tool is implemented as a web application and can be run on a browser. A developer can create a flow using a development tool from a developer terminal equipped with a browser. Also, the developer can register the created flow in the service providing system via the network.

Each component included in the flow can input and output various parameters and files. The input data of each component may be data input to the flow by the user or data output by the previous component. When executing a flow in response to a user's request, the service providing system generates log information (hereinafter also referred to as "job information") that records input/output data of each component together with execution results.

If an error occurs when executing a flow, the user may request the application developer to analyze the failure. The developer who received the request refers to the job information when the flow was executed to identify the cause of the failure and recover from the failure. However, job information may contain personal information, confidential information, or the like. Therefore, when job information is displayed, the input/output data may be masked to keep it confidential so that it cannot be viewed by a third party. In this case, the developer cannot obtain sufficient information, making failure analysis difficult.

The information processing system according to the present embodiment, when outputting job information in which the input/output data is kept confidential, performs control so that the input/output data that the user has permitted to view is not kept confidential. According to the information processing system of this embodiment, a developer can obtain information necessary for failure analysis, and failure analysis is facilitated.

<Overall Configuration of Information Processing System 100>
First, the configuration of an information processing system 100 according to this embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of an information processing system 100 according to this embodiment.

As shown in FIG. 1 , information processing system 100 includes service providing system 10 , developer terminal 20 , one or more devices 30 , and one or more external service systems 40 . The service providing system 10, the developer terminal 20, the device 30 and the external service system 40 are each connected to the communication network N1. The communication network N1 is configured so that connected devices can communicate with each other.

The communication network N1 is constructed by a wired communication network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network). The communication network N1 includes not only wired communication but also wireless LAN, wireless communication such as short-range wireless communication, WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or 5G (5th Generation). of mobile communication networks may be included.

The service providing system 10 is realized by one or more information processing devices, and provides various services realized by a series of processes in cooperation with an external service system 40 such as a cloud service via the communication network N1. In addition, hereinafter, the service provided by the service providing system 10 is also referred to as an “application”. A series of processes for realizing a service is also referred to as a "flow".

In this embodiment, a cloud service is used as a specific example of the external service, but the present invention is not limited to this. The present embodiment may be applied to various external services provided via a network, such as services provided by an ASP (Application Service Provider) and web services.

The developer terminal 20 is an information processing device used by a developer who develops an application. A developer can use the developer terminal 20 to develop various applications provided by the service providing system 10 .

The devices 30 are various electronic devices used by users who use applications. A user can use various applications provided by the service providing system 10 using the device 30 .

Hereinafter, when distinguishing between the plurality of devices 30, they are described using serial numbers such as “device 30-1” and “device 30-2”.

An example of the service providing system 10 and developer terminal 20 is a computer. An example of the device 30 is an image forming device (printer, FAX device, MFP (Multifunction Peripheral/Product/Printer: digital multifunction peripheral), scanner device, etc.). Another example of device 30 is a computer.

The developer terminal 20 and the device 30 are not limited to information processing devices or image forming devices as long as they are devices having a communication function. That is, the developer terminal 20 and the device 30 are, for example, a PJ (Projector), an IWB (Interactive White Board: a whiteboard having an electronic blackboard function capable of mutual communication), an output device such as a digital signage, a HUD ( Head Up Display) equipment, industrial machinery, imaging equipment, sound collecting equipment, medical equipment, network appliances, automobiles (connected cars), notebook PCs (personal computers), mobile phones, smartphones, tablet terminals, game machines, PDA (Personal Digital) Assistant), a digital camera, a wearable PC, a desktop PC, or the like.

The external service system 40 is realized by one or more information processing devices, and provides various cloud services via the communication network N1. An example of an external service system is a cloud service called storage service (or online storage). A storage service is a service that lends out a storage area of the storage of the external service system 40 .

Hereinafter, a plurality of external service systems 40 will be described using branch numbers such as "external service system 40-1" and "external service system 40-2" when distinguishing between them. Also, the names of the storage services provided by the external service system 40-1 and the external service system 40-2 are respectively called "external storage service A" and "external storage service B".

The configuration of the information processing system 100 shown in FIG. 1 is an example, and other configurations may be used. For example, the information processing system 100 in this embodiment includes various devices that perform at least one of input and output of electronic data, and these devices may use various services provided by the service providing system 10. .

<Hardware Configuration of Information Processing System 100>
Next, the hardware configuration of each device included in the information processing system 100 according to this embodiment will be described with reference to FIGS. 2 and 3. FIG.

<<Computer hardware configuration>>
FIG. 2 is a diagram showing an example of a hardware configuration when the service providing system 10, developer terminal 20, device 30, and external service system 40 are implemented by a computer.

As shown in FIG. 2, the computer includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, RAM (Random Access Memory) 503, HD (Hard Disk) 504, HDD (Hard Disk Drive) Controller 505, display 506, external device connection I/F (Interface) 508, network I/F 509, bus line 510, keyboard 511, pointing device 512, DVD-RW (Digital Versatile Disk Rewritable) drive 514, media I/F 516 I have.

Among these, the CPU 501 controls the operation of the entire computer. The ROM 502 stores programs used to drive the CPU 501, such as an IPL (Initial Program Loader). A RAM 503 is used as a work area for the CPU 501 . The HD 504 stores various data such as programs. The HDD controller 505 controls reading or writing of various data to/from the HD 504 under the control of the CPU 501 .

A display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection I/F 508 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. A network I/F 509 is an interface for data communication using the communication network N1. A bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

Also, the keyboard 511 is a kind of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 512 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A DVD-RW drive 514 controls reading or writing of various data to a DVD-RW 513 as an example of a removable recording medium. It should be noted that not only DVD-RW but also DVD-R or the like may be used. A media I/F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

<<Hardware Configuration of MFP>>
FIG. 3 is a diagram showing an example of a hardware configuration when the device 30 is realized by an MFP.

As shown in FIG. 3, the MFP has a controller 910, a short-range communication circuit 920, an engine control section 930, an operation panel 940, and a network I/F 950.

Among these, the controller 910 includes a CPU 901, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a storage unit, which is the main part of the computer. A local memory (MEM-C) 907 , an HDD controller 908 , and an HD 909 as a storage unit, and the NB 903 and ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921 .

Among these, the CPU 901 is a control unit that performs overall control of the MFP. The NB 903 is a bridge for connecting the CPU 901, the MEM-P 902, the SB 904, and the AGP bus 921, and is a memory controller that controls reading and writing with respect to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target. have

The MEM-P 902 is composed of a ROM 902a, which is a memory for storing programs and data for realizing each function of the controller 910, and a RAM 902b, which is used as a drawing memory for expanding the programs and data and for memory printing. The program stored in the RAM 902b is configured to be provided by being recorded in a computer-readable recording medium such as a CD-ROM, CD-R, DVD, etc. as a file in an installable format or an executable format. You may

The SB 904 is a bridge for connecting the NB 903 with PCI devices and peripheral devices. The ASIC 906 is an image processing IC (Integrated Circuit) having hardware elements for image processing, and serves as a bridge that connects the AGP bus 921, PCI bus 922, HDD 908 and MEM-C 907, respectively. This ASIC 906 includes a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 906, a memory controller that controls the MEM-C 907, and multiple DMACs (Direct Memory Access Controllers) that perform image data rotation, etc. by hardware logic. , and a PCI unit that transfers data between the scanner unit 931 and the printer unit 932 via the PCI bus 922 . Note that the ASIC 906 may be connected to a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface.

MEM-C 907 is a local memory used as an image buffer for copying and an encoding buffer. The HD 909 is a storage for accumulating image data, accumulating font data used for printing, and accumulating forms. The HD 909 controls reading or writing of data to or from the HD 909 under the control of the CPU 901 . The AGP bus 921 is a bus interface for graphics accelerator cards proposed to speed up graphics processing, and can speed up the graphics accelerator card by directly accessing the MEM-P 902 with high throughput. .

The near field communication circuit 920 also includes a near field communication circuit 920a. The short-range communication circuit 920 is a communication circuit for NFC, Bluetooth, or the like.

Furthermore, the engine control section 930 is configured by a scanner section 931 and a printer section 932 . The operation panel 940 displays a current setting value, a selection screen, and the like, and a panel display unit 940a such as a touch panel for receiving input from an operator, and setting values for image forming conditions such as density setting conditions. An operation panel 940b is provided which includes a numeric keypad for accepting a copy start instruction, a start key for accepting a copy start instruction, and the like. A controller 910 controls the entire image forming apparatus, such as drawing, communication, and input from an operation panel 940 . The scanner unit 931 or printer unit 932 includes an image processing part such as error diffusion and gamma conversion.

The MFP can switch and select the document box function, the copy function, the printer function, and the facsimile function in sequence using the application switching key on the operation panel 940 . The document box mode is set when the document box function is selected, the copy mode is set when the copy function is selected, the printer mode is set when the printer function is selected, and the facsimile mode is set when the facsimile mode is selected.

A network I/F 950 is an interface for data communication using the communication network N1. A short-range communication circuit 920 and a network I/F 950 are electrically connected to the ASIC 906 via a PCI bus 922 .

<Functional Configuration of Information Processing System 100>
Next, an example of the functional configuration of the information processing system 100 according to this embodiment will be described with reference to FIG. FIG. 4 is a block diagram illustrating the functional configuration of each device included in the information processing system 100 according to this embodiment.

<<Functional Configuration of Service Providing System 10>>
As shown in FIG. 4, the service providing system 10 in this embodiment includes a screen information storage unit 101, an application information storage unit 102, a file storage unit 103, a job information storage unit 104, a portal service unit 110, and an input/output unit. A service unit 120 is provided. Portal service unit 110 includes screen providing unit 111 , job information viewing unit 112 , viewing permission requesting unit 113 , and job information translation unit 114 . The input/output service unit 120 includes an application management unit 121 , a file management unit 122 , a job management unit 123 , a job information control unit 124 and a notification unit 125 .

The portal service unit 110 and the input/output service unit 120 are implemented by, for example, processing that causes the CPU 501 and the HDD controller 505 to execute a program expanded from the HD 504 shown in FIG. 2 onto the RAM 503 .

The screen information storage unit 101, the application information storage unit 102, the file storage unit 103, and the job information storage unit 104 are realized using the HD 504 shown in FIG. 2, for example. Reading or writing of data stored in the HD 504 is performed via the HDD controller 505, for example.

Note that the screen information storage unit 101, the application information storage unit 102, the file storage unit 103, and the job information storage unit 104 are not provided in the service providing system 10, and external storage devices may be used. An example of an external storage device is NAS (Network Attached Storage) or an online storage service.

The screen information storage unit 101 stores screen information provided by the screen providing unit 111 to the browsers 210 and 310 . Each piece of screen information stored in the screen information storage unit 101 is, for example, screen information described in HTML (HyperText Markup Language) or the like, and may include an application described in JavaScript (registered trademark) or the like.

The application information storage unit 102 stores application information related to applications provided by the service providing system 10 . The application information is associated with an application ID that identifies the application.

The application information includes screen definition and processing content. A screen definition is data defining a screen provided when an application is executed. The screen definition includes data to be displayed on the screen, layout, and the like. The processing content is data representing settings related to the flow included in the application. The processing contents include the execution order of components in the flow, parameter definitions of each component, and the like.

The file storage unit 103 temporarily stores files input or generated when the service providing system 10 executes an application. A file is associated with a file ID that identifies the file.

The job information storage unit 104 stores job information when the service providing system 10 executes the application. Job information is associated with a job ID that identifies the job.

The job information includes parameter information, execution result information, and job-related information. The parameter information is data recording input/output data of each component included in the flow. Input and output data are parameters or files. When the input/output data is a file, information indicating the file (file ID and/or file name) is recorded in the parameter information.

The execution result information is data recording the results of executing each component. In particular, when an error occurs in a component, the content of the error is recorded in detail. The job relation information is data recording the order relation between components.

The screen providing unit 111 transmits (provides) screen information stored in the screen information storage unit 101 to the developer terminal 20 and the device 30 in response to requests from the developer terminal 20 and the device 30 .

The job information browsing unit 112 requests job information from the job information control unit 124 in response to a request from the developer terminal 20 . Also, the job information browsing unit 112 transmits the job information received from the job information control unit 124 to the developer terminal 20 .

The viewing permission application unit 113 receives viewing application data from the developer terminal 20 . Also, the viewing permission application unit 113 requests the job management unit 123 to register the viewing application data. The access request data is data representing input/output data for which access is requested.

In addition, the viewing permission application unit 113 transmits viewing application data managed by the job management unit 123 to the device 30 in response to a request from the device 30 . At this time, the viewing permission application unit 113 requests the job information translation unit 114 to convert the viewing application data into permission request data. Permission request data is data for requesting permission to view input/output data for which viewing has been requested.

Furthermore, the viewing permission application unit 113 receives viewing permission data from the device 30 . Also, the viewing permission application unit 113 requests the job management unit 123 to register viewing permission data. Browsing permission data is data representing input/output data for which browsing is permitted.

Job information translation unit 114 converts the viewing application data into permission request data in response to a request from viewing permission requesting unit 113 . At this time, the job information translation unit 114 identifies the data of the input source by tracing the relationship of the input/output data requested to be browsed, and adds the identified input data to the browse application data. In addition, the job information translation unit 114 converts the wording included in the browsing application data into content that is easy for the user to understand. Predetermined dictionary information and application information are used for word conversion.

The application management unit 121 writes and reads application information to and from the application information storage unit 102 .

The file management unit 122 writes and reads files to and from the file storage unit 103 .

The job management unit 123 writes and reads job information in the job information storage unit 104 .

Job information control unit 124 requests job information from job management unit 123 in response to a request from job information browsing unit 112 or browsing permission application unit 113 . In addition, the job information control unit 124 controls the job information received from the job management unit 123 so that input/output data permitted to be viewed can be viewed and other input/output data cannot be viewed. Then, the job information control unit 124 sends the job information in which the input/output data for which viewing is not permitted is prohibited to be viewed to the job information viewing unit 112 or the viewing permission requesting unit 113 .

The notification unit 125 notifies the device 30 that the viewing application data has been registered from the developer terminal 20 in response to the request from the viewing permission application unit 113 . Also, the notification unit 125 notifies the developer terminal 20 that the viewing permission data has been registered from the device 30 in response to the request from the viewing permission application unit 113 .

<<Function Configuration of Developer Terminal 20>>
As shown in FIG. 4, the developer terminal 20 in this embodiment has a browser 210 . The browser 210 is realized, for example, by processing that is executed by the CPU 501 from the HD 504 shown in FIG.

The browser 210 requests screen information from the screen providing unit 111 included in the service providing system 10 according to the developer's operation. Also, the browser 210 displays a screen used by the developer on the display 506 based on the screen information received from the screen providing unit 111 .

<<Functional configuration of device 30>>
As shown in FIG. 4, device 30 in this embodiment comprises browser 310 . The browser 310 is implemented by, for example, processing that causes the CPU 901 to execute a program developed on the RAM 902a from the HD 909 shown in FIG.

The browser 310 requests screen information from the screen providing unit 111 included in the service providing system 10 according to the user's operation. In addition, browser 310 displays a screen to be used by the user on operation panel 940 based on the screen information received from screen providing unit 111 .

<Processing procedure of information processing system 100>
Next, the details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method in this embodiment includes: 1. browsing application processing;2. Browsing permission processing and 3. Includes job information browsing processing.

≪Premise≫
First, the flow assumed in this embodiment will be described with reference to FIG. FIG. 5 is a conceptual diagram showing an example of the flow in this embodiment.

As shown in FIG. 5, flow 1000 in this embodiment executes file download component 1100, PDF conversion component 1200 and image extraction component 1300 in sequence.

File download component 1100 downloads a specified file from external storage service A. The PDF conversion component 1200 converts the input file into a file in PDF format. The image extraction component 1300 extracts images embedded in the input PDF file.

When the user executes the application containing flow 1000, the user enters a file ID that identifies the file. The file download component 1100 downloads the file from the external storage service A based on the file ID entered by the user.

Assume that an error occurs when the user executes the application including the flow 1000 . The user requests the developer to analyze the failure. When the developer browsed the job information when the application was executed, it was found that the file download component 1100 and PDF conversion component 1200 were successful, but an error occurred in the image extraction component 1300 .

The execution result information included in the job information records that the error that occurred is an "error due to an external factor." This error is known to be caused by bad input data. Therefore, the developer considers it necessary to check the content of the file input to the image extraction component 1300 .

However, since the flow 1000 may handle files containing personal information or confidential information, the input/output data is set so that third parties cannot view it. Therefore, the developer needs the user's permission to view the file input to the image extraction component 1300 .

≪1. Browse request process≫
First, referring to FIG. 6, a description will be given of a viewing application process in which a developer applies for viewing input/output data. FIG. 6 is a sequence diagram showing an example of browsing request processing executed by the information processing system 100 according to this embodiment.

In step S101, the browser 210 included in the developer terminal 20 transmits a request to acquire the viewing application screen to the service providing system 10 in response to the developer's operation on the job list screen.

Here, the job list screen in this embodiment will be described with reference to FIG. FIG. 7 is a conceptual diagram showing an example of a job list screen in this embodiment.

As shown in FIG. 7, the job list screen 2000 in this embodiment has an application ID display field 2010 and a job list display field 2020. FIG. The job list display field 2020 has a job ID display field 2021 , a status display field 2022 and a browse request button 2023 .

An application ID display field 2010 displays an application ID corresponding to the displayed job information. A job ID display field 2021 displays a job ID for identifying the job information. A status display column 2022 displays the execution result of the job information. When the browse application button 2023 is pressed, the browser 210 transmits a request to acquire the browse application screen to the service providing system 10 .

Returning to FIG. 6, description will be made. In step S<b>102 , the screen providing unit 111 included in the service providing system 10 receives an acquisition request for a browsing application screen from the developer terminal 20 . Next, the screen providing unit 111 acquires screen information representing the browsing application screen from the screen information storage unit 101 . Subsequently, the screen providing unit 111 transmits the acquired screen information to the developer terminal 20 . In the developer terminal 20, the browser 210 receives the screen information representing the browsing application screen.

In step S<b>103 , the browser 210 of the developer terminal 20 transmits a job information acquisition request to the service providing system 10 . The acquisition request includes the application ID and job ID related to the job information selected on the job list screen 2000 .

In the service providing system 10 , the viewing permission application unit 113 receives the job information acquisition request from the developer terminal 20 . The viewing permission application unit 113 requests the job information control unit 124 for job information corresponding to the job ID included in the acquisition request. The job information control unit 124 requests the job management unit 123 for job information corresponding to the job ID.

In step S<b>104 , the job management unit 123 provided in the service providing system 10 receives a job information acquisition request from the job information control unit 124 . Next, the job management section 123 acquires job information corresponding to the job ID included in the acquisition request from the job information storage section 104 . Subsequently, the job management section 123 sends the acquired job information to the job information control section 124 .

In step S<b>105 , the job information control section 124 provided in the service providing system 10 receives job information from the job management section 123 . Next, the job information control unit 124 extracts parameter information from the job information.

Subsequently, the job information control unit 124 performs mask processing on the input/output data included in the parameter information. Subsequently, the job information control unit 124 sends the job information including the masked parameter information to the viewing permission application unit 113 . The viewing permission application unit 113 transmits the job information received from the job information control unit 124 to the developer terminal 20 .

Here, parameter information in this embodiment will be described with reference to FIG. FIG. 8 is a conceptual diagram showing an example of parameter information in this embodiment.

As shown in FIG. 8, the parameter information 3000 in this embodiment describes jobDetailParameters. jobDetailParameters is an array of jobDetailParameters. jobDetailParameter is a data structure that records the input/output data used when executing each component.

Each jobDetailParameter records a job ID (jobId: 233333) for identifying the job and job detail IDs (id: 3456787, 3456788, 3456789) for identifying the components in the job. Input/output data (parameters, inputFile, outputFile, etc.) for the component is recorded in each jobDetailParameter.

In the parameter information 3000, the contents of input/output data (fileId, fileName, etc.) are masked by mask processing. However, the data (id, relationFileId, etc.) used internally by the service providing system 10 are not masked because they do not contain personal information or confidential information. Note that relationFileId is data for recording a file ID that identifies a file before conversion when the component converts the file.

Returning to FIG. 6, description will be made. In step S<b>106 , the browser 210 of the developer terminal 20 receives job information from the service providing system 10 . Next, the browser 210 displays the viewing application screen on the display 506 or the like based on the screen information and job information received from the service providing system 10 .

Here, the viewing application screen according to the present embodiment will be described with reference to FIG. 9 . FIG. 9 is a conceptual diagram showing an example of a viewing application screen in this embodiment.

As shown in FIG. 9, the browsing application screen 2100 in this embodiment has a component display field 2101, an input data selection field 2102, an output data selection field 2103, and a send button 2109. FIG.

The component display field 2101 displays words representing components included in the flow. The input data selection field 2102 displays the input data of the component in a selectable format. The output data selection field 2103 displays the output data of the component in a selectable format.

Returning to FIG. 6, description will be made. In step S<b>107 , the browser 210 provided in the developer terminal 20 transmits an acquisition request for the browse application items to the service providing system 10 . The acquisition request includes an application ID and a job ID.

In step S<b>108 , the viewing permission application unit 113 provided in the service providing system 10 receives a request to acquire viewing request items from the developer terminal 20 . Next, the viewing permission application unit 113 sends a request for acquisition of execution result information to the job management unit 123 . The acquisition request includes an application ID and a job ID.

In step S<b>109 , the job management unit 123 included in the service providing system 10 receives the execution result information acquisition request from the browsing permission application unit 113 . Next, the job management unit 123 acquires execution result information corresponding to the application ID and job ID included in the acquisition request from the job information storage unit 104 . Subsequently, the job management section 123 sends the obtained execution result information to the viewing permission application section 113 .

In step S<b>110 , the viewing permission application unit 113 provided in the service providing system 10 receives execution result information from the job management unit 123 . Next, the viewing permission application unit 113 identifies the component in which the error occurred based on the execution result information. Subsequently, the viewing permission application unit 113 transmits information about the specified component (hereinafter also referred to as “error component information”) to the developer terminal 20 .

Here, execution result information in this embodiment will be described with reference to FIG. FIG. 10 is a conceptual diagram showing an example of execution result information in this embodiment.

As shown in FIG. 10, the execution result information 3100 in this embodiment includes application ID (id: 100000), job ID (jobId: 233333), job detail ID (jobDetailId: 3456789), execution result (status : "error"), component name (componentName: "extraImages"), and error code (message_id: "io-pdf.external_error") are recorded. Therefore, it can be seen from the execution result information 3100 shown in FIG. 10 that an error has occurred in the image extraction component 1300 due to an external factor.

Returning to FIG. 6, description will be made. In step S<b>111 , the browser 210 provided in the developer terminal 20 receives error component information from the service providing system 10 . The browser 210 then suggests input/output data to apply for viewing based on the error component information. Specifically, the browser 210 automatically selects the input/output data related to the component in which the error occurred from among the input/output data displayed in the input data selection field 2102 and the output data selection field 2103 on the browsing application screen 2100. do.

In step S<b>112 , the browser 210 of the developer terminal 20 generates viewing application data according to the developer's operation on the viewing application screen 2100 . Next, the browser 210 transmits a registration request for viewing application to the service providing system 10 . The registration request includes the generated browsing application data.

Specifically, the developer presses a send button 2109 on the viewing application screen 2100 . The browser 210 generates access request data for requesting access to the input/output data selected in the input data selection field 2102 and the output data selection field 2103 . Then, the browser 210 transmits a request for registering the browsing application to the service providing system 10 . The registration request includes the generated browsing application data.

In the service providing system 10, the browsing permission application unit 113 receives the registration request for the browsing application. The viewing permission application unit 113 sends the viewing application data included in the registration request to the job management unit 123 .

Here, the browsing application data in this embodiment will be described with reference to FIG. 11 . FIG. 11 is a conceptual diagram showing an example of browsing request data in this embodiment.

As shown in FIG. 11, jobDetails is described in the browse request data 3200 in this embodiment. jobDetails is an array of jobDetails. jobDetail is a data structure that represents information about the input/output data for which viewing is requested.

Each jobDetail describes a job ID (jobId: 233333) that identifies the job and a job detail ID (id: 3456789) that identifies a component in the job. Also, each jobDetail describes the input/output data (inputFile) to be viewed. Note that browsable included in inputFile is a setting value for controlling whether or not the input/output data can be browsed.

The jobDetailParameter described in the parameter information 3000 and the jobDetail described in the viewing application data 3200 are associated by a job detail ID (id).

Returning to FIG. 6, description will be made. In step S<b>113 , the job management unit 123 provided in the service providing system 10 receives the viewing application data from the viewing permission requesting unit 113 . Next, the job management section 123 stores the browse application data in the job information storage section 104 . Subsequently, the job management unit 123 sends the registration result of the browsing application to the browsing permission application unit 113 . The registration result includes a job ID. The viewing permission application unit 113 transmits the registration result of the viewing application received from the job management unit 123 to the developer terminal 20 .

In step S<b>114 , the browser 210 provided in the developer terminal 20 receives the registration result of the browsing application from the service providing system 10 . Next, the browser 210 transmits a user notification request to the service providing system 10 . The notification request includes an application ID and a job ID.

In step S<b>115 , the notification unit 125 provided in the service providing system 10 receives a notification request to the user from the developer terminal 20 . Next, the notification unit 125 generates a URL (Uniform Resource Locator) for opening the viewing permission screen based on the application ID and job ID included in the notification request.

Subsequently, the notification unit 125 notifies the user of the generated URL. The user may be notified by sending an e-mail containing a URL to the user's e-mail address, or by sending a message containing a URL to the user's account via SNS (Social Networking Service) or the like. good.

≪2. Browsing permission process≫
Next, referring to FIG. 12, a browse permission process for allowing a user to browse input/output data will be described. FIG. 12 is a sequence diagram showing an example of browsing permission processing executed by the information processing system 100 according to this embodiment.

In step S<b>201 , the browser 310 provided in the device 30 transmits a viewing permission screen acquisition request to the service providing system 10 in response to the user's operation. Specifically, the user performs an operation to open the notified URL.

In step S<b>202 , the screen providing unit 111 included in the service providing system 10 receives an acquisition request for a viewing permission screen from the device 30 . Next, the screen providing unit 111 acquires screen information representing the browsing permission screen from the screen information storage unit 101 . Subsequently, the screen providing unit 111 transmits the acquired screen information to the developer terminal 20 . In the device 30, the browser 310 receives the screen information representing the browsing permission screen.

In step S<b>203 , the browser 310 provided in the device 30 transmits an acquisition request for browsing application data to the service providing system 10 . The acquisition request includes a job ID specified by the notified URL. At this time, browser 310 displays standby screen 2200 shown in FIG. 13 on operation panel 940 .

In the service providing system 10 , the viewing permission requesting unit 113 receives the viewing request data acquisition request from the device 30 . The viewing permission application unit 113 requests the job management unit 123 for viewing application data corresponding to the job ID included in the acquisition request.

In step S<b>204 , the job management unit 123 provided in the service providing system 10 receives a request for obtaining viewing application data from the viewing permission requesting unit 113 . Next, the job management unit 123 acquires from the job information storage unit 104 the browsing application data corresponding to the job ID included in the acquisition request. Subsequently, the job management section 123 sends the acquired viewing application data to the viewing permission requesting section 113 .

In step S<b>205 , the viewing permission application unit 113 included in the service providing system 10 receives the viewing application data from the job management unit 123 . Next, the viewing permission application unit 113 sends a conversion request for the viewing application data to the job information translation unit 114 . The conversion request includes the browsing application data received from the job management unit 123 .

In step S<b>206 , the job information translation unit 114 provided in the service providing system 10 receives a conversion request for viewing application data from the viewing permission requesting unit 113 . Next, the job information translation unit 114 sends a job information acquisition request to the job information control unit 124 . The acquisition request includes a job ID. The job information control unit 124 requests the job management unit 123 for job information corresponding to the job ID included in the acquisition request.

In step S<b>207 , the job management unit 123 included in the service providing system 10 receives the job information acquisition request from the job information control unit 124 . Next, the job management section 123 acquires job information corresponding to the job ID included in the acquisition request from the job information storage section 104 . Subsequently, the job management section 123 sends the acquired job information to the job information control section 124 . The job information includes parameter information and job-related information.

Here, job-related information in this embodiment will be described with reference to FIG. FIG. 14 is a conceptual diagram showing an example of job-related information in this embodiment.

As shown in FIG. 14, jobDetailRelation is described in the job relation information 3300 in this embodiment. In each element of jobDetailRelation, id corresponds to the job detail ID of each component. previousId corresponds to the job detail ID of the previously executed component. nextId corresponds to the job detail ID of the component executed after one. Therefore, by following the previousId and nextId from the element specified by the job detail ID (id) for which viewing is requested, it is possible to trace the flow and search for the relationship between the input and output data of each component. .

Returning to FIG. 12, description will be made. In step S<b>208 , the job information control unit 124 included in the service providing system 10 receives job information from the job management unit 123 . Next, the job information control unit 124 extracts parameter information from the job information. Subsequently, the job information control unit 124 performs mask processing on the input/output data included in the parameter information. The job information control unit 124 then sends the job information including the masked parameter information to the job information translation unit 114 .

In step S<b>209 , the job information translation unit 114 included in the service providing system 10 receives job information from the job information control unit 124 . Next, based on the parameter information and job-related information included in the job information, the job information translation unit 114 traces the relationship between the input/output data requested to be browsed, and Identify the original data. Subsequently, the job information translation unit 114 adds the specified input data to the browsing application data.

In this embodiment, the input/output data requested by the developer to be viewed is the input file of the image extraction component 1300 . However, since the user does not know the concept of a component, it is not possible to judge whether or not there is no problem in permitting viewing based on the content of the application. Therefore, by specifying the input source file, the content of the application is converted into an easy-to-understand application content for the user. This is because the input source file is input by the user, so the user should be aware of the file.

Here, a procedure for searching for input source data (hereinafter also referred to as "input source search processing") will be described with reference to FIG. FIG. 15 is a flow chart showing an example of input source search processing in this embodiment.

In step S209-1, the job information translation unit 114 acquires parameter information and job-related information from the job information control unit 124. FIG. Hereinafter, the parameter information is assumed to be the parameter information 3000 shown in FIG. The job-related information is assumed to be the job-related information 3300 shown in FIG.

In step S209-2, the job information control unit 124 acquires the id of the inputFile described in the browsing application data. Also, from jobDetailParameters described in the parameter information, get jobDetailParameter with an id that matches the id of inputFile. Hereinafter, this id will be referred to as "the id of the current jobDetail".

In step S209-3, the job information translation unit 114 identifies an element that matches the id of the current jobDetail from the jobDetailRelation described in the job-related information. Also, the id of the previous jobDetail is obtained from the previousId of the identified element.

In step S209-4, the job information translation unit 114 determines whether or not the relationFileId of the inputFile of the jobDetailParameter matches the id of the outputFile of the previous jobDetail. If they do not match (NO), the previous jobDetail is set as the current jobDetail and the process moves to S209-3. If they match (YES), the process moves to S209-5.

In step S209-5, the job information translation unit 114 determines whether or not there is inputFile in jobDetailParameter. If not (NO), it is determined that the input data has been input from the component, and the process ends. If there is (YES), the process moves to S209-6.

In step S209-6, the job information translation unit 114 acquires information of inputFile of jobDetailParameter. This is the information representing the file before it is converted by the component.

In step S209-7, the job information translation unit 114 refers to previousId of jobDetailRelation and determines whether or not there is a previous jobDetail. If there is (YES), move to S209-3 with the previous jobDetail as the current jobDetail. If not (NO), exit the loop and move to S209-8.

In step S209-8, the job information translation unit 114 identifies the current jobDetail as the component to which the input source data is input, and terminates the process.

The flowchart shown in FIG. 15 will be described by taking the flow 1000 shown in FIG. 5 as an example. JobDetail of the browsing request data shown in FIG. 11 corresponds to the image extraction component 1300 . The jobDetailParameter of the previous PDF conversion component 1200 is referenced to determine whether the output file (outputFile) of the PDF conversion component 1200 matches the input file (inputFile) of the image extraction component 1300 . Here, since they match, the input file of the PDF conversion component 1200 is acquired.

Next, the same thing is done for the file download component 1100 as well. The inputFile of the PDF conversion component 1200 and the outputFile of the file download component 1100 match. However, file download component 1100 does not have an inputFile. Therefore, in the file download component 1100, it can be determined that the file is downloaded from the external storage service A and input to the flow. In this way, the input source data can be specified.

Returning to FIG. 12, description will be made. In step S210, the job information translation unit 114 provided in the service providing system 10 uses predetermined dictionary information to translate the wording included in the browsing application data. Next, the job information translation unit 114 transmits the converted browsing application data to the device 30 as permission request data.

Here, dictionary information in this embodiment will be described with reference to FIG. FIG. 16 is a conceptual diagram showing an example of dictionary information in this embodiment.

As shown in FIG. 16, in the dictionary information 3400 in this embodiment, the terms described in the browsing request data and the words used when displaying the terms to the user are described in association with each other. It is For example, a component name (componentName) of "storageA" is converted into the words of "external storage A".

Next, permission request data in this embodiment will be described with reference to FIG. FIG. 17 is a conceptual diagram showing an example of permission request data in this embodiment.

As shown in FIG. 17, the permission request data 3500 in this embodiment has the file ID (display: 500001) specified as the input source data in the display of inputFile when compared with the viewing application data 3200. The difference is that In addition, the file ID (id: 500001) of the inputFile specified as the input source data in relatedFile, the component name (componentName: "storageA",) where the input source data was input, and the operation name (operationName: "fileDownload") are The points described are different.

Returning to FIG. 12, description will be made. In step S<b>211 , the browser 310 provided in the device 30 receives permission request data from the service providing system 10 . Next, browser 310 displays a viewing permission screen on operation panel 940 or the like based on the screen information and permission request data received from service providing system 10 .

Here, the viewing permission screen in this embodiment will be described with reference to FIGS. 18 and 19. FIG. FIG. 18 is a conceptual diagram showing an example of a viewing permission screen in this embodiment.

As shown in FIG. 18, the viewing permission screen 2300 in this embodiment has a viewing permission data selection field 2301 and a send button 2309 .

In the view-permitted data selection field 2301, the input/output data requested to be viewed is displayed in a selectable format. Note that the wording displayed in the browse-permitted data selection field 2301 is converted using dictionary information.

FIG. 19 is a conceptual diagram showing another example of the viewing permission screen in this embodiment. As shown in FIG. 19, the viewing permission screen 2300 in this embodiment may have a file preview field 2302 in addition to the viewing permission data selection field 2301 and the send button 2309 .

In the file preview column 2302, when the input/output data requested to be browsed is a file, a preview of the content of the file is displayed. Since the user may not be able to understand the content of the file based on the file name alone, previewing the content of the file enables the user to appropriately determine whether or not to permit browsing.

Returning to FIG. 12, description will be made. In step S<b>212 , the browser 310 provided in the device 30 generates viewing permission data according to the user's operation on the viewing permission screen 2300 . Next, the browser 310 transmits a viewing permission registration request to the service providing system 10 . The registration request includes the generated browsing permission data.

Specifically, the user presses a send button 2309 on the viewing permission screen 2300 . The browser 310 generates viewing permission data for permitting viewing of the input/output data selected in the viewing permission data selection field 2301 . The browser 310 then transmits a viewing permission registration request to the service providing system 10 . The registration request includes the generated browsing permission data.

In the service providing system 10, the viewing permission application unit 113 receives the viewing permission registration request. The viewing permission application unit 113 sends the viewing permission data included in the registration request to the job management unit 123 .

Here, viewing permission data in this embodiment will be described with reference to FIG. 20 . FIG. 20 is a conceptual diagram showing an example of browsing permission data in this embodiment.

As shown in FIG. 20, viewing permission data 3600 in this embodiment differs from permission request data 3500 in that browsable included in inputFile is set to "true".

Returning to FIG. 12, description will be made. In step S<b>213 , the job management unit 123 provided in the service providing system 10 receives the viewing permission data from the viewing permission application unit 113 . Next, job management section 123 stores the browsing permission data in job information storage section 104 . Subsequently, the job management unit 123 sends the browsing permission registration result to the browsing permission application unit 113 . The registration result includes a job ID. The viewing permission application unit 113 transmits the viewing permission registration result received from the job management unit 123 to the device 30 .

In step S<b>214 , the browser 310 provided in the device 30 receives the registration result of viewing permission from the service providing system 10 . Next, the browser 310 transmits a developer notification request to the service providing system 10 . The notification request includes an application ID and a job ID.

In step S<b>215 , the notification unit 125 included in the service providing system 10 receives the notification request to the developer from the device 30 . Next, the notification unit 125 generates a URL for opening the job information browsing screen based on the application ID and job ID included in the notification request.

Subsequently, the notification unit 125 notifies the developer of the generated URL. The developer can be notified by sending an email containing the URL to the developer's email address, or by sending a message containing the URL to the developer's account via SNS (Social Networking Service), etc. You may

≪3. Job information browsing process≫
Next, the job information browsing process in which the developer browses the job information will be described with reference to FIG. 21 . FIG. 21 is a sequence diagram showing an example of job information browsing processing executed by the information processing system 100 according to this embodiment.

In step S301, the browser 210 included in the developer terminal 20 transmits a job information browsing screen acquisition request to the service providing system 10 in response to the developer's operation. Specifically, the developer performs an operation to open the notified URL.

In step S<b>302 , the screen providing unit 111 included in the service providing system 10 receives a job information viewing screen acquisition request from the developer terminal 20 . Next, the screen providing unit 111 acquires screen information representing the job information browsing screen from the screen information storage unit 101 . Subsequently, the screen providing unit 111 transmits the acquired screen information to the developer terminal 20 . In the developer terminal 20, the browser 210 receives screen information representing the job information browsing screen.

In step S<b>303 , the browser 210 of the developer terminal 20 transmits a job information acquisition request to the service providing system 10 . The acquisition request includes a job ID specified by the notified URL.

In the service providing system 10 , the job information browsing unit 112 receives the job information acquisition request from the device 30 . The job information browsing unit 112 requests the job information control unit 124 for job information corresponding to the job ID included in the acquisition request. The job information control unit 124 requests the job management unit 123 for job information corresponding to the job ID.

In step S<b>304 , the job management unit 123 included in the service providing system 10 receives a job information acquisition request from the job information control unit 124 . Next, the job management section 123 acquires job information corresponding to the job ID included in the acquisition request from the job information storage section 104 . Subsequently, the job management section 123 sends the acquired job information to the job information control section 124 .

In step S<b>305 , the job information control unit 124 provided in the service providing system 10 receives job information from the job management unit 123 . Next, the job information control unit 124 extracts parameter information and viewing permission data from the job information.

Subsequently, the job information control unit 124 performs mask processing on the input/output data included in the parameter information based on the browsing permission data. When masking the parameter information, the job information control unit 124 does not mask input/output data for which viewing is permitted in the viewing permission data (that is, browsable="true" is set), and does not mask other input data. Output data is controlled to be masked.

The job information control unit 124 then sends the job information including the masked parameter information to the job information browsing unit 112 . The job information browsing unit 112 transmits the job information received from the job information control unit 124 to the developer terminal 20 .

In step S<b>306 , the browser 210 of the developer terminal 20 receives job information from the service providing system 10 . Next, the browser 210 transmits an application information acquisition request to the service providing system 10 . The acquisition request includes an application ID specified by the notified URL.

In step S<b>307 , the application management unit 121 included in the service providing system 10 receives an application information acquisition request from the developer terminal 20 . Next, the application management unit 121 acquires application information corresponding to the application ID included in the acquisition request from the application information storage unit 102 . Subsequently, the application management unit 121 transmits the acquired application information to the developer terminal 20 .

In step S<b>308 , the browser 210 included in the developer terminal 20 receives application information from the service providing system 10 . Next, the browser 210 displays a job information viewing screen on the display 506 or the like based on the screen information, application information, and job information received from the service providing system 10 .

Here, the job information viewing screen in this embodiment will be described with reference to FIG. 22 . FIG. 22 is a conceptual diagram showing an example of a job information viewing screen according to this embodiment.

As shown in FIG. 22, the job information browsing screen 2400 in this embodiment has a flow display field 2401 and an input/output data display field 2402. FIG. The input/output data display field 2402 has an input parameter display field 2403 , an input file display field 2404 , a download button 2405 , an output parameter display field 2406 , an output file display field 2407 and a download button 2408 .

In the flow display field 2401, components included in the flow are displayed in order of execution. When any component is selected in the flow display field 2401, input/output data related to the selected component is displayed in the input/output data display field 2402. FIG.

The input parameter display column 2403 displays parameters input to the component. An input file display field 2404 displays information about the file input to the component. The output parameter display column 2406 displays parameters output from the component. The output file display column 2407 displays information about files output from the component.

A download button 2405 is a button for downloading the file input to the component. A download button 2405 can be pressed when information about an input file is displayed in the input file display field 2404 . A download button 2408 is a button for downloading the file output from the component. A download button 2408 can be pressed when information about an output file is displayed in the output file display field 2407 .

In this embodiment, the input/output data requested by the developer to be viewed was the input file of the image extraction component 1300 . However, on the job information browsing screen 2400 shown in FIG. 22, the input/output files of the PDF conversion component 1200 can be browsed. In the input source search process, it is specified that the file input to the image extraction component 1300 is the file downloaded from the external storage service A by the file download component 1100 and input to the PDF conversion component 1200. It's for.

Returning to FIG. 21, description will be made. In step S<b>309 , the browser 210 of the developer terminal 20 transmits a file acquisition request to the service providing system 10 in response to the developer's operation on the job information browsing screen 2400 . The acquisition request includes a file ID.

Specifically, the developer presses any download button on the job information browsing screen 2400 . The browser 210 acquires the file ID corresponding to the file corresponding to the pressed download button from the parameter information. The browser 210 then transmits an acquisition request including the file ID to the service providing system 10 .

In step S<b>310 , the file management unit 122 included in the service providing system 10 receives a file acquisition request from the developer terminal 20 . Next, the file management unit 122 acquires from the file storage unit 103 the file corresponding to the file ID included in the acquisition request. Subsequently, the file management unit 122 transmits the acquired file to the developer terminal 20 .

In developer terminal 20 , browser 210 receives the file from service providing system 10 . The browser 210 then displays the received file on the display 506 or the like.

<Effects of the first embodiment>
The information processing system 100 in this embodiment displays the job information browsing screen on the developer terminal based on the browsing permission data representing the input/output data that the user has permitted to browse. At this time, the information processing system 100 according to the present embodiment performs control such that the input/output data that the user has permitted to be viewed can be viewed on the job information viewing screen, and other input/output data cannot be viewed. Therefore, the developer can view the input/output data that the user has permitted to view among the input/output data recorded in the parameter information, thereby facilitating fault analysis and the like.

In addition, the information processing system 100 according to the present embodiment proposes a request for viewing the input/output data related to the component in which the error occurred on the viewing request screen for requesting viewing of the input/output data. Therefore, the developer can appropriately select input/output data necessary for fault analysis and apply for inspection.

Furthermore, the information processing system 100 according to the present embodiment traces the relationship between the input/output data for which viewing has been requested, identifies the input source data of the input/output data, and allows the viewing permission screen for permitting the viewing application, Requests permission to view the identified source data. In addition, the information processing system 100 according to the present embodiment converts the wording representing the input/output data requested to be browsed into content that is easy for the user to understand and displays it. Therefore, the user can appropriately determine whether or not the browsing can be permitted.

[Second embodiment]
In the first embodiment, an application for browsing input/output data related to a component in which an error has occurred is proposed on the browsing application screen. In the second embodiment, the developer can specify arbitrary input/output data and apply for viewing on the viewing application screen.

The information processing system 100 according to the present embodiment will be described below, focusing on differences from the first embodiment.

<Processing procedure of information processing system 100>
Details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method in this embodiment includes: 1. reading application processing and 2. Browsing permission processing is different from that of the first embodiment.

≪1. Browse request process≫
First, the browsing request processing in this embodiment will be described. The viewing application process in this embodiment is the same as in the first embodiment, but the viewing application screen and viewing application data are different from those in the first embodiment.

The viewing application screen according to the present embodiment will be described with reference to FIG. 23 . FIG. 23 is a conceptual diagram showing an example of a viewing application screen in this embodiment.

The viewing application screen in the present embodiment is configured so that the developer can specify arbitrary input/output data and apply for viewing. As shown in FIG. 23 , the viewing application screen 2100 in this embodiment includes an input data input field 2104 in an input data selection field 2102 . In the input data input field 2104, the developer can input a character string representing arbitrary input data. Here, it indicates that the developer has applied for viewing "fileId", which is the input data of the file download component 1100 .

The browsing application data in this embodiment will be described with reference to FIG. 24 . FIG. 24 is a conceptual diagram showing an example of browsing request data in this embodiment.

As shown in FIG. 24 , jobDetail (name: “fileId”) corresponding to the input data entered in the input data entry field 2104 by the developer is added to the browsing application data 3200 in this embodiment.

≪2. Browsing permission process≫
Next, viewing permission processing in this embodiment will be described with reference to FIG. 25 . FIG. 25 is a sequence diagram showing an example of browsing permission processing executed by the information processing system 100 according to this embodiment.

In step S<b>221 , the job information translation unit 114 included in the service providing system 10 sends an application information acquisition request to the application management unit 121 . The acquisition request includes the application ID.

In step S<b>222 , the application management unit 121 included in the service providing system 10 receives the application information acquisition request from the job information translation unit 114 . Next, the application management unit 121 acquires application information corresponding to the application ID included in the acquisition request from the application information storage unit 102 . Subsequently, application management unit 121 sends the acquired application information to job information translation unit 114 .

In step S<b>210 , the job information translation unit 114 included in the service providing system 10 receives application information from the application management unit 121 . Next, the job information translation unit 114 uses predetermined dictionary information to translate the wording included in the browsing application data. Subsequently, the job information translation unit 114 uses the application information received from the application management unit 121 to convert the wording included in the browsing application data. Then, the job information translation unit 114 transmits the converted browsing application data to the device 30 as permission request data.

For the name of the input parameter, a display name can be arbitrarily set for each application. The set display name is displayed on the application execution screen. As such, the user can understand the input parameter being requested to view by the display name. Therefore, the input parameter entered by the developer is converted into the display name included in the application information.

Permission request data in this embodiment will be described with reference to FIG. FIG. 26 is a conceptual diagram showing an example of permission request data in this embodiment.

As shown in FIG. 26, the permission request data 3500 in this embodiment includes a name for display (displayName: "fileId") in jobDetail (name: "fileId") corresponding to the input data entered by the developer. ") is set.

The viewing permission screen in this embodiment will be described with reference to FIG. 27 . FIG. 27 is a conceptual diagram showing an example of a viewing permission screen in this embodiment.

As shown in FIG. 27, the viewing permission screen 2300 in this embodiment has the input data input by the developer added to the viewing permission data selection column 2301 . Also, the added input data is converted into the display name set in the permission request data.

<Effects of Second Embodiment>
The information processing system 100 according to the present embodiment is configured so that the developer can input arbitrary input data on the browsing application screen. Therefore, the developer can apply for inspection of input/output data that does not cause an error but is considered useful for failure analysis.

[Third embodiment]
In the first embodiment, there is only one type of user authority, and the user can enter all parameters that can be entered into the application. In the third embodiment, user authority is classified into general user and administrator user, and the authority of permissible users is restricted for each input/output data requested to be viewed.

The information processing system 100 according to the present embodiment will be described below, focusing on differences from the first embodiment.

<Processing procedure of information processing system 100>
Details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method in this embodiment includes: 1. A viewing application process is different from that of the first embodiment.

≪1. Browse request process≫
First, the browsing request processing in this embodiment will be described with reference to FIG. 28 . FIG. 28 is a sequence diagram showing an example of browsing request processing executed by the information processing system 100 according to this embodiment.

In this embodiment, users who can set parameters to be input to the flow are classified into general users and administrator users. Parameters to be entered in the flow can be entered not only by general users during execution, but also default values can be set in advance by the administrator user. Therefore, in a given flow, there may be a mixture of parameters set by a general user and parameters set by an administrator user.

Also, in this embodiment, it is possible to create an application for personal use and an application shared by tenants. For personal applications, normal users and administrator users can set parameters. For tenant-shared applications, only administrator users can set parameters. Therefore, when applying to view a personal application, it is necessary to determine the authority of the user requesting permission to view each input/output data.

In step S<b>121 , the viewing permission application unit 113 provided in the service providing system 10 receives a registration request for viewing application from the developer terminal 20 . Next, the browsing permission application unit 113 sends an application information acquisition request to the application management unit 121 . The acquisition request includes the application ID.

In step S<b>122 , the application management unit 121 included in the service providing system 10 receives the application information acquisition request from the browsing permission application unit 113 . Next, the application management unit 121 acquires application information corresponding to the application ID included in the acquisition request from the application information storage unit 102 . Subsequently, application management unit 121 sends the acquired application information to browsing permission application unit 113 .

Here, application information in this embodiment will be described with reference to FIG. 29 . FIG. 29 is a conceptual diagram showing an example of application information in this embodiment.

As shown in FIG. 29, the application information 3700 in this embodiment includes settings related to login type (loginType) and input/output data (fileId, to, cc) of each component (filedownload, mail) included in the flow. (name, adminCustomizedOnly, etc.) are described. Note that adminCustomizedOnly is a flag that allows only administrator users to enter parameters.

Returning to FIG. 28, description will be made. In step S<b>123 , the viewing permission application unit 113 included in the service providing system 10 receives application information from the application management unit 121 . Next, the viewing permission application unit 113 classifies the input/output data requested to be viewed in the viewing application data according to the authority of the user who requests permission. That is, the viewing permission application unit 113 converts the viewing request data so that the parameters that can be input only by the administrator user request permission from the administrator user, and the other parameters request permission from general users. .

Here, the browsing application data in this embodiment will be described with reference to FIG. 30 . FIG. 30 is a conceptual diagram showing an example of browsing request data in this embodiment.

As shown in FIG. 30, in the viewing application data 3200 in this embodiment, the input/output data (inputFile, inputParameters) for requesting viewing are classified into two elements, admin and user. admin is input/output data that requests permission for viewing from the administrator user. user is input/output data requesting general user's permission to browse.

In the application information 3700 shown in FIG. 29, fileId has adminCustomizedOnly true, and to and cc have adminCustomizedOnly false. Therefore, in the browsing application data 3200, fileId is classified as admin, and to and cc are classified as user.

<Effects of the third embodiment>
In the information processing system 100 according to the present embodiment, user authority is classified into general user and administrator user, and input/output data that can be input is restricted according to user authority. In addition, the information processing system 100 according to the present embodiment identifies the authority of the user who is permitted to view each piece of input/output data for which viewing has been requested. Therefore, the developer can request permission for viewing from a user having appropriate authority for each piece of input data for which viewing is requested.

[Fourth embodiment]
In the first embodiment, an application for browsing input/output data related to a component in which an error has occurred is proposed on the browsing application screen. In the fourth embodiment, when the input/output data that caused the error can be identified from the execution result information, an application for viewing the identified input/output data is proposed.

The information processing system 100 according to the present embodiment will be described below, focusing on differences from the first embodiment.

<Processing procedure of information processing system 100>
Details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method in this embodiment includes: 1. A viewing application process is different from that of the first embodiment.

≪1. Browse request process≫
First, referring to FIG. 31, the browsing request processing in this embodiment will be described. FIG. 31 is a sequence diagram showing an example of browsing request processing executed by the information processing system 100 according to this embodiment.

In step S<b>130 , the viewing permission application unit 113 provided in the service providing system 10 receives execution result information from the job management unit 123 . Next, the browsing permission application unit 113 identifies the input/output data that caused the error based on the execution result information. Subsequently, the viewing permission application unit 113 transmits information about the identified input/output data (hereinafter also referred to as “error parameter information”) to the developer terminal 20 .

Here, execution result information in this embodiment will be described with reference to FIG. FIG. 32 is a conceptual diagram showing an example of execution result information in this embodiment.

As shown in FIG. 32, in the execution result information 3100 in this embodiment, the error code (message_id) is "io-storageA.invalid_params_fileId".

If you can identify the input/output data that caused the error when generating the execution result information, the structure of the error code will be "io-(component name).(error cause)_(parameter name)". Become. That is, the execution result information 3100 indicates that the file ID (fileId) input to the file download component 1100 (storageA) is invalid.

Therefore, the browsing permission application unit 113 analyzes the structure of the error code recorded in the execution result information, and if the parameter name can be specified, the error parameter information is sent to the developer terminal 20 instead of the error component information. do.

<Effects of the Fourth Embodiment>
When the input/output data that caused the error can be identified, the information processing system 100 in the present embodiment proposes a viewing application for the input/output data that caused the error on the viewing request screen. Therefore, the developer can more appropriately select the input/output data required for failure analysis and apply for viewing.

[Fifth embodiment]
In the first embodiment, an application for browsing input/output data related to a component in which an error has occurred is proposed on the browsing application screen. In the fifth embodiment, when no error occurs but the application does not operate as expected, input/output data to be requested for browsing is proposed.

The information processing system 100 according to the present embodiment will be described below, focusing on differences from the first embodiment.

<Functional Configuration of Information Processing System 100>
First, an example of the functional configuration of the information processing system 100 according to this embodiment will be described with reference to FIG. FIG. 33 is a block diagram illustrating the functional configuration of each device included in the information processing system 100 according to this embodiment.

<<Functional Configuration of Service Providing System 10>>
As shown in FIG. 33, the service providing system 10 in this embodiment further includes a component information storage unit 105 and an inspection parameter storage unit 106 in addition to each unit included in the service providing system 10 in the first embodiment. . The portal service unit 110 according to the present embodiment further includes an inspection parameter registration unit 115 in addition to each unit included in the portal service unit 110 according to the first embodiment. The input/output service unit 120 according to the present embodiment further includes a component management unit 126 and an inspection parameter management unit 127 in addition to the units included in the input/output service unit 120 according to the first embodiment.

The component information storage unit 105 and inspection parameter storage unit 106 are implemented using, for example, the HD 504 shown in FIG. Reading or writing of data stored in the HD 504 is performed via the HDD controller 505, for example.

Note that the component information storage unit 105 and the inspection parameter storage unit 106 may not be provided in the service providing system 10, and may use an external storage device. An example of an external storage device is NAS (Network Attached Storage) or an online storage service.

The component information storage unit 105 stores component information regarding components that can be used in flows. The component information is associated with a component ID that identifies the component.

The inspection parameter storage unit 106 stores inspection parameter information regarding inspection parameters. An inspection parameter is input/output data that proposes an application for browsing for job information in which no error has occurred. A parameter ID that identifies the inspection parameter is associated with the inspection parameter information.

The inspection parameter registration unit 115 transmits component information managed by the component management unit 126 to the developer terminal 20 in response to a request from the developer terminal 20 . Also, the inspection parameter registration unit 115 receives inspection parameter information from the developer terminal 20 . Further, the inspection parameter registration unit 115 requests the inspection parameter management unit 127 to register inspection parameter information.

The component management unit 126 executes writing and reading of component information with respect to the component information storage unit 105 .

The inspection parameter management unit 127 writes and reads inspection parameter information to and from the inspection parameter storage unit 106 .

<Processing procedure of information processing system 100>
Next, the details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method according to this embodiment includes:0. 1. further includes an inspection parameter registration process; The viewing application process is different from that of the first embodiment.

≪Premise≫
First, the flow assumed in this embodiment will be described with reference to FIG. FIG. 34 is a conceptual diagram showing an example of the flow in this embodiment.

As shown in FIG. 34, the flow 1010 in this embodiment executes the file download component 1100, the PDF conversion component 1200, and the mail transmission component 1400 in order.

When the user executes the application including flow 1010, the user enters the destination email address. The mail transmission component 1400 transmits an e-mail attached with the PDF file input from the PDF conversion component 1200 to the e-mail address input by the user.

If the user incorrectly enters the destination e-mail address, the e-mail will not reach the destination e-mail address even if the flow 1010 ends normally. In this case, the user contacts the developer because the application is not working as expected. However, since no error has occurred, it is difficult for the developer to determine which input/output data should be requested for viewing.

≪0. Inspection parameter registration process≫
First, inspection parameter registration processing in which a developer registers inspection parameters will be described with reference to FIG. FIG. 35 is a sequence diagram showing an example of examination parameter registration processing executed by the information processing system 100 according to this embodiment.

In step S401, the browser 210 included in the developer terminal 20 transmits an acquisition request for an examination parameter registration screen to the service providing system 10 according to the developer's operation.

In step S<b>402 , the screen providing unit 111 included in the service providing system 10 receives an acquisition request for an examination parameter registration screen from the developer terminal 20 . Next, the screen providing unit 111 acquires screen information representing the examination parameter registration screen from the screen information storage unit 101 . Subsequently, the screen providing unit 111 transmits the acquired screen information to the developer terminal 20 . In the developer terminal 20, the browser 210 receives screen information representing the inspection parameter registration screen.

In step S<b>403 , the browser 210 included in the developer terminal 20 transmits a component information acquisition request to the service providing system 10 .

In the service providing system 10 , the inspection parameter registration unit 115 receives the component information acquisition request from the developer terminal 20 . The inspection parameter registration unit 115 requests component information from the component management unit 126 .

In step S<b>404 , the component management unit 126 included in the service providing system 10 acquires component information from the component information storage unit 105 . Next, the component management section 126 sends the acquired component information to the inspection parameter registration section 115 . The inspection parameter registration unit 115 transmits the component information received from the component management unit 126 to the developer terminal 20 .

In step S<b>405 , the browser 210 of the developer terminal 20 receives component information from the service providing system 10 . Next, the browser 210 displays an inspection parameter registration screen on the display 506 or the like based on the screen information and component information received from the service providing system 10 .

Here, the inspection parameter registration screen in this embodiment will be described with reference to FIG. FIG. 36 is a conceptual diagram showing an example of an inspection parameter registration screen in this embodiment.

As shown in FIG. 36, the inspection parameter registration screen 2500 in this embodiment has a component selection column 2501, a parameter selection column 2502 and a send button 2509.

A component selection field 2501 displays components included in the component information in a selectable manner. Input parameters of the component selected in the component selection field 2501 are displayed in the parameter selection field 2502 in a selectable manner.

Returning to FIG. 35, description will be made. In step S<b>406 , the browser 210 of the developer terminal 20 generates inspection parameter information according to the developer's operation on the inspection parameter registration screen 2500 .

Specifically, the developer selects a component whose inspection parameters are to be registered in the component selection field 2501 and selects input parameters for the component in the parameter selection field 2502 . The developer then presses a send button 2509 on the inspection parameter registration screen 2500 . The browser 210 generates inspection parameter information representing input parameters selected in the parameter selection field 2502 .

In step S<b>407 , the browser 210 provided in the developer terminal 20 transmits a registration request for inspection parameters to the service providing system 10 . The registration request includes inspection parameter information.

In the service providing system 10, the inspection parameter registration unit 115 receives the inspection parameter registration request. The inspection parameter registration unit 115 sends the inspection parameter information included in the registration request to the inspection parameter management unit 127 .

In step S<b>408 , the inspection parameter management unit 127 included in the service providing system 10 receives inspection parameter information from the inspection parameter registration unit 115 . Next, the inspection parameter management unit 127 stores the inspection parameter information in the inspection parameter storage unit 106. FIG. Subsequently, the inspection parameter management unit 127 sends the inspection parameter registration result to the inspection parameter registration unit 115 . The inspection parameter registration unit 115 transmits the inspection parameter registration result received from the inspection parameter management unit 127 to the developer terminal 20 .

≪1. Browse request process≫
Next, referring to FIG. 37, the browsing request processing according to the present embodiment will be described. FIG. 37 is a sequence diagram showing an example of browsing request processing executed by the information processing system 100 according to this embodiment.

In step S<b>141 , the viewing permission application unit 113 provided in the service providing system 10 receives execution result information from the job management unit 123 . Next, the viewing permission application unit 113 determines whether an error has occurred based on the execution result information. In this embodiment, the description will be continued on the assumption that no error has occurred.

In step S<b>142 , the viewing permission application unit 113 provided in the service providing system 10 sends a test parameter acquisition request to the test parameter management unit 127 .

In step S<b>143 , the inspection parameter management unit 127 provided in the service providing system 10 receives the inspection parameter acquisition request from the viewing permission application unit 113 . Next, the inspection parameter management unit 127 acquires inspection parameter information from the inspection parameter storage unit 106 . Subsequently, the inspection parameter management unit 127 sends the acquired inspection parameter information to the viewing permission application unit 113 .

In step S<b>144 , the viewing permission application unit 113 included in the service providing system 10 receives parameter information from the inspection parameter management unit 127 . Next, the viewing permission application unit 113 determines whether or not there is input/output data included in the parameter information that matches the inspection parameter included in the inspection parameter information. Here, the explanation is continued on the assumption that there is input/output data that matches the inspection parameters.

In step S<b>145 , the viewing permission application unit 113 included in the service providing system 10 sends an application information acquisition request to the application management unit 121 . The acquisition request includes the application ID.

In step S<b>146 , the application management unit 121 included in the service providing system 10 receives the application information acquisition request from the browsing permission application unit 113 . Next, the application management unit 121 acquires application information corresponding to the application ID included in the acquisition request from the application information storage unit 102 . Subsequently, application management unit 121 sends the acquired application information to browsing permission application unit 113 .

In step S<b>147 , the browsing permission application unit 113 included in the service providing system 10 receives application information from the application management unit 121 . Next, the viewing permission application unit 113 uses the application information to determine whether or not the method of inputting input/output data that matches the examination parameter corresponds to a predetermined method.

For example, when a user inputs input data as text, there is a high possibility that a problem will occur due to an input error. Therefore, if the input/output data that matches the inspection parameters is text input, it is recommended to propose an application for viewing the input/output data. The predetermined input method is not limited to text input, and any input method that is prone to input errors may be set.

Based on the determination result, the viewing permission application unit 113 generates candidate parameter information representing input/output data for proposing a request for viewing. Next, the viewing permission application unit 113 transmits the generated candidate parameter information to the developer terminal 20 .

In step S<b>111 , the browser 210 provided in the developer terminal 20 receives candidate parameter information from the service providing system 10 . Based on the candidate parameter information, the browser 210 then suggests input/output data that should be requested for viewing. Specifically, the browser 210 automatically selects the input/output data represented in the candidate parameter information among the input/output data displayed in the input data selection column 2102 or the output data selection column 2103 on the browsing application screen 2100. select.

<Effects of the Fifth Embodiment>
The information processing system 100 according to the present embodiment proposes a request for viewing of test parameters registered in advance on the viewing request screen when no error has occurred. Therefore, even if no error has occurred, the developer can appropriately select input/output data useful for investigation and apply for viewing.

[Sixth Embodiment]
In the first embodiment, an example has been described in which, when the input/output data requested to be browsed is a file, the relationship of the input/output data is traced back to identify the input source file. In the sixth embodiment, an example will be described in which, when the input/output data requested to be browsed is a parameter, the relationship of the input/output data is traced back to identify the input source parameter.

The information processing system 100 according to the present embodiment will be described below, focusing on differences from the first embodiment.

<Processing procedure of information processing system 100>
First, the details of the information processing method executed by the information processing system 100 according to the present embodiment will be described. The information processing method in this embodiment includes: 1. reading application processing and 2. Browsing permission processing is different from that of the first embodiment.

≪Premise≫
First, the flow assumed in this embodiment will be described with reference to FIG. FIG. 38 is a conceptual diagram showing an example of the flow in this embodiment.

As shown in FIG. 38, the flow 1020 in this embodiment executes the file folder list acquisition component 1500A, the file folder list acquisition component 1500B, the string concatenation component 1600, and the mail transmission component 1400 in order.

The file folder list acquisition component 1500A acquires from the external storage service A a list of folders and files directly under the folder specified by the user. The file folder list acquisition component 1500B acquires from the external storage service B a list of folders and files directly under the folder specified by the user. The string concatenation component 1600 concatenates multiple input strings.

When the user executes the application including the flow 1020, the user inputs the folder ID for identifying the folder of the external storage service A, the folder ID for identifying the folder of the external storage service B, and the e-mail address of the destination.

When the user executes the application including the flow 1020, the service providing system 10 acquires a list of folders and files directly under the folder specified by the user from each of the external storage service A and the external storage service B, and concatenates them with a character Send an email with the columns to the destination email address.

FIG. 39 is a conceptual diagram showing an example of output data output from flow 1020. As shown in FIG. As shown in FIG. 39, in output data 3800, file folder list information (StorageA) obtained from external storage service A and file folder list information (StorageB) obtained from external storage service B are combined. string is described.

Assume that the user requests the developer to analyze the failure. When the developer browsed the job information when the application was executed, the file folder list acquisition component 1500A and the file folder list acquisition component 1500B were successful, but an error occurred in the character string concatenation component 1600. I found out. The execution result information included in the job information records that the error that occurred is "an error caused by internal processing".

≪1. Browse request process≫
Next, referring to FIG. 40, a description will be given of a viewing application process in which a developer requests viewing of input/output data. FIG. 40 is a sequence diagram showing an example of browsing request processing executed by the information processing system 100 according to this embodiment.

In step S111, the browser 210 provided in the developer terminal 20 proposes input/output data to be requested for viewing based on the error component information.

FIG. 41 is a conceptual diagram showing an example of a viewing application screen in this embodiment. As shown in FIG. 41, the input data (args) of the character string combination component is automatically selected on the viewing application screen 2100 in this embodiment.

Returning to FIG. 40, description will be made. In step S<b>112 , the browser 210 of the developer terminal 20 generates viewing application data according to the developer's operation on the viewing application screen 2100 . Next, the browser 210 transmits a registration request for viewing application to the service providing system 10 . The registration request includes the generated browsing application data.

In step S<b>151 , the viewing permission application unit 113 provided in the service providing system 10 receives a registration request for viewing application from the developer terminal 20 . Next, the browsing permission application unit 113 sends an application information acquisition request to the application management unit 121 . The acquisition request includes the application ID.

In step S<b>152 , the application management unit 121 included in the service providing system 10 receives the application information acquisition request from the browsing permission application unit 113 . Next, the application management unit 121 acquires application information corresponding to the application ID included in the acquisition request from the application information storage unit 102 . Subsequently, application management unit 121 sends the acquired application information to browsing permission application unit 113 .

Here, application information in this embodiment will be described with reference to FIG. 42 . FIG. 42 is a conceptual diagram showing an example of application information in this embodiment.

As shown in FIG. 42, application information 3700 in this embodiment includes "userInputParameters" representing parameters input by the user and "defaultParameters" representing parameters input by default. folderId of getItemListStorageA is a folder ID for acquiring file folder list information of external storage service A. folderId of getItemListStorageB is a folder ID for acquiring file folder list information of external storage service B. to of sendMail is the destination email address.

"(component name).IOResult" included in args of concatString is a placeholder representing the output result of the component. By setting in this way, the output result of one component can be input to another component. That is, the application information 3700 indicates that the output result of the file folder list acquisition component 1500A and the output result of the file folder list acquisition component 1500B are input to the character string concatenation component 1600. FIG.

Returning to FIG. 40, description will be made. In step S<b>153 , the viewing permission application unit 113 included in the service providing system 10 receives application information from the application management unit 121 . Next, based on the application information, the viewing permission application unit 113 traces the relationship of the input/output data for which viewing has been requested, and identifies the input source data from which the input/output data was input to the flow. Subsequently, the viewing permission application unit 113 adds the identified input data to the viewing application data.

Here, the input source search processing in this embodiment will be described with reference to FIG. FIG. 43 is a flowchart showing an example of input source search processing in this embodiment.

In step S 153 - 1 , browsing permission application section 113 acquires application information from application management section 121 . Hereinafter, the application information is assumed to be the application information 3700 shown in FIG.

In step S153-2, the viewing permission application unit 113 identifies the component for which viewing has been requested. Here, concatString is specified because the input data (args) of the string concatenation component 1600 is requested to be viewed.

In step S153-3, the browsing permission application unit 113 acquires input parameters of the specified component. Here, "getItemListStorageA.IOResult" and "getItemListStorageB.IOResult" are acquired.

In step S153-4, the viewing permission application unit 113 determines whether or not the obtained input parameter includes IOResult. If there is an IOResult (YES), the process proceeds to step S153-5. If there is no IOResult (NO), the process proceeds to step S153-6. Here, since "getItemListStorageA.IOResult" and "getItemListStorageB.IOResult" are acquired, the process proceeds to step S153-5.

In step S153-5, the viewing permission application unit 113 identifies the component that outputs the IOResult. Here, "getItemListStorageA" and "getItemListStorageB" are specified.

In step S153-3, which is executed again, the browsing permission application unit 113 acquires the input parameters of "getItemListStorageA" and "getItemListStorageB". Here, the "folderId" of "getItemListStorageA" and the "folderId" of "getItemListStorageB" are acquired.

In step S153-4, which is executed again, the browsing permission application unit 113 proceeds to step S153-6 because there is no IOResult in the acquired input parameters.

In step S153-6, the viewing permission application unit 113 identifies the current input data of the component as the input source data, and terminates the process. That is, the "folderId" input to the file folder list acquisition component 1500A and the "folderId" input to the file folder list acquisition component 1500B are specified as input source data.

Here, the browsing application data in this embodiment will be described with reference to FIG. 44 . FIG. 44 is a conceptual diagram showing an example of browsing request data in this embodiment.

As shown in FIG. 44, in the browse application data 3200 in this embodiment, relatedParameters including an inputParameter named "folderId" are added to jobDetail corresponding to "getItemListStorageA" and jobDetail corresponding to "getItemListStorageA". It is

≪2. Browsing permission process≫
Next, the browsing permission processing in this embodiment will be described. The viewing permission process in this embodiment is the same as in the first embodiment, but the viewing permission screen is different from that in the first embodiment.

The viewing permission screen in this embodiment will be described with reference to FIG. FIG. 45 is a conceptual diagram showing an example of a viewing permission screen in this embodiment.

As shown in FIG. 45, the viewing permission screen 2300 in the present embodiment has a viewing permission data selection field 2301 that includes "file folder list information directly under the folder specified by storageAFolderId" specified as the input source data. and "file folder list information directly under the folder specified by storageBFolderId" are displayed. These wordings are obtained by converting "folderId" of "getItemListStorageA" and "folderId" of "getItemListStorageB" into contents that are easy for the user to understand, based on application information and dictionary information.

The displayName described in the viewing application data 3200 shown in FIG. 44 is the name displayed on the application execution screen displayed on the operation panel 940 of the device 30 when executing the application.

FIG. 46 is a conceptual diagram showing an example of an application execution screen in this embodiment. As shown in FIG. 46 , the application execution screen 2600 in this embodiment has a parameter input field 2601 indicated by storageAFolderId, a parameter input field 2602 indicated by storageBFolderId, and an execute button 2609 .

Since the user uses the application execution screen 2600 when executing the application, the user can understand the content of the request for permission to view storageAFolderId and storageBFolderId on the viewing permission screen 2300 .

<Effects of the sixth embodiment>
The information processing system 100 according to the present embodiment, when the input/output data for which viewing is requested is a parameter, traces the relationship of the input/output data to identify the parameter input by the user, and performs viewing of the specified input data. Register the browsing request data to apply. Therefore, the user can appropriately determine whether or not the browsing can be permitted.

[supplement]
In each of the embodiments described above, the service providing system 10 is an example of an information processing device. The developer terminal 20 is an example of a first information processing terminal. Device 30 is an example of a second information processing terminal. Parameter information is an example of log information. The execution result information is an example of second log information. Browsing permission data is an example of control information. Inspection parameter information is an example of second control information. The viewing permission application unit 113 is an example of a receiving unit. Browser 210 is an example of a screen display unit. Browser 310 is an example of a transmitter.

Each function of the embodiments described above may be implemented by one or more processing circuits. Here, the "processing circuit" in this specification means a processor programmed by software to perform each function, such as a processor implemented by an electronic circuit, or a processor designed to perform each function described above. ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and devices such as conventional circuit modules.

The devices described in the examples are merely representative of one of several computing environments for implementing the embodiments disclosed herein. In some embodiments, service delivery system 10 includes multiple computing devices, such as server clusters. Multiple computing devices are configured to communicate with each other over any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein. Similarly, external service system 40 may include multiple computing devices configured to communicate with each other.

Further, service providing system 10 and external service system 40 can be configured to share the disclosed processing steps in various combinations. For example, processes performed by a given unit may be performed by external service system 40 . Similarly, the functionality of a given unit can be performed by external service system 40 . Further, each element of the service providing system 10 and the external service system 40 may be integrated into one server device, or may be divided into a plurality of devices.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to these embodiments, and various modifications or Change is possible.

100 Information processing system 10 Service providing system 101 Screen information storage unit 102 Application information storage unit 103 File storage unit 104 Job information storage unit 105 Component information storage unit 106 Inspection parameter storage unit 110 Portal service unit 111 Screen providing unit 112 Job information browsing unit 113 View permission application unit 114 Job information translation unit 115 Inspection parameter registration unit 120 Input/output service unit 121 Application management unit 122 File management unit 123 Job management unit 124 Job information control unit 125 Notification unit 126 Component management unit 127 Inspection parameter management unit 20 Developer terminal 210 Browser 30 Device 310 Browser

JP 2020-119047 A

Claims (10)

An information processing device capable of communicating with a first information processing terminal and a second information processing terminal via a network,
a management unit that stores log information that records input/output data related to a series of processes in a storage unit;
a receiving unit that receives control information permitting viewing of the input/output data from the second information processing terminal;
a screen providing unit configured to transmit, to the first information processing terminal, screen information representing a viewing screen displaying the log information in which the input/output data, which is not permitted to be viewed based on the control information, is displayed;
Information processing device. The information processing device according to claim 1,
The screen providing unit transmits screen information representing an application screen for selecting the input/output data to be viewed, to the first information processing terminal, and selects the input/output data to be permitted to be viewed. transmitting screen information representing a permission screen to the second information processing terminal;
Information processing equipment. The information processing device according to claim 2,
The management unit stores second log information that records execution results of the processing in the storage unit,
The application screen proposes an application for viewing the input/output data related to the process in which an error has occurred;
Information processing equipment. The information processing device according to claim 3,
the permission screen requests permission to view other input/output data associated with the input/output data for which viewing is requested;
Information processing equipment. The information processing device according to claim 4,
The permission screen selects the input/output data for which viewing permission is requested according to the authority of the user using the second information processing terminal.
Information processing equipment. The information processing device according to claim 2,
The receiving unit receives second control information representing the input/output data selected in advance from the first information processing terminal,
the application screen proposes an application for viewing the input/output data represented in the second control information;
Information processing equipment. The information processing device according to any one of claims 2 to 6,
the permission screen converts and displays the wording representing the input/output data for which the viewing has been requested;
Information processing equipment. An information processing system in which a first information processing terminal, a second information processing terminal, and an information processing device can communicate via a network,
The information processing device is
a management unit that stores log information that records input/output data related to a series of processes in a storage unit;
a receiving unit that receives control information permitting viewing of the input/output data from the second information processing terminal;
a screen providing unit configured to transmit, to the first information processing terminal, screen information representing a viewing screen displaying the log information in which the input/output data, which is not permitted to be viewed based on the control information, is displayed;
with
The second information processing terminal includes a transmission unit that transmits the control information to the information processing device,
The first information processing terminal includes a screen display unit that displays the browsing screen,
Information processing system. A computer capable of communicating with the first information processing terminal and the second information processing terminal via a network,
a management procedure for storing log information in which input/output data relating to a series of processes are recorded in a storage unit;
a reception procedure for receiving, from the second information processing terminal, control information permitting viewing of the input/output data;
a screen providing procedure for transmitting to the first information processing terminal screen information representing a viewing screen displaying the log information in which the input/output data, which is not permitted to be viewed based on the control information, is displayed;
Information processing method that performs A computer capable of communicating with the first information processing terminal and the second information processing terminal via a network,
a management procedure for storing log information in which input/output data relating to a series of processes are recorded in a storage unit;
a reception procedure for receiving, from the second information processing terminal, control information permitting viewing of the input/output data;
a screen providing procedure for transmitting to the first information processing terminal screen information representing a viewing screen displaying the log information in which the input/output data, which is not permitted to be viewed based on the control information, is displayed;
program to run the

Images