Information processing device, method for controlling the information processing device, and application that operates on the information processing device.

Abstract

To provide a server system for enabling a user to select a file desired to be printed by operating an information processing device in which a collaboration tool is installed, an information processing device and a control method thereof.SOLUTION: A collaboration tool is a server system that operates in cooperation with software for displaying an object to be selected in performing operation about a file submitted together with a message in an area of a corresponding message card. The server system has control means which causes software to execute processing for displaying, on a first operation screen for performing operation about a file or a second operation screen to be called from the first operation screen to be displayed on the basis of the selection of the object, the other object corresponding to a printing function provided by the server system, and enabling operation to print the file on the basis of the selection of the other object.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a control method for the information processing apparatus, and an application operating on the information processing apparatus.

Background Art

[0002] Representative examples of collaboration tools (hereinafter referred to as collaboration tools) include Microsoft Teams (registered trademark), Skype (registered trademark), Slack (registered trademark), and the like. As a method of sharing files in such collaboration tools, there is a method in which a file holder attaches a file existing in a shared server or locally to a message and posts it to upload it onto the system. Another user can view, edit, or download the uploaded file by operating the UI displayed on the file list screen or the message.

[0003] When printing a shared file, there is a method in which a plugin having a printing function (hereinafter referred to as a printing plugin) prints via a cloud printing service. Patent Document 1 describes a method of printing a file posted to a chat using a chatbot server. The print bot detects print actions such as a message post suggesting printing by a user on the collaboration tool or pressing an icon of the printing plugin displayed on the collaboration tool UI. The print bot inputs and manages a print job to a virtual queue of an image forming apparatus pre-registered with a tenant of the cloud printing service. Thereafter, the image forming apparatus acquires the print job from the virtual queue of the cloud printing service and outputs it. Representative examples of cloud printing services that are linked with the printing plugin include, for example, Microsoft Universal Print (registered trademark), uniFLOW Online (registered trademark), and the like.

Prior Art Documents

Patent Documents

[0004] [Patent Document 1] Japanese Patent Publication No. 2021-43717 [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] However, Patent Document 1 does not describe how a user can operate an information processing device on which a collaboration tool is installed and select a file to print from files uploaded to the collaboration tool.

[0006] In view of the above-mentioned problems, the present invention aims to enable a user to select a file to print by operating an information processing device on which a collaboration tool is installed. [Means for solving the problem]

[0007] The server system described in this application is a server system that operates in conjunction with software that provides a chat function, which, when a file is posted with a message, displays the file name of the file and a message card containing the message, displays a first object selected when performing an operation on the message outside the message card, and displays a second object selected when performing an operation on the file within the message card area, wherein, in a first operation screen for performing operations on the file, or a second operation screen called from the first operation screen, which is displayed based on the selection of the second object, an object corresponding to the printing function provided by the server system is displayed. With the print plugin installed The Supports printing functionality Control means that causes the software to perform a process that enables the operation of printing the file using the server system based on the selection of an object. The system includes a display means that, based on the selection of an object corresponding to the printing function when the printing plugin is not installed, displays an installation screen to instruct the installation of the printing plugin, and displays an input field for entering the channel name of the channel to which the printing plugin is associated, based on the instructions entered on the displayed installation screen; and an installation means that installs the printing plugin in association with the channel having the channel name entered in the input field. It is characterized by doing so. [Effects of the Invention]

[0008] By implementing the present invention, it becomes possible to operate an information processing device on which a collaboration tool is installed and allow the user to select the file they want to print. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the system configuration in this embodiment. [Figure 2] This figure shows an example of the hardware configuration in this embodiment. [Figure 3] This figure shows an example of the application installation UI in this embodiment. [Figure 4] This figure shows an example of the installation process for the print plugin in this embodiment. [Figure 5] This figure shows an example of the print settings UI provided by the print plugin in this embodiment. [Figure 6] This figure shows an example of the printing sequence in this embodiment. [Figure 7] This is a flowchart showing how the collaboration tool activates the print plugin in Example 1. [Figure 8] This flowchart shows the printing process performed by the print plugin in this embodiment. [Figure 9] This figure shows an example of the UI for calling the print plugin in Example 2. [Figure 10] This is a flowchart showing how to launch the print plugin from the function selection UI, which includes the print plugin item, in Example 2. [Figure 11] This figure shows an example of the UI for calling the print plugin in Example 3. [Figure 12] This is a flowchart showing how to launch the print plugin from a function selection UI that has a print item in Example 3. [Modes for carrying out the invention]

[0010] <Example 1> The best mode for carrying out the present invention will be described below with reference to the drawings.

[0011] Figure 1 is a simplified system configuration diagram of the network 700 environment showing an embodiment of the present invention. A client computer 100 and a printer 200 are connected to the network 700, which are configured on the same intranet and are in a state where communication is possible. In addition, there is a client computer 101 and a printer 201 connected to a different intranet, which are connected via the internet. Note that client computers 100 and 101 may be PCs, smartphones, or tablet devices. A collaboration tool 300, cloud storage 400, cloud print service 500, and print plugin 600 are connected to the network 700.

[0012] CollabTool 300 is a server system that provides services as an application running on client computers 100 and 101, or on a web browser installed on client computers 100 and 101. CollabTool 300 provides online meeting and chat services to client computers 100 and 101. Account management is performed using a user ID and password, and users can use the services provided by CollabTool 300 using this account. Online video calls and chat meetings are possible, and even users who have not registered an account can temporarily use it by being invited.

[0013] Cloud storage 400 is a cloud (i.e., a server system) consisting of one or more server devices. Cloud storage 400 is a server system that provides a storage service on the Internet. A user authenticated using an ID and password for cloud storage can use the service. A user who uses cloud storage 400 can upload file data onto cloud storage 400, view, and download the file data stored in cloud storage 400. The file data uploaded to cloud storage 400 can be shared with other users, and depending on the settings, restrictions on viewing, editing, and downloading can be set for each user or group.

[0014] Cloud print service 500 is a cloud (i.e., a server system) consisting of one or more servers. Cloud print service 500 is a server system that provides a printing function to users via the Internet. In the present embodiment, cloud print service 500 can be connected to each intranet. Further, cloud print service 500 can be connected to client computer 100, printer 200, client computer 101, and printer 201 via the Internet. Cloud print service 500 performs account management using an ID and password for the cloud print service, and users can use the printing function provided by cloud print service 500 using this account.

[0015] The printing plugin 600 is a server system composed of one or more information processing devices. The printing plugin 600 provides a printing function in cooperation with the online cloud storage 400, cloud printing service 500, and collaboration tool 300. When a user who has logged in to the service provided by the collaboration tool 300 performs an operation to use the service provided by the printing plugin 600 on the collaboration tool 300, the functions provided by the printing plugin 600 can be used. When the user operates the UI provided by the printing plugin 600 to the collaboration tool 300, a processing instruction is sent to the printing plugin 600. The printing plugin 600 that has received the instruction executes printing processing via the cloud printing service 500. At that time, message information is obtained from the collaboration tool 300, and file information is obtained from the cloud storage.

[0016] When accessing the collaboration tool 300, cloud storage 400, and cloud printing service 500, it is also possible to access each service with the account for the collaboration tool by means of single sign-on technology.

[0017] Next, the hardware configuration in the system of this embodiment will be described using FIG. 2.

[0018] FIG. 2(A) is a block diagram showing the hardware configuration of the client computer 100.

[0019] The client computer 100 comprises a control unit 110, a network communication unit 113, a storage unit 114, a display unit 115, and an input unit 116. The control unit 110 consists of a CPU 111 and a memory 112, and controls the overall operation of the client computer 100. The CPU 111 loads programs stored in the storage unit 114 into the memory 112 and executes them. The memory 112 is the main memory of the CPU 111 and is used as a work area and a temporary storage area for loading various programs. The network communication unit 113 is a device that communicates with external servers and information communication terminals via an external network 700 to input and output digital data. The storage unit 114 refers to a non-volatile storage device such as a hard disk or SSD, which can store and rewrite digital data. The display unit 115 is a device for displaying visual information to the user in real time, such as a liquid crystal display, and the input unit 116 is a device for receiving input from the user, such as a keyboard, mouse, camera, or microphone. Note that a device having both input and display functions, such as a touch panel, may also be used. In this embodiment, it is assumed that an application for using the services provided by the collaboration tool 300 is installed in the storage unit 114 of the client computer 100. The application stored in the storage unit 114 is loaded into memory 112 and executed by the CPU 111, thereby allowing the client computer 100 to access the services provided by the collaboration tool 300 and provide users with web conferencing and chat functions. The hardware configuration of the client computer 101 is the same as that of the client computer 100.

[0020] Figure 2(B) is a block diagram showing the hardware configuration of the printer 200. The printer 200 comprises a control unit 210, a network communication unit 213, a storage unit 214, a display unit 215, an input unit 216, and a printing unit 217. The control unit 210 and the storage unit 214 are the same as those in Figure 2(A), so their explanation is omitted. The network communication unit 213 is a device that communicates with an external network 700 and is mainly responsible for receiving print data and sending information about the printer 200's status, such as errors, to an external server. In the case of a cloud print-compatible printer, it also communicates with the cloud print service 500 to send registration information and receive jobs. The display unit 215 is a device that displays information to the user in real time, such as a touch panel or LEDs built into the printer 200. The input unit 216 is a device that accepts input from the user and may include a touch panel or hard keys such as a numeric keypad. The printing unit 217 is a device that performs printing processing by feeding, printing, and ejecting paper from paper prepared in a cassette or tray. The printing method is not particularly limited and can be electrophotographic or inkjet. The duplex unit and finishing device used during paper output are also included in the printing unit 217. In this embodiment, a multifunction printer (multifunction device) that also has scanner and fax functions may be used. Printer 201 will have the same configuration as printer 200.

[0021] Figure 2(C) is a block diagram showing the hardware configuration of the collaboration tool 300. It consists of a control unit 310, a network communication unit 313, and a storage unit 314. Details are the same as in Figure 2(A) and are therefore omitted. The storage unit 314 stores a program that enables the collaboration tool 300 to provide web conferencing and chat services. This program is loaded into memory 312 and executed by the CPU 311, allowing the collaboration tool 300 to provide services to client computers 100 and 101.

[0022] Figure 2(D) is a block diagram showing the hardware configuration of the cloud storage 400. It consists of a control unit 410, a network communication unit 413, and a storage unit 414. Details are the same as in Figure 2(A) and are therefore omitted. The storage unit 414 stores programs used by the cloud storage 400 to provide storage services, as well as file data uploaded by users.

[0023] Figure 2(E) is a block diagram showing the hardware configuration of the cloud print service 500. It consists of a control unit 510, a network communication unit 513, and a storage unit 514. The details of each component are the same as those in Figure 2(A) and are therefore omitted. The storage unit 514 stores programs used by the cloud print service 500 to provide the service, print data received from client computers 100 and 10, file information obtained from cloud storage 400, etc. Furthermore, the storage unit 514 stores the printer names and IP addresses of printers 200 and 201 to which the cloud print service 500 sends print data, as well as information on users who can use those printers.

[0024] Figure 2(F) is a block diagram showing the hardware configuration of the print plug-in 600. It consists of a control unit 610, a network communication unit 613, and a storage unit 614. The configurations of each unit are the same as those in Figure 2(A) and are therefore omitted. The storage unit 614 stores the program that the print plug-in 600 uses to provide services.

[0025] Furthermore, the information processing device having the hardware configuration of the collaboration tool 300, cloud storage 400, cloud print service 500, and print plugin 600 may be composed of multiple information processing devices. The details of this embodiment will be described below.

[0026] [Install the print plugin] First, we will explain the steps that users must take in order to utilize the functions provided by the printing plugin from the application provided by CollaborateTool300.

[0027] Furthermore, the Collaborative Tool 300 provides video call and chat functions as standard features. The Collaborative Tool 300 can provide users with extended functionality by linking with a server system provided by a vendor other than the vendor providing the Collaborative Tool 300. In this embodiment, a printing function is provided as an extended functionality. The vendor providing the printing function registers in advance a manifest file with the Collaborative Tool 300 that contains identification information to identify the service of the printing plugin 600 and a URL for the Collaborative Tool 300 to call the printing plugin 600. By installing the application that provides the registered extended functionality within the service provided by the Collaborative Tool 300, the user can use the extended functionality.

[0028] As shown in Figure 3, this system allows for functionality expansion through integration with Cloud Storage 400 and the installation of other applications, and a user interface is provided for each function.

[0029] Figure 3(A) shows an example of the collaboration tool screen. The application bar on the collaboration tool 300 displays pinned function buttons, and applications can be selected and installed for individuals or teams from the application button 1000. Adding the print plugin 600 to an individual is an example, and the installation flow shown in Figure 4 will be explained.

[0030] The Collaborative Tool 300 detects that the application button 1000 has been selected by the user (step S2001). The Collaborative Tool 300 displays a list of installable applications (Figure 3(B)) on the client computer's display (step S2002).

[0031] UI1001 allows the user to select an application category, and a filtered list of applications based on the user's selection is displayed on screen 315. The collaboration tool 300 detects the user's selection of the print plugin 600 (step S2003). The collaboration tool 300 then pops up the installation UI shown in Figure 3(C) on the client computer's display (S2004).

[0032] The Collaborative Tool 300 detects that the Add button 316 has been selected (step S2005). The Collaborative Tool 300 installs the print plugin 600 (step S2006). Installing the print plugin 600 means registering the identification information of the user who instructed the installation and the identification information of the print plugin 600 in the storage unit of the Collaborative Tool 300.

[0033] Furthermore, when adding a print plugin to a team, the user selects "Add to Team" 318 from list 317 on the screen shown in Figure 3(C). When the collaboration tool 300 detects the selection of "Add to Team" 318, it displays the pop-up shown in Figure 3(D) on the client computer screen. The user enters the team identification information and channel name to be installed in the input field 319 and selects the settings button 320. The collaboration tool 300 refers to the entered team identification information and channel name and installs the print plugin 600. Installation here means linking and storing the team or channel identification information and the print plugin 600 identification information in the collaboration tool 300's storage. In this way, the print plugin 600 can be called from the screen of the team or channel linked to the print plugin 600.

[0034] It would also be possible to install the plugin from various other locations within CollaboratTool 300, such as the team management button or tab, or the message posting UI. For example, in addition to installing the print plugin for each user, users could register and configure the app from the CollaboratTool 300 admin center, and then install the print plugin 600 by specifying the user or team.

[0035] Furthermore, the screen shown in Figure 3(C) also illustrates an object that accepts instructions to install the print plugin for a chat. This object allows the user to use the print plugin in a chat room they specify. When the user selects "Add to Chat," a screen appears where they can select the chat room to which they want to make the print plugin available. Once the user selects a chat room, the collaboration tool 300 associates the chat room's identification information with the print plugin's identification information and stores it, making the print plugin 600 service available from the chat room.

[0036] Once the Print Plugin 600 is installed, an icon to launch Print Plugin 600 will appear within the ellipsis (ellipsis) in Collaborative Tool 300. Users can then access the services provided by Print Plugin 600 by clicking on the displayed icon.

[0037] [Integration of printing plugins with various services] This section explains how the Print Plugin 600 integrates with various cloud services. When user authentication is performed on the Collaboration Tool 300, a token is issued. The Print Plugin 600 can then use this token to interact with cloud services and exchange information.

[0038] Files stored in Cloud Storage 400 contain basic information such as file names and creators, as well as sharing settings and access permission information. Control permissions can be set for each user or team for files and folders, and permissions for reading, writing, downloading, and printing can be configured. This information can be changed directly from the Cloud Storage 400 web page, and can also be modified using the Web API. Furthermore, file information, access permission information, and sharing settings information can be retrieved via the Web API.

[0039] Similarly, Cloud Print Service 500 stores pre-registered user and printer information. In addition to data such as printer name, printer ID, registrant, and status, information such as job acceptance capacity and operational status is also registered and managed. Registered information can be viewed and modified by accessing the Cloud Print Service 500 web page, and some information can be retrieved using the Web API. Furthermore, the Web API can be used to send print jobs, including file data and detailed settings, to virtual printer queues registered with Cloud Print Service 500, and to instruct the start of printing.

[0040] Example 1 describes how to call the print plugin from the ellipsis in a message with an attached file and print it.

[0041] First, Figure 5 will explain the transitions in the print settings UI displayed when the print plugin 600 is called on the collaboration tool 300.

[0042] In Collaboration Tool 300, when a message with an attached file is posted, as shown in Figure 5(A), a message card 1002 is displayed. The message card displays the posted message, file name, etc., along with the posting time. The user's username is also added to the message card so that the user who posted the message can be identified.

[0043] A toolbar 1003 is displayed outside the message card. The toolbar 1003 is an area where users can post reactions to the message card 1002. The toolbar 1003 displays an ellipsis 331 along with an object for posting reactions. This ellipsis 331 is an object for displaying the function selection UI 1332 for giving instructions to the message card 1002. The function selection UI 332 is an operation screen that calls up functions provided by the collaboration tool 300 and applications that the user has additionally installed.

[0044] When the print plugin 600 is installed, the function selection UI 332 displays the standard functions provided by the collaboration tool 300 and the "print plugin" 360. For example, the "Delete" object in the function selection UI 332 is used to delete the message card 1002.

[0045] When the user selects an item in "Print Plugin" 360, the Print Plugin 600 communicates with the Collaborative Tool 300, Cloud Storage 400, and Cloud Print Service 500 to obtain information about the files to be printed and the print queue to be used for printing. Based on the information obtained from the Collaborative Tool 300 and Cloud Print Service 500, the Print Plugin 600 sends a display instruction to the Collaborative Tool 300 for the screen shown in Figure 5(B).

[0046] Based on instructions from the print plugin 600, the collab tool 300 generates a print settings UI as shown in Figure 5(B) and displays it on the client computer's display. The print settings UI has a printer area 333 with a display field for the printer name to be printed and a printer selection button, and a file area 324 with a list of file names to be printed and a UI to switch whether to print each file name. Since there is only one file attached to the message card 1002 corresponding to the ellipsis 331, only "AAA.pdf" is displayed in list 334. If multiple files are attached to the message card 1002, the file names of multiple files are displayed in list 334, and the user selects the file they want to print from the file area 324. The default value for the check in the file area 324 may be on or off. If the cancel button 340 is selected, the print plugin 600 terminates the display of the print settings UI in Figure 5(B) on the collab tool 300. As a result, the screen shown in Figure 5(A) is displayed on the client computer's display. In Figure 5(B), the print settings UI is displayed in the form of an adaptive card on the screen shown in Figure 5(A) by the collaboration tool. The print settings UI may also be displayed in other formats.

[0047] Additionally, a detailed settings button 335 for calling up a WebUI to perform detailed print settings, a button 336 for instructing the user to print, and a button 340 for instructing the user to cancel are displayed. When the detailed settings button 335 is selected, the print plugin 600 displays a print settings screen (not shown) in the collaboration tool. On this print settings screen, the user can set the number of copies to print, the color mode, settings related to finishing such as stapling and punching, and enter a PIN code for secure printing. When the user presses button 336, the print plugin 600 sends the file to be printed, detailed settings, and user information to the printer queue registered in the cloud print service 500 and instructs the user to print. Here, the print plugin 600 sends the print data to the cloud print service 500 by specifying the print queue set in 333 in Figure 5(B).

[0048] The cloud print service 500 sends the print data obtained from the print plugin 600 to the printer 200 and prints it. When printing is complete, the UI on the collaboration tool 300 switches to the print completion UI shown in Figure 5(C). Figure 5(C) includes a message indicating that printing is complete, a button 337 to instruct the user to continue printing, and a button to instruct the user to end printing. If the button 337 to instruct the user to continue is selected, the print plugin 600 redisplays Figure 5(B). On the other hand, if the button to instruct the user to end printing is selected, the print plugin 600 closes the UI displayed by the print plugin and ends the printing operation.

[0049] Furthermore, when the printer selection button in the printer area 333 of Figure 5(B) is selected, the printer selection UI of Figure 5(D) is displayed. The printer selection UI displays a list 338 of shared printers registered with the cloud print service 500. When the OK button 339 is selected, the print plugin 600 displays a screen in which the result of the selection in the printer list UI 338 is reflected in the printer name display field of the printer area 333 of Figure 5(B). On the other hand, when the cancel button 1004 is selected, the print plugin 600 switches the screen to Figure 5(B) without updating the information.

[0050] Next, we will explain the workflow from calling the print plugin to printing using Figure 6.

[0051] As shown in Figure 5(A), when the collaboration tool 300 detects that the user has selected the "Print Plugin" item 360, which has been added to the function selection UI 332 via the ellipsis 331 attached to the message, it activates the print plugin 600 (S3001). The collaboration tool 300 notifies the print plugin 600 of the identification information of the user who instructed the activation of the print plugin 600, the identification information of the team to which the user belongs, and the identification information of the attachment associated with the message card 1002 corresponding to the selected ellipsis.

[0052] When the print plugin 600 is activated, it requests a list of registered shared printers from the cloud print service 500 (S3002). The print plugin 600 sends the user identification information received from the collaboration tool 300, the identification information of the team the user belongs to, and a request to the cloud print service 500 to obtain a list of shared printers that the user can use. The list of shared printers is a list of printer identification information registered with the cloud print service 500, and is a list of printer identification information that the user of the identification information sent by the print plugin 600 is permitted to use.

[0053] Once the request is approved by the cloud print service 500, the print plugin 600 receives a list of shared printers from the cloud print service 500 (S3003).

[0054] The print plugin 600 then combines the file information, user information, shared printer information, and default printer received from the collaboration tool 300 to generate the print settings UI shown in Figure 5(B), and displays the print settings UI on the collaboration tool 300 (S3004). The user selects the button 336 shown in Figure 5(B) (S3005). The print plugin 600 confirms the operation results on the print settings UI (printer and file information, detailed print settings). The print plugin 600 then requests the file data to be printed from the cloud storage 400 (S3006). The print plugin 600 then retrieves the file that has been instructed to be printed from the cloud storage 400 via the screen shown in Figure 5(B) (S3007). The print plugin 600 sends the retrieved file data and detailed print settings to the virtual printer queue of the cloud print service 500 (S3008). Once the cloud print service 500 has finished registering the print data received from the print plugin, it sends the print data transmission result to the print plugin 600. The print plugin 600 receives the transmission result from the cloud print service 500 (S3009). When the cloud print service 500 receives the print data from the print plugin 600, it sends the data as a job to the printer 200 and starts printing (S3010). Also, when the print plugin 600 receives notification that the transmission is complete, it displays the print completion UI shown in Figure 5(C) on the collaboration tool 300 (S3011).

[0055] Furthermore, Figures 7 and 8 will be used to explain the flow from the collaboration tool 300 to the call of the print plugin 600 within the print flow shown in Figure 6, as well as the flow of the print plugin 600 after it has been called by the collaboration tool 300.

[0056] Figure 7 is a flowchart illustrating the processes performed by the collaboration tool 300. The processes described in this flowchart are executed by the CPU 311 of the collaboration tool 300.

[0057] The collab tool 300 detects that the user has selected the ellipsis 331 attached to the message (S4001). In S4001, the collab tool 300 obtains the user identification information of the user who selected the ellipsis and the identification information of the team to which the user belongs. It determines whether the obtained user identification information is registered in the collab tool 300 in association with the identification information of the print plugin 600. If the obtained user identification information is registered in the collab tool 300 in association with the identification information of the print plugin 600, the collab tool 300 executes the process shown in S4002. If the obtained user identification information is not registered in the collab tool 300 in association with the identification information of the print plugin 600, the collab tool 300 determines whether the obtained team identification information is registered in association with the identification information of the print plugin 600. If the obtained team identification information is registered in association with the identification information of the print plugin 600, the collab tool 300 executes the process shown in S4002. If the acquired team identification information and the print plugin 600 identification information are not registered in association, the collab tool 300 determines whether the chat room identification information corresponding to the ellipsis is registered in association with the print plugin 600 identification information. If the chat room identification information is registered in association with the print plugin 600 identification information, the collab tool 300 executes the process described in S4002. If the chat room identification information is not registered in association with the print plugin 600 identification information, the collab tool 300 displays a function selection UI 332 that does not include "print plugin" 360. The case where "print plugin" 360 is not displayed is omitted in the explanation of Figure 7.

[0058] The collaboration tool 300 displays a function selection UI 332 that adds the items of the installed print plugin 600 to the standard functions of the collaboration tool 300 (S4002). In this embodiment, the standard functions of the collaboration tool include deleting posted messages and downloading uploaded files.

[0059] The collab tool 300 detects that the user has selected an item for the print plugin 600 in the function selection UI 332 (S4003). The collab tool 300 then activates the print plugin 600 (S4004). At this time, the collab tool 300 obtains file information, including the name and URL of the file attached to the message that called the print plugin 600 (S4005). Furthermore, it obtains user information, including the name and ID of the user who called the print plugin 600 (S4006). Having also obtained other information such as location information on the collab tool and message information, the collab tool 300 passes various information, including the above file information and user information, to the activated print plugin 600 (S4007).

[0060] This completes the process that Collaboration Tool 300 executes when Print Plugin 600 is launched.

[0061] Next, we will explain the operation of the print plugin 600. The print plugin 600 is called and started from the collaboration tool 300 (S5001). The print plugin 600 receives various information from the collaboration tool 300, including file information and user information (S5002).

[0062] Once the print plugin 600 has finished receiving information from the collaboration tool 300, it then sends a request to the cloud print service 500 for a list of registered shared printers (S5003). The print plugin 600 then retrieves the list of printers sent by the cloud print service 500 (S5004).

[0063] The print plugin 600 generates the print settings UI shown in Figure 5(B) along with file information, etc. (S5005). Then, the print plugin 600 displays the print UI on the collaboration tool 300 (S5006).

[0064] The system accepts user input until the print button 336 is pressed. The print plugin 600 determines whether the advanced settings button has been selected (S5007). If it determines that the advanced settings button has been selected, the print plugin 600 displays the Web UI for advanced settings (S5008). The print plugin 600 determines whether the printer selection button in the printer area 333 has been selected (S5009). If it detects that the printer selection button has been pressed, the print plugin 600 displays the printer selection UI shown in Figure 5(D) (S5010).

[0065] The print plugin 600 determines whether the OK button or the Cancel button of button 339 on the printer selection UI in Figure 5(D) is selected (S5011). If it is determined that the OK button is selected, the print plugin 600 proceeds to S5012. On the other hand, if it is determined that the Cancel button is selected, the print plugin returns to S5007.

[0066] If the OK button is selected, the printer information re-selected by the user in the printer list UI338 is reflected in the print UI in Figure 5(B) and redisplayed on the collaboration tool 300 (S5012). Then, when the print plugin 600 detects that the print button 336 in Figure 5(B) has been pressed, it executes the print process (S5013).

[0067] In this way, the print plugin can be invoked and a print command issued from the ellipsis (3-dot) added to the message area when a file is posted.

[0068] <Example 2> In Example 1, we described an example of calling the print plugin from an ellipsis attached to a message, as shown in Figure 5(A). However, the print plugin may also be called from an ellipsis 341 corresponding to a file attached to the message, as shown in Figure 9(A). The ellipsis 341 is an object that is displayed in a one-to-one correspondence with the uploaded file. Note that in Example 2, Figures 1 to 4, 5(B) to (D), 6 and 8 are the same as in Example 1 described above.

[0069] When the user selects the ellipsis 341, the function selection UI 342 is displayed. The function selection UI 342 is a UI for selecting an action to be taken on a file uploaded to the collaboration tool 300. For example, "Open in Browser" is an option to open and display "AAA.pdf" in a web browser installed on the client computer. "Download" is an option to download "AAA.pdf" to the client computer. "Copy Link" is an option to copy a link to retrieve "AAA.pdf" from the cloud storage 400. Thus, the ellipsis attached to an uploaded file is an object for selecting an action to be taken on the uploaded file, not on the entire posted message.

[0070] In Figure 9(A), when the function selection UI342 is displayed and "Print Plugin" is selected, the screen shown in Figure 5(B) is displayed. Here, the file to be printed is "AAA.pdf", which corresponds to the ellipsis. The screens and processes displayed by the print plugin 600 from here on are the same as in Example 1, so the explanation is omitted.

[0071] Furthermore, as shown in Figure 9(B), a UI is provided to display a list of files shared within a tenant on a tenant or channel basis, and a UI is also provided to display a list of files in Cloud Storage 400 in conjunction with Cloud Storage 400. Each file in the UI that displays the file list is equipped with an ellipsis, and it may be possible to call the print plugin 600. Figure 9(B) is a list of files shared with users belonging to channel C of team B. "Name" is the file name, and "Updated Date" indicates the date and time the file was updated. "Updater" shows the username of the last person to update the file.

[0072] In Figure 9(B), selecting "Print Plugin" from the function selection UI344 displays the screen shown in Figure 5(B). At this time, the screen displays the file "AAA.pdf," which corresponds to the ellipsis used to call the print plugin, as the file to be printed.

[0073] The ellipsis 343 corresponds to "AAA.pdf". In the file list shown in Figure 9(B), an ellipsis is attached to every file in a one-to-one relationship. By calling the function selection UI344 from the ellipsis attached to each file, you can open the corresponding file in a browser, download it, or print it.

[0074] Example 2 describes an example of calling the print plugin 600 from the ellipsis (3) added to a file displayed on the collaboration tool 300, as shown in Figure 9, and then printing.

[0075] Figure 10 is a diagram summarizing the flow of calling the print plugin 600 from the ellipsis attached to the file on the collaboration tool 300 shown in Figure 9.

[0076] Figure 10 is a flowchart showing the processes executed by the CPU 311 of the collaboration tool 300.

[0077] The collaboration tool 300 detects that the ellipsis 341 or 343 in Figure 9(A)(B) has been selected by the user (S6001). The collaboration tool 300 searches for applications already installed (S6002). The collaboration tool 300 determines whether the print plugin 600 is included in the search results (S6003). The collaboration tool 300 uses the identification information of the user who selected the ellipsis, the identification information of the team to which the user belongs, and the identification information of the chat room where the ellipsis was displayed to determine whether the print plugin 600 is already installed. If the identification information of the print plugin 600 is registered in association with any of the user identification information, team identification information, or chat room identification information, the collaboration tool 300 determines that the print plugin 600 is already installed.

[0078] If the print plugin 600 is not included, the collaborating tool 300 displays a feature selection UI that does not include "print plugin" as an option (S6008).

[0079] On the other hand, if a print plugin is included, the collab tool 300 generates a function selection UI 342 or 344 with the print plugin 600 item added and displays it on the collab tool 300 (S6005). The collab tool 300 then detects that the print plugin 600 item on the function selection UI 342 or 344 has been selected by the user (S6006). The collab tool 300 then activates the print plugin 600 (S6007). In S6007, the collab tool 300 notifies the print plugin 600 of the user's identification information, the team information to which the user belongs, and the identification information of the file associated with the ellipsis used to activate the print plugin 600.

[0080] The subsequent printing flow and the operation of the print plugin 600 are the same as in Example 1, so they will be omitted.

[0081] Furthermore, when launching the print plugin 600 from the file list screen shown in Figure 9(B), it may be possible to print multiple files at once. For example, in Figure 9(B), the user selects the files they want to print from 371a, 371b, and 371c, which are displayed next to each file name. When at least one file from 371a to 371c is selected, "Print" 373 is displayed in area 372. When the user selects "Print" 373, the collaboration tool launches the print plugin and notifies the print plugin of the file name and file path of the selected file from 371a to c. As a result, the print plugin displays the screen shown in Figure 5(B). Here, list 334 in Figure 5(B) displays the file names of the files selected by the user from 371a to c. In Figure 5(B), the checkboxes next to the file names may all be selected, or no files may be selected.

[0082] In the above explanation, when a file is selected in Figure 9(B), "Print" 373 is displayed in area 372. Alternatively, "Print" 373 may always be displayed in area 373 if the print plugin is associated with the team sharing the file.

[0083] By doing this, printing can be performed as the corresponding process for the file selected in CollaborationTool 300.

[0084] <Example 3> Examples 1 and 2 described the case where the Print Plugin 600 item was added to the function selection UI directly below the ellipsis. In Example 3, as shown in Figures 11(A) and 11(B), the function selection UI called from the ellipsis attached to the file has a print item. When the print item is selected, the collab tool displays a print function selection UI consisting of a list of print-related plugins as the second level. Note that in Example 2, Figures 1 to 4, 5(B) to 5(D), 6 and 8 are the same as in Example 1 described above.

[0085] Figures 11(A) and 11(B) show examples of screens displayed by the collaboration tool 300 in Example 3. In Figure 11(A), when the user selects the three dots next to the file name of the file they want to print, the function selection UI 352 is displayed, and "Print" 353 is displayed in the function selection UI 352. When the user selects "Print" 353, the print plugin selection UI 354 is displayed.

[0086] This area in CollaborationTool 300 displays a list of applications that provide printing functionality installed for a user, their team, or the chat room associated with the ellipsis. Multiple printing plugins offering different functionalities are displayed here.

[0087] Figure 12(A) summarizes the flow for calling the print plugin 600 from the second-level print function selection UI. The process shown in Figure 12(A) is a flowchart of the process executed by the CPU 311 of the collaboration tool 300.

[0088] First, the collaboration tool 300 detects that the user has selected the ellipsis 351 and 355 attached to the file (S7001). The collaboration tool 300 then displays the first-level function selection UI 352 and 356 (S7002). Which of the function selection UI 352 or 356 is displayed depends on whether the screen associated with the selected ellipsis is the chat screen or the file list screen. The function selection UI 352 and 356 include the print items 353 and 357.

[0089] The Collaborative Tool 300 detects that print item 353 or 357 has been selected (S7003). The Collaborative Tool 300 searches all installed applications (S7004). Based on the identification information of the user who selected "Print", the identification information of the team to which the user belongs, and the identification information of the chat room used to call the function selection UI, the Collaborative Tool 300 searches for a print plugin associated with any of the identification information.

[0090] Furthermore, the Collaborative Tool 300 determines whether the search results include applications related to printing (S7005). The manifest file of applications provided for functional extensions of the Collaborative Tool can include the category of the application. In S7005, the Collaborative Tool 300 refers to the manifest file of the installed applications and searches for applications that are described as "printing" as a category.

[0091] If the collab tool 300 determines that a printing application is installed, it generates a second-level print plugin selection UI 354 (S7006). In S7006, the collab tool 300 generates a print plugin selection UI 354 or 358 that displays applications with "Print" as a category and others.

[0092] The collaboration tool 300 then displays the generated print plugin selection UI 354 or 358 on the client computer (S7007).

[0093] Then, it detects that an application item included in the print plugin selection UI 354 or 358 has been selected (S7008). The collab tool 300 sends a notification to launch the selected print plugin (S7009).

[0094] On the other hand, if the Collaborative Tool 300 determines that no printing applications are included in the search results, it generates a print plugin selection UI containing only "other" items (S7010). The Collaborative Tool 300 displays the generated print plugin selection UI on the client computer's display unit (S7011). Then, when it detects that the user has selected "other" items, it switches to the application installation screen shown in Figure 3(B) and prompts the user to install the application (S7012, S7013).

[0095] In the above embodiment, if "Other" is selected in S7008, the Collaborative Tool 300 displays a screen to select an application to install that has printing functionality but is not currently installed. This is the same process as that corresponding to S7013.

[0096] In Figure 12(A), function selection UIs 352 and 356, which include a print item, were generated regardless of whether or not a printing application is present. If the user has not added any printing plugins, the "Print" option in function selection UIs 352 and 356 may be hidden. In other words, as shown in the flow in Figure 12(B), it may be possible to determine whether or not to include a print item based on the presence or absence of a printing application when generating the function selection UI, and to display a function selection UI that does not include a print item.

[0097] The Collaborative Tool 300 detects that the user has selected the ellipsis attached to the file (S8001). The Collaborative Tool 300 searches for installed applications (S8002). At this time, it determines whether the search results include any applications related to printing (S8003). If none are included, the Collaborative Tool 300 displays a function selection UI that does not include any printing items (S8011). On the other hand, if it is confirmed that at least one application related to printing is included, it generates and displays function selection UIs 352 and 356 that have printing items as shown in Figures 11(A) and (B) (S8004, S8005). Then, when the Collaborative Tool 300 detects that printing items 353 and 357 have been selected by the user (S8006), it generates and displays a print function selection UI that includes all the printing applications found in S8003 (S8007, S8008). When the Collaborative Tool 300 detects that an application item has been selected by the user on the print function selection UI, it launches the corresponding system (S8009, S8010).

[0098] The subsequent printing flow and the operation of the print plugin 600 are the same as in Examples 1 and 2, so they will be omitted.

[0099] Furthermore, in Figures 12(A) and 12(B), when the user selects "Other" in the print plugin selection UI 354 or 358, a screen is displayed to select an application to install from among the applications with printing capabilities that are not currently installed. When "Other" is selected, the collab tool 300 may perform the following actions: The collab tool 300 generates a PDF file based on the file corresponding to the selected ellipsis. The collab tool 300 launches a PDF viewer or an application capable of displaying PDFs installed on the client computer and displays the generated PDF file. In this way, the user can print files without having to install an application with printing capabilities within the collab tool.

[0100] This allows users to freely select the plugin they want to use, even if multiple print plugins are installed.

[0101] <Other examples> Note that Figures 7, 10, and 12 in Examples 1-3 above describe processes executed by the Collaborative Tool, which is a server system. Alternatively, these processes may be executed by an application for the Collaborative Tool installed on a client computer.

[0102] The present invention can also be realized by performing the following process: supplying software (programs) that realize the functions of the embodiments described above to a system or device via a network or various storage media, and having the computer (or CPU, MPU, etc.) of that system or device read and execute the program code. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

Claims

1. A server system that operates in conjunction with software that provides a chat function, which, when a file is posted with a message, displays the file name of the file and a message card containing the message, displays a first object selected when performing an action on the message outside the message card, and displays a second object selected when performing an action on the file within the message card area, In the first operation screen for performing operations on the file, or the second operation screen called from the first operation screen, which is displayed based on the selection of the second object, the object corresponding to the printing function provided by the server system is displayed. A control means that causes the software to execute a process that enables the operation for printing the file using the server system, based on the selection of an object corresponding to the printing function while the printing plugin is installed, A display means that, based on the selection of an object corresponding to the printing function when the printing plugin is not installed, displays an installation screen to instruct the installation of the printing plugin, and displays an input field for entering the channel name of the channel to which the printing plugin is associated, based on the instructions entered on the displayed installation screen, A server system characterized by having an installation means for installing the print plugin in association with a channel having a channel name entered in the input area.

2. The server system according to claim 1, characterized in that the control means causes the software to display a screen for setting print settings for the file based on the selection of the object.

3. The server system according to claim 1 or 2, characterized in that the control means obtains information about the file from the software based on the selection of the object.

4. The server system according to any one of claims 1 to 3, characterized in that the information relating to the file is the file path in which the file is stored.

5. The aforementioned server system The print settings screen is displayed in the aforementioned software. Based on the aforementioned file path, retrieve the aforementioned file, The server system according to claim 4, which transmits the acquired file and the print settings configured via the displayed print settings screen to another server system.

6. The server system according to claim 1, characterized in that the display means displays a plurality of file candidates based on the fact that an object corresponding to the printing function has been selected while the printing plugin is installed.

7. A control method for a server system that operates in conjunction with software that provides a chat function, which, when a file is posted with a message, displays the file name of the file and a message card containing the message, displays a first object selected when performing an operation on the message outside the message card, and displays a second object selected when performing an operation on the file within the message card area, In the first operation screen for performing operations on the file, or the second operation screen called from the first operation screen, which is displayed based on the selection of the second object, the object corresponding to the printing function provided by the server system is displayed. A control step in which, based on the fact that an object corresponding to the printing function has been selected while the printing plugin is installed, the software is instructed to perform a process that enables the operation for printing the file using the server system, A display step in which, based on the selection of an object corresponding to the printing function when the printing plugin is not installed, an installation screen is displayed to instruct the installation of the printing plugin, and an input field for entering the channel name of the channel to which the printing plugin is associated is displayed based on the instructions entered on the displayed installation screen, A method for controlling a server system, characterized by comprising an installation step of installing the print plugin in association with a channel having a channel name entered in the input area.

8. The control step is characterized in that, based on the selection of the object, the software displays a screen for setting the printing of the file, as described in claim 7.

9. The control step is characterized in that, based on the selection of the object, information regarding the file is obtained from the software, as described in claim 7 or 8.

10. The method for controlling a server system according to any one of claims 7 to 9, characterized in that the information relating to the file is the file path where the file is stored.

11. The aforementioned server system The print settings screen is displayed in the aforementioned software. Based on the aforementioned file path, retrieve the aforementioned file, A method for controlling a server system according to claim 10, comprising sending the acquired file and the print settings configured via the displayed print settings screen to another server system.

12. The control method for a server system according to claim 7, characterized in that the display step displays a plurality of file candidates based on the fact that an object corresponding to the printing function has been selected while the printing plugin is installed.

Images