JP2024172980A - Program, method, and information processing device - Google Patents

Abstract

To allow a user who uses a plurality of web services to easily check information which the user should check in each of the web service.SOLUTION: A program causes a computer to execute: obtaining user information from a user; obtaining registration information indicating a plurality of registration web services in which the user is registered from among a plurality of web services based on the user information; obtaining, based on the registration information, task information that is associated with the user in each of at least one or more registration web services among the plurality of registration web services and that indicates a task which the user should do; and generating screen information of a task display screen for presenting the task to the user based on the task information.SELECTED DRAWING: Figure 2

Description

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

In organizations such as companies, various application and approval tasks are performed, such as expense applications, vacation applications, and procedure approvals. There are web services that allow these tasks to be performed via a cloud network over the Internet. There are multiple web services depending on the type of task, and a portal site may be used to access each web service. Patent Document 1 describes a portal system that aims to prevent the occurrence of information leaks as one technology for using a portal site.

JP 2018-55225 A

When a user uses multiple web services, the information communicated to the user by each web service must be understood by the user by logging in to each web service and viewing the screens provided by each web service individually. In this way, if the user has to check the web page of each service individually, it may be less convenient for the user, and they may miss things or applications.

The present invention aims to enable users who use multiple web services to easily check the information they should check in each web service.

A program according to one aspect of the present invention causes a computer to perform the following operations: acquire user information from a user; acquire registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services based on the user information; acquire task information indicating tasks to be performed by the user that are associated with the user in at least one of the plurality of registered web services based on the registration information; and generate screen information for a task display screen that presents tasks to the user based on the task information.

According to this aspect, even if a user is registered with multiple web services, information from the registered web services in which the user is registered can be displayed on the task display screen. This allows the information that the user needs to check to be displayed in a list, allowing the user to easily check the information that they need to check.

In the above aspect, generating screen information may include generating screen information having an approval task area in which approval tasks that require user approval are displayed.

According to this aspect, approval tasks can be displayed separately on the task display screen, improving user convenience.

In the above aspect, the approval tasks may be arranged in the approval task area in a first arrangement order based on the appropriability range of the approval tasks associated with the user.

According to this aspect, tasks can be arranged on the task display screen according to the user's range of approval. For example, if a user is responsible for approving accounting within an organization, accounting-related tasks can be displayed with priority. This allows the user to properly check the information that they need to check.

In the above aspect, the approval tasks may be arranged in the approval task area in a second arrangement order based on the time when the user information was acquired and the deadline of the task.

According to this aspect, for example, if a deadline is set for a task, the tasks that need to be completed by the deadline can be displayed with priority. This allows the user to properly check the information that they need to check.

In the above aspect, generating the screen information may include generating screen information for a task display screen that is associated with the task information and includes connection information used to connect to a web service that corresponds to the task information.

According to this aspect, the user can access the web service corresponding to the task through the task display screen, improving convenience for the user.

In the above aspect, the computer may further be caused to acquire a user's operation input for a target web service that is to be operated by the user among the multiple registered web services, and transmit operation information based on the operation input to a target server that provides the target web service.

According to this aspect, operation information can be sent to the target server through the task display screen in response to operation input. This eliminates the need for the user to access individual web services and perform operations, improving user convenience.

In the above aspect, the computer may further be caused to acquire response information indicating a response to the operation information from the target server, and generating the screen information may include updating the screen information based on the response information.

According to this aspect, the user can check whether or not his/her operation was performed in the web service to which the operation information was transmitted. This improves user convenience.

In the above aspect, the computer may further be caused to acquire request information regarding a requested operation that the user requests to be executed in one of the multiple registered web services, identify a web service among the multiple registered web services that can execute the requested operation based on the request information, and present to the user information on the web services that can execute the requested operation.

According to this aspect, information on web services that can execute the requested operation is provided to the user in response to request information indicating the operation that the user requests to be executed. This makes it possible to introduce web services that meet the user's needs when the user uses multiple web services, improving user convenience.

A method according to another aspect of the present invention includes a computer acquiring user information from a user, acquiring registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services based on the user information, acquiring task information indicating tasks to be performed by the user that are associated with the user in each of at least one of the plurality of registered web services based on the registration information, and generating screen information of a task display screen that presents the tasks to the user based on the task information.

An information processing device according to another aspect of the present invention includes a user information acquisition unit that acquires user information from a user, a registration information acquisition unit that acquires, based on the user information, registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services, a task information acquisition unit that acquires, based on the registration information, task information indicating tasks to be performed by the user that are associated with the user in at least one of the plurality of registered web services, and a screen information generation unit that generates, based on the task information, screen information for a task display screen that presents tasks to the user.

According to the present invention, a user who uses multiple web services can easily check the information that the user should check in each web service.

1 is a schematic diagram of a web service providing system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an overview of processing in a web service providing system. FIG. 2 is a block diagram of a server intermediation device according to the present embodiment. 4 is an example of user information according to the embodiment. 11 is a diagram illustrating an example of a process in the server intermediation device according to the embodiment. FIG. 13 is an example of a task display screen according to the embodiment. 13 is another example of a task display screen according to the embodiment. 13 is a diagram illustrating an example of another process in the server intermediation device according to the embodiment. FIG. 13 is a diagram illustrating an example of another process in the server intermediation device according to the embodiment. FIG. 13 is an example of a required operation acquisition screen according to the embodiment.

A preferred embodiment of the present invention will be described with reference to the attached drawings. In each drawing, the same reference numerals are used to denote the same or similar configurations.

Figure 1 shows a schematic diagram of a web service providing system 10 according to this embodiment. The web service providing system 10 has a server intermediary device 101, user terminals 201a, 201b, and 201c, and web service providing servers 301a, 301b, and 301c. These terminals, devices, and servers are communicatively connected via a network N. Note that although there are multiple user terminals and web service providing servers, such as user terminals 201a, 201b, and 201c, and web service providing servers 301a, 301b, and 301c, they will be simply referred to as user terminal 201 and web service providing server 301 when there is no need to distinguish between them.

The server intermediary device 101 is a server that mediates the sending and receiving of information from multiple web services for a user who uses multiple web services through a user terminal 201. The configuration of the server intermediary device 101 will be described later.

The user terminal 201 is a terminal operated by a user, and is, for example, an information processing device such as a personal computer, smartphone, or tablet terminal that stores browsing software that can access the server intermediary device 101 and the web service providing server 301 via the network N.

The web service providing servers 301 are server devices that actually provide web services according to various functions. Each of the web service providing servers 301 has its own functions, such as attendance management and expense reporting.

With reference to Figure 2, an overview of the processing in the web service providing system 10 is described.

In step (A) of FIG. 2, a user (user A) accesses the server intermediary device 101 through a user terminal 201. At this time, user A transmits to the server intermediary device 101 user information such as an ID and password required for the user to access the server intermediary device 101 and the web service providing server 301. The server intermediary device 101 verifies the access and accepts login from the user.

Based on the user information, the server intermediary device 101 identifies registered web services that are stored in the server intermediary device 101 and are available to the user. In the example of FIG. 2, it is shown that user A can use services including service A and service B.

In step (B), the server intermediation device 101 accesses the web service providing server 301 that provides the registered web service, and obtains task information indicating the tasks associated with the user from the web service providing server 301. In the example of FIG. 2, for user A, the server intermediation device 101 accesses each of the web service providing server 301a that provides service A and the web service providing server 301b that provides service B, and obtains task information for the tasks associated with user A.

In step (C), the server intermediary device 101 generates screen information for a task display screen that displays the tasks that the user must handle based on the acquired task information, and transmits the screen information to the user. In the example of FIG. 2, a task display screen that displays tasks 1a, 1b, 2a, and 2b associated with the web service providing server 301a and the web service providing server 301b, respectively, is shown to user A.

Similarly, for user B, in step (D), user information for user B is sent to the server intermediary device 101, in step (B), task information is acquired from the web service providing server 301 in which user B is registered, and in step (E), the task display screen is displayed.

The components of the server intermediary device 101 will be described with reference to FIG. 3. The web service providing system 10 has a communication unit 1011, a memory unit 1012, a user information acquisition unit 1013, a registration information acquisition unit 1014, a task information acquisition unit 1015, a screen information generation unit 1016, an operation input acquisition unit 1017, an operation information transmission unit 1018, a request information acquisition unit 1019, and a web service presentation unit 1020.

Each part of the server intermediary device 101 can be realized in the server device by a communication device, a storage device, and a processor that executes a program stored in the storage device.

The communication unit 1011 controls communication between the server intermediation device 101 and devices external to the server intermediation device 101, including the user terminal 201 and the web service providing server 301.

The memory unit 1012 acquires various information used for processing in the server intermediary device 101. Figure 4 shows an example of user management information stored in the memory unit 1012.

The user management information has the fields "User ID", "Registered Web Services", and "Display Settings". The "User ID" field stores identification information that identifies the user. The "Registered Web Services" field stores registered web services that are registered as web services that the user can use. The "Display Settings" field stores information that sets the display mode of tasks on the task display screen.

In the example of Figure 4, a user with a "user ID" of ID001 has "registered web services" that include service A and service B, and a user with a "user ID" of ID002 has "registered web services" that include service B and service C. For example, service A is a service that manages the user's attendance, service B is a service that manages the user's expenses, and service C is a service that manages the user's salary. Other types of services include a human resources management service, a contract management service, and a year-end tax adjustment service.

In addition, the "display settings" for users A and B are stored as settings A and B, respectively. The display settings are set, for example, based on the work content of each user. For example, if the user is in charge of labor management, the display settings are set so that tasks related to labor management are preferentially displayed on the task display screen described below. Alternatively, if the user is in charge of accounting, the display settings are set so that tasks related to accounting, such as expense application approval, are preferentially displayed on the task display screen. Furthermore, the display settings may be set so that among approval tasks, tasks with an upcoming approval deadline are preferentially displayed. Here, preferential display is, for example, a display that makes it easier for the user to see the tasks on the screen, and includes displaying the target task at the top of the task list and highlighting the target task.

The user information acquisition unit 1013 acquires user information from the user to access the server intermediary device 101 and the web service providing server 301. The user information includes, for example, a user ID and a login password.

The registration information acquisition unit 1014 acquires, based on the user information, from the storage unit 1012, registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services.

Based on the registration information, the task information acquisition unit 1015 acquires task information indicating tasks to be performed by the user that are associated with the user in at least one of the multiple registered web services. In the example of FIG. 3, the task information acquisition unit 1015 acquires task information for user A with user ID ID001 from the web service providing server 301 that provides services A and B, and acquires task information for user B with user ID ID002 from the web service providing server 301 that provides services B and C.

The screen information generating unit 1016 generates screen information for a task display screen that presents the task to the user based on the task information. The task display screen will be described later. The screen information generating unit 1016 may display a link for connecting to a web service corresponding to the task together with the task. The screen information generating unit 1016 may also generate screen information for the task display screen according to the display settings for each user stored in the storage unit 1012.

The operation input acquisition unit 1017 acquires a user's operation input for a target web service on which the user is to perform an operation among a plurality of registered web services. Specifically, the operation input acquisition unit 1017 acquires an operation input for a service provided by one of the web service providing servers 301 via a task display screen.

The operation information transmission unit 1018 transmits operation information based on the operation input to the operation target server that provides the operation target web service. Furthermore, the operation information transmission unit 1018 acquires response information indicating a response to the operation information from the operation target server.

The request information acquisition unit 1019 acquires request information regarding a request operation that the user requests to be performed in one of multiple registered web services. Specifically, the request information acquisition unit 1019 acquires information indicating the operation that the user wishes to perform, for example, information input in natural language such as "I would like to apply for vacation."

The web service presentation unit 1020 identifies a web service that can execute the requested operation from among multiple registered web services based on the request information, and presents information on the web services that can execute the requested operation to the user. Specifically, the web service presentation unit 1020 interprets the user's operation request, which is input as a sentence, using natural language processing, and identifies an appropriate web service.

The processing in the server intermediary device 101 will be described with reference to FIG. 5. In step S501, the user information acquisition unit 1013 acquires user information corresponding to a login operation from the user.

In step S502, the registration information acquisition unit 1014 identifies registered web services available to the user based on the user information.

In step S503, the task information acquisition unit 1015 accesses the web service providing server 301 that provides the registered web service.

In step S504, the task information acquisition unit 1015 acquires task information associated with the user in the registered web service.

In step S505, the screen information generation unit 1016 generates screen information for a task display screen that displays task information.

Figure 6 shows an example of a task display screen 601 displayed to user A. The task display screen 601 has an attendance menu display area 6011 and a task display area 6012. The task display screen 601 functions as a personal page that is displayed individually according to the registered web services of each individual user.

The attendance menu display area 6011 has a display field 60111, a clock-in button 60112, a clock-out button 60113, and a leave application button 60114. The attendance menu display area 6011 is a display area that enables collaboration with Service A, which is a registered web service for User A and is related to attendance management.

The current time is displayed in display field 60111. The clock-in button 60112, clock-out button 60113, and vacation application button 60114 are operation areas that, when selected by user A, enable clock-in processing, clock-out processing, and vacation application via the operation information transmission unit 1018 described below.

The task display area 6012 includes a list of tasks waiting for approval 60121, a list of returned tasks 60122, and a create new application form button 60123.

The list of tasks waiting for approval 60121 displays the tasks that require approval among the tasks assigned to user A in each registered web service. Tasks displayed in the list of tasks waiting for approval 60121 have fields for the service name in which the task is stored, the date of approval application, the applicant user who made the application, the application content, and confirmation of details.

The sent back task list 60122 displays tasks that have been applied for by user A through each web service and that have been sent back by other approval users. Tasks displayed in the sent back task list 60122 have fields for the service name, application date, approval user who will approve the task, application content, and detailed confirmation. In both the waiting for approval task list 60121 and the sent back task list 60122, the user can access each registered web service by selecting the part marked "Details" in the detailed confirmation.

In addition, the display order of tasks in the list of tasks waiting for approval 60121 can be changed based on the display settings stored in the memory unit 1012.

In this way, the user can check approval tasks and returned tasks for multiple web services at a glance through the task display screen 601. This reduces the occurrence of missed confirmations and missed applications, and allows the organization to be run more appropriately.

Figure 7 shows an example of a task display screen 701 displayed to user B. The task display screen 701 has a task display area 7012. The task display area 7012 has the same functions as the task display screen 6012, and has a list of tasks waiting for approval 70121, a list of tasks sent back 70122, and a create new application button 70123. In addition, the task display screen 701 does not have an area corresponding to the attendance menu display area 6011 in the task display screen 601. This is because user B is not registered as a user who can use service A related to attendance management, as shown in Figure 4. Tasks related to user B's registered web services are displayed on user B's task display screen 701. In this way, the server intermediary device 101 can present each user with a screen corresponding to each user's registered web service.

The waiting task list 70121 displays tasks that require approval among the tasks assigned to user B in each registered web service. The sent back task list 70122 displays tasks that have been applied for by user B through each web service and have been sent back by other approving users. In both the waiting task list 70121 and the sent back task list 70122, the user can access each registered web service by selecting the part marked "Details" in the details confirmation. In addition, the display order of tasks in the waiting task list 70121 can be changed based on the display settings stored in the memory unit 1012.

Referring to FIG. 8, the operation of the web service providing server 301 by the server intermediary device 101 through the task display screen 601 will be described. Here, the case where user A uses service A related to attendance management will be described as an example.

In step S801, the operation input acquisition unit 1017 acquires a user operation on the task display screen 601. The user operation is, for example, the selection of the clock-in button 60112, the clock-out button 60113, or the vacation request button 60114.

In step S802, the operation information transmission unit 1018 accesses the operation target server that provides the operation target web service based on the user operation. For example, the operation information transmission unit 1018 accesses the web service providing server 301 that provides the attendance management service.

In step S803, the operation information transmission unit 1018 transmits operation information to the operation target server. For example, when the attendance button 60112 is selected, the operation information is information instructing the web service providing server 301 to change the status of the attendance information to attendance.

In step S804, the operation information transmission unit 1018 acquires response information from the operation target server. The response information is, for example, information indicating whether or not processing based on the operation information has been completed.

In step S805, the screen information generating unit 1016 updates the display on the task display screen 601. For example, the screen information generating unit 1016 updates the task display screen 601 so as to display a message indicating that the operation has been completed on the task display screen 601.

User A can also apply for leave by operating the leave application button 60114. In this case, when the operation of the leave application button 60114 is acquired in step S801, the server intermediary device 101 causes the user terminal 201 to display a separate leave application input screen for the service on the user terminal 201. User A can apply for leave by inputting the leave category, period, and comments via the displayed input screen, and operating the application button provided on the input screen. When a leave application is made, the operation information sending unit 1018 sends operation information related to the leave application to the target server. Note that the leave application button 60114 does not have to be provided on the task display screen 601, and leave application procedures may be made only through a separate attendance management web service.

The process described in FIG. 8 allows users to operate each web service providing server 301 via the task display screen 601, which allows users to check tasks in a list while operating the web service providing server 301, improving user convenience.

The intermediary server 101 allows each user to check the task display screen (my page) of each user, which occurs in each web service and is associated with the user, and to execute corresponding processing for the task. Specifically, for example, in the case of a web service related to attendance management, each user logs in to an individual service page through the task display screen, and is able to operate detailed functions such as analysis report generation processing related to attendance, time stamping aggregation processing by base, or custom automatic aggregation processing (numerical aggregation). In addition, on the task display screen, operations related to attendance such as attendance can be performed on the task display screen, and necessary processing can be completed. In addition, in the case of a web service related to expense management, each user logs in to an individual service page through the task display screen, and is able to operate detailed functions such as automatic acquisition processing of expense details, automatic acquisition processing of receipt image data, request processing for proxy input of evidence, and input processing using OCR processing. In addition, on the task display screen, operations for application and approval of expenses can be performed on the task display screen, and necessary processing can be completed. As in these examples, by being able to log in to and operate the page of each web service through the task display screen, and by being able to check and operate on the task display screen, users can make use of web services more conveniently.

The web service recommendation process in the server intermediation device 101 will be described with reference to Figures 9 and 10.

In step S901 of FIG. 9, the request information acquisition unit 1019 acquires request information regarding a requested operation that the user requests to be executed. For example, assume that the user selects the Create new application button 60123 on the task display screen 601. At this time, the request information acquisition unit 1019 displays the requested operation acquisition screen 1001 shown in FIG. 10 by superimposing it on the task display screen 601 or in a pop-up format.

Display field 10011 in FIG. 10 displays a message prompting input of a requested operation. In requested operation input field 10012, the operation that the user wishes to execute is entered by user input. Request information acquisition unit 1019 acquires the information entered in requested operation input field 10012 as request information.

In step S902 of FIG. 9, the web service presentation unit 1020 identifies a web service capable of executing the requested operation based on the request information. The web service presentation unit 1020 performs, for example, natural language processing to interpret the context of the request information and identify an appropriate web service. For example, in FIG. 10, the web service presentation unit 1020 identifies a web service related to expense claims based on the request information "I would like to submit an expense claim for consumables."

In step S1003, the web service presentation unit 1020 presents the identified web service to the user. For example, in FIG. 10, "Service A" is displayed in the service presentation field 10014 along with the message "Please use this service" in the display field 10013. The request operation acquisition screen 1001 also has a form link button 10015. When the user selects the form link button 10015, an input screen for information required for the expense application is displayed, and similar to the process described with reference to FIG. 8, the operation information is sent to the web service providing server 301, and the application is completed. In this way, by making it possible to specify the web service to be used and send the operation information to each web service providing server through the task display screen 601, the user does not need to access each individual web service providing server 301 each time to perform the operation, thereby improving user convenience.

The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangement, conditions, shape, size, etc., are not limited to those exemplified, and may be modified as appropriate. In addition, configurations shown in different embodiments may be partially substituted or combined.

10...Web service providing system, 101...Server intermediary device, 201...User terminal, 301...Web service providing server, 1013...User information acquisition unit, 1014...Registration information acquisition unit, 1015...Task information acquisition unit, 1016...Screen information generation unit, 1017...Operation input acquisition unit, 1018...Operation information transmission unit, 1019...Request information acquisition unit, 1020...Web service presentation unit

Claims (10)

On the computer,
Obtaining user information from a user;
acquiring registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services based on the user information;
acquiring task information indicating a task to be handled by the user, the task information being associated with the user in each of at least one of the plurality of registered web services based on the registration information;
generating screen information of a task display screen that presents the task to the user based on the task information. The program according to claim 1,
The generating of the screen information includes:
generating the screen information having an approval task area in which an approval task that requires approval by the user among the tasks is displayed. The program according to claim 2,
The approval tasks are arranged in the approval task area in a first arrangement order based on the approval scope of the approval tasks associated with the user. The program according to claim 2,
The approval tasks are arranged in the approval task area in a second arrangement order based on the time when the user information was acquired and the deadline of the task. The program according to claim 1,
The generating of the screen information includes:
generating screen information for the task display screen including connection information associated with the task information and used to connect to a web service corresponding to the task information. The program according to claim 1,
The computer includes:
acquiring an operation input by the user for a target web service that is to be operated by the user among the plurality of registered web services;
and transmitting operation information based on the operation input to an operation target server that provides the operation target web service. The program according to claim 6,
The computer includes:
acquiring, from the operation target server, response information indicating a response to the operation information;
The generating of the screen information includes updating the screen information based on the response information. The program according to claim 6,
The computer includes:
obtaining request information regarding a requested operation that the user requests to be performed on one of the plurality of registered Web services;
The program further executes: identifying a web service from among the plurality of registered web services that can execute the requested operation based on the request information; and presenting information on the web services that can execute the requested operation to the user. The computer
Obtaining user information from a user;
acquiring registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services based on the user information;
acquiring task information indicating a task to be handled by the user, the task information being associated with the user in each of at least one of the plurality of registered web services based on the registration information;
generating screen information for a task display screen that presents the task to the user based on the task information. A user information acquisition unit that acquires user information from a user;
a registration information acquisition unit that acquires registration information indicating a plurality of registered web services in which the user is registered among a plurality of web services based on the user information;
a task information acquisition unit that acquires task information indicating a task to be handled by the user, the task information being associated with the user in at least one of the plurality of registered web services based on the registration information;
a screen information generating unit configured to generate screen information of a task display screen that presents the task to the user based on the task information.

Images