Information processing device, system, information processing method, and program

Abstract

To allow setting information for hot folders to be appropriately registered and used.SOLUTION: A server system capable of communicating with an information processing device includes providing means for providing the information processing device with information for displaying a setting screen for performing a setting related to a hot folder in the information processing device, and registration means for registering information about the hot folder in association with a setting value associated with the hot folder based on operations received from a user on the setting screen.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a system, an information processing method, and a program. [Background technology]

[0002] A folder is prepared in a client device such as a PC, and the client device performs image processing associated with the folder on the target file as the target file is stored in the folder. For example, a hot folder system is known in which the target folder is configured as a print job and the client device automatically sends the print job to an image forming device such as a printer to execute the print process (see Patent Document 1). This system allows a user of a client device to issue a print instruction by the relatively simple operation of storing the target files in the hot folder. For example, if a user wishes to issue a print instruction using the same print settings for a large number of target files (print data), the user can store the files together in the hot folder and issue the print instruction using the same print settings. This system eliminates the user's need to individually select target files to print using an application such as a printer driver and issue a print instruction, which is cumbersome. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-219920 Summary of the Invention [Problem to be solved by the invention]

[0004] Print instructions via a hot folder are made according to the print settings associated with the hot folder. In conventional hot folder systems, the setting information associated with a hot folder is registered and used for each client device. For example, if a hot folder associated with the same setting information was to be registered and used on another client device, the setting information had to be registered from scratch. The present invention aims to provide a method for conveniently registering and using folder setting information. [Means for solving the problem]

[0005] A server system capable of communicating with an information processing device, characterized by having a providing means for providing the information processing device with information for displaying a setting screen for configuring hot folders on the information processing device, and a registration means for registering information about the hot folder in association with setting values ​​associated with the hot folder based on operations received from a user on the setting screen. [Effects of the Invention]

[0006] According to the present invention, it is possible to preferably register and use folder setting information. [Brief explanation of the drawings]

[0007] [Figure 1] System configuration diagram according to this embodiment [Figure 2] 1 is a hardware configuration diagram of an information processing device according to an embodiment of the present invention; [Figure 3] 1 is a hardware configuration diagram of an image forming apparatus according to an embodiment of the present invention; [Figure 4] 1 is a software configuration diagram of an information processing device according to an embodiment of the present invention; [Figure 5] 1 is a diagram illustrating a software configuration of an image forming apparatus according to an embodiment of the present invention; [Figure 6] 1 is a software configuration diagram of a cloud service according to this embodiment. [Figure 7] Capability information of the image forming apparatus in this embodiment [Figure 8]Product template management and creation screen in this embodiment [Figure 9] Hot folder management and creation screen in this embodiment [Figure 10] Product template creation flowchart in this embodiment [Figure 11] Product template editing flowchart according to this embodiment [Figure 12] Hot folder creation flowchart in this embodiment [Figure 13] 10 is a flowchart of a hot folder application according to this embodiment. [Figure 14] 1 is a flowchart of a cloud application according to this embodiment. [Figure 15] Flowchart of the print job transmission / reception unit in this embodiment [Figure 16] 1 is a diagram showing the structure of a job management table in this embodiment. [Figure 17] Image forming device management and addition screen in this embodiment [Figure 18] Addition flowchart of the image forming apparatus in this embodiment [Figure 19] Product template update flow chart for printing in the second embodiment [Figure 20] Software configuration diagram and hot folder management screen of information processing device in embodiment 3 DETAILED DESCRIPTION OF THE INVENTION

[0008] The following describes embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the present invention, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0009] <Embodiment 1> FIG. 1 is a schematic diagram illustrating the configuration of a cloud printing system according to this embodiment. At location X 103, an information processing device 100, such as a computer, and an image forming device 101 are connected to the Internet 130 via a LAN (Local Area Network) 102. Similarly, at location Y 122, an information processing device 120 is connected to the Internet 130 via a LAN 121. Locations X 103 and Y 122 may each have multiple image forming devices 101. Furthermore, the image forming devices 101 may each be different models. A cloud service 110 is connected to the Internet 130 via a LAN (Local Area Network) 111. The cloud service 110 is provided by a server system consisting of one or more information processing devices, and multiple cloud services 110 may be provided. Furthermore, multiple cloud services 110 may be combined into a single cloud service. The information processing device 100, the information processing device 120, and the image forming device 101 can communicate with the cloud service 110 via the Internet 130.

[0010] A user can log in to the cloud service 110 from the information processing device 100 and create, edit, and delete product templates used by the hot folder application 400 of the information processing device 100. A hot folder is a system in which setting information is linked to each folder, and when a file is stored in the folder, the stored file is processed using the setting information linked to the file. A product template is a group of setting values ​​linked to a folder, and here, it is assumed to be a group of setting values ​​for instructing printing. The hot folder application 400 running on the information processing device 100 can download product templates held by the cloud service 110. The hot folder application 400 can create a hot folder linked to the downloaded product template. The hot folder application 400 also transmits a print file stored in the hot folder and a product template identifier as a print job to the cloud service 110. The cloud service 110 converts the print job received from the hot folder application 400 based on the product template and transmits the converted data to the image forming device 101. The image forming device 101 prints the print job received from the cloud service 110. The hot folder application 400 may also run on the information processing device 120, and the cloud service 110 can be used from the information processing device 120 in the same manner.

[0011] In this embodiment, the above configuration example will be described as an example of a cloud printing system, but the present invention is not limited to this, and it is sufficient that the information processing device 100, the image forming device 101, and the cloud service 110 are communicably connected via a network. The network may be wireless or wired. The image forming device 101 only needs to have a printing function, and may be a device with a single printing function, or an MFP (multifunction peripheral) that adds a scanner and / or fax function to the printing function.

[0012] FIG. 2 is a diagram showing an example of the hardware configuration of the information processing devices 100 and 120 according to this embodiment.

[0013] The information processing devices 100 and 120 each include a CPU 201 , a ROM 202 , a RAM 203 , a HDD 204 , an input device 205 , a display 206 , and a network I / F 207 , all of which are connected to a bus 208 .

[0014] The CPU 201 reads out control programs stored in the ROM 202 or hard disk drive (HDD) 204 and executes various control processes. The RAM 203 is used as a temporary storage area such as the main memory or work area of ​​the CPU 201. The HDD 204 stores image data and various programs. Note that the configuration may include other storage devices such as a solid state drive (SSD) instead of or in addition to the HDD.

[0015] The input device 205 is an instruction input unit that inputs control commands and text to applications (described later), and includes a keyboard, pointing device, and the like.

[0016] The display 206 is an output device that is a display unit, and displays commands input from the input device 205, the status of applications (to be described later), and the like.

[0017] The network I / F 207 connects the information processing devices 100 and 120 to a network (such as a LAN, an intranet, or the Internet). The information processing devices 100 and 120 transmit and receive various information to and from other devices on the network using the network I / F 207. The hardware configuration of the cloud service 110 is also equivalent to the hardware configuration of the information processing device 100 shown in FIG. 2.

[0018] 3 is a diagram showing an example of the hardware configuration of the image forming apparatus 101 according to this embodiment. The image forming apparatus 101 includes a CPU 301, a ROM 302, a RAM 303, a HDD 304, an input device 305, a display 306, a printing unit 307, an image processing unit 308, and a network I / F 309, all of which are connected to a bus 310.

[0019] The CPU 301 reads out control programs stored in the ROM 302 or hard disk drive (HDD) 304 and executes various control processes. The RAM 303 is used as a temporary storage area such as the main memory or work area of ​​the CPU 301. The HDD 304 stores image data and various programs. Note that the configuration may include another storage device such as a solid state drive (SSD) instead of or in addition to the HDD.

[0020] The input device 305 is an instruction input unit that issues control commands and is composed of a touch panel superimposed on the display 306. The display 306 displays a UI for operating the image forming apparatus 101 and image data. The image processing unit 308 performs correction, processing, and editing processes on the input image data. The printing unit 307 prints the data processed by the image processing unit 308. The network I / F 309 connects the information processing apparatuses 100 and 120 to a network (such as a LAN, an intranet, or the Internet).

[0021] 4 is a software configuration diagram of the information processing devices 100 and 120 according to this embodiment. These are realized by the CPU 201 executing programs stored in the ROM 202, HDD, etc. of the information processing devices 100 and 120. The same reference numerals are used for components already mentioned, and descriptions thereof will be omitted. The configuration of FIG. 4 is a functional configuration realized by a computer executing a program, and does not necessarily have to be exactly as shown in FIG. 4. For example, there may be variations in the configuration, such as integrating multiple functional blocks, or having part of a certain functional block in FIG. 4 included in another functional block.

[0022] Reference numeral 400 denotes a hot folder application that realizes a hot folder function in the information processing device 100. Reference numeral 401 denotes a hot folder storage unit that stores information about hot folders managed by the hot folder application 400. Reference numeral 402 denotes a template storage unit that stores product templates used by the hot folder application 400. Reference numeral 403 denotes a template acquisition unit that acquires product templates from the cloud system 110. Reference numeral 404 denotes a job transmission unit that transmits print jobs from the hot folder to a cloud service. Reference numeral 405 denotes a hot folder management unit that manages information about each hot folder and product templates. Reference numeral 406 denotes a hot folder monitoring unit that monitors whether a print file has been placed in a hot folder. Reference numeral 407 denotes a file output unit that outputs a print file imposed by the cloud service 110 to the hot folder. Reference numeral 408 denotes a print job transmission / reception unit that receives print data imposed by the cloud service 110 and transmits it to the image forming device 101. The print job transmission / reception unit 408 may be located in the information processing device 120 or another information processing device, but is preferably located within the same network as the image forming device 101. Reference numeral 409 denotes a control unit for controlling processing and communication between 401 to 408. Reference numeral 410 denotes a communication processing unit for performing communication processing between the information processing device 100 and other image processing devices.

[0023] 5 is a diagram showing the software configuration of the image forming apparatus 101 according to this embodiment. These are realized by the CPU 301 executing programs stored in the ROM 302 of the image forming apparatus 101.

[0024] The print queue 501 can queue and store print jobs received by the receiving unit 503. The print job includes a print file such as PDF and a print setting file such as JDF. The print control unit 502 reads the print file such as PDF and the print setting file such as JDF included in the print job stored in the print queue 501, performs rendering, image processing, etc., and executes control to send them to the printing unit 307. The receiving unit 503 controls the network I / F 309 and executes control to store the received print job in the print queue 501. The print setting capability information 504 is a database that indicates the printing capabilities of the image forming apparatus 101. Details of the printing capabilities will be explained in FIG. 7.

[0025] 6 is a diagram showing the software configuration of the cloud service 110 in this embodiment. These are realized by loading a program stored in an HDD 204 provided in one or more information processing devices 110 of the cloud into a RAM 203 and executing it with a CPU 201.

[0026] The template management unit 601 is a program that reads / writes / updates the template storage unit 602. The template storage unit 602 is a database that stores product templates. The job storage unit 603 is a database that stores job information. The image forming device information storage unit 604 is a database that stores capability information of image processing devices supported by this cloud service. The job transmission unit 605 is a program that controls the job stored in the job storage unit 603 so that it can be read from the information processing device 100. The print data analysis unit 606 is a program that executes a preflight to check whether a PDF file input to the cloud service is suitable for printing. The layout generation unit 607 is a program that specifies imposition processing. The print data conversion unit 608 is a program that converts a PDF file input to the cloud service into a PDF file to be sent to a printing device. The print job information generation unit 609 is a program that creates JDF to specify printing to a printing device. The control unit 610 is a program that combines programs held by the cloud service 110 to provide a specified service. A communication control unit 611 controls communication according to the HTTP protocol, and can communicate with other cloud services, the information processing device 100, the information processing device 120, and the image forming device 101. An image forming device management unit 612 is a program that processes a registration request for the image forming device 101 from the information communication device 100.

[0027] 7 is a diagram showing the capability information of the image forming apparatus in this embodiment. For example, the capability information is held by the image forming apparatus and is used by the hot folder application 400 and the cloud service 110.

[0028] The capability information file 701 is a file that indicates capability information provided by the image forming apparatus 101, and is assumed to be an XML file here.

[0029] General information 702 (General) includes the name (NAME) and model name (Model) of the image forming apparatus.

[0030] Stapling capability 703 (Stapling) indicates the stapling function provided by the image forming apparatus 101. In this embodiment, the setting values ​​include no stapling (None), single (Single), dual (Dual), corner (Corner), and saddle stitching (Saddle). Stapling position information 704 indicates designation information for the staple position that can be designated in the image forming apparatus 101. Left, upper left (LeftTop), bottom left (LeftBottom), right (Right), upper right (RightTop), and bottom right (RightBottom) can be designated. It also indicates that top, upper left, upper right, bottom, bottom left, and bottom right can be designated.

[0031] The media size name 705 indicates the name of the paper size supported by the image forming apparatus 101. In this embodiment, A3, A4, A4Tab, A5, Executive, Legal, Letter, and SRA3 can be specified. The media type 706 (MediaType) indicates the media type supported by the image forming apparatus 101. In this embodiment, ContinuousLong, Photographic, Stationary, Envelope, and Undefined can be specified. The media source 707 indicates information about the paper feed slots supported by the image forming apparatus 101. In this embodiment, AutoSelect, BypassTray, Tray-1, and Tray-2 can be specified.

[0032] The constraint information 708 indicates a combination of job setting values ​​that cannot be accepted by the image forming apparatus 101. In this embodiment, this indicates that the combination of a staple function specification of dual or corner and a media type of continuous paper or envelope cannot be executed. The constraint information can describe multiple combinations, and various other constraint conditions can also be defined.

[0033] 8 shows a product template management screen provided by the cloud service 110 in this embodiment. For example, this is a screen that is displayed on a web browser of the information processing device 100 when the information processing device 100 accesses the cloud service 110. Each screen in FIG. 8 is an example of a screen for creating a product template, and does not necessarily have to be exactly as shown in FIG. 8. Furthermore, the information processing device 100 may display the screen provided by the cloud service 110 by means other than a browser.

[0034] Reference numeral 800 denotes a product template management screen. Reference numeral 801 denotes an add product template button. Pressing this button opens a preview file selection screen 810. Reference numeral 802 denotes a delete product template button, which deletes a product template selected in the product template list 803 from the template storage unit 602. Reference numeral 803 denotes a table showing the product template list, which displays a list of product templates stored in the template storage unit 602. A login screen for logging in to the service may be provided before displaying the product template management screen 800, and a product template list corresponding to the logged-in user may be displayed. Users can manage and use the product templates they have registered, regardless of the device they use. Reference numeral 804 denotes an edit product template button. This button is used to edit a product template selected in the product template list 803, and pressing this button opens a product template print setting screen 820. Reference numeral 805 denotes a save product template button. Pressing this button saves or updates the product template with the current print settings and detailed settings in the template storage unit 602.

[0035] Reference numeral 840 denotes a detailed setting value input section for a product template. This is an area for inputting detailed setting values ​​for a product template selected from the product template list 803. Details will be explained in 841 to 848.

[0036] Reference numeral 810 is a screen for selecting a file for previewing a product template. This is a screen for selecting a file to be used for displaying the preview screen, which will be described later. Reference numeral 811 is a file path input section for the preview file. Reference numeral 812 is a preview file browse button. When pressed, a file selection dialog (explorer) opens, and the file path of the selected file is entered in the file path input section 811. Reference numeral 813 is a button for canceling the preview file selection. When pressed, the preview file selection screen 810 closes. Reference numeral 814 is a product template editing start button. When pressed, the product template print setting screen 820 opens, and the preview file selection screen 810 closes.

[0037] Reference numeral 820 denotes a print setting screen for configuring print settings for the product template. Reference numeral 821 denotes a preview display area for checking the print data image when changing print settings. A preview of the print data is displayed for the file specified by the information entered in the file path input area 811. Reference numeral 822 denotes a print setting area for changing print settings. Here, the image forming device 101 from which print settings will be acquired is selected. Print settings such as paper size can also be changed. The cloud service 110 acquires print settings that can be processed by the image forming device selected in the "Device Name" field, and the user sets the desired print setting values ​​from those print settings. Reference numeral 823 denotes a button for canceling the product template print settings. Pressing this button closes the product template print setting screen 820. Reference numeral 824 denotes an end editing button for product template print settings. Pressing this button closes the product template print setting screen 820 and displays the product template setting value input screen 830.

[0038] Reference numeral 830 denotes a product template setting value input screen, which has a product template detailed setting value input section 840 for inputting information about the template. The product template setting value input screen 830 further has an edit product template button 804 for opening the product template print setting screen 820, and a save product template button 805 for saving the set product template.

[0039] The product template detailed setting value input section 840 will now be described. It is assumed that the product template detailed setting value input section 840 included in the product template management screen 800 and the product template setting value input screen 830 are the same. 841 is a product template name input section. 842 is a category selection section. A pull-down menu is used to select from a list of product template categories (bookbinding, flyers, etc.). 843 is a category edit button. Pressing the category edit button 843 opens a category edit screen 850. 844 is a display checkbox. Unchecking this disables the hot folder application 400 from obtaining information about the corresponding product template. 845 is an icon selection button. Pressing this button opens a file selection dialog box, and the selected image file is set as the product template icon. Here, it is also possible to select from icons predetermined by the cloud service 110. 846 is a description input section. The user inputs and sets a description for the target product template.

[0040] The category edit screen 850 will now be described. 851 is a category list display area. 852 is a category delete button. When pressed, the category selected in the category list display area 851 is deleted. 853 is an additional category name input area. 854 is an add category button. When pressed, a category is added to the list with the category name input in the additional category name input area 853. 855 is a close button. When pressed, the category edit screen 850 is closed.

[0041] The created product template, category, and uploaded icon data are stored in the template storage unit 602.

[0042] On the product template management screen 800, even if the setting values ​​in the product template detailed setting value input section 840 are changed, they can be saved by using the product template save button 805. The file to be selected on the preview file selection screen 810 may be a preview file that has been saved in advance in the template storage section 602.

[0043] The screen shown here allows a product template to be created and edited using the cloud service 110 from the user interface of the information processing device 100. The creation and editing of the product template here can also be performed from other information processing devices.

[0044] 9 shows a hot folder management screen provided by the hot folder application 400 in this embodiment. This screen is displayed, for example, on a browser of the information processing device 100. Each screen in FIG. 9 does not necessarily have to be exactly as shown in FIG. 9 as long as it allows a product template to be selected and a hot folder to be created. The screen may also be displayed by a means other than a browser. For example, the information processing device 100 may be configured to store screen information for the following screens, access the cloud service 110 as needed to acquire information, and display the screen.

[0045] Reference numeral 900 denotes a hot folder management screen. Reference numeral 901 denotes an add hot folder button. When pressed, a hot folder creation screen 910 opens. Reference numeral 902 denotes a delete hot folder button. When pressed, a hot folder selected in a hot folder list 905 is deleted from the hot folder storage unit 401. Reference numeral 903 denotes a start hot folder monitoring button. When pressed, monitoring of the hot folder selected in the hot folder list 905 begins. Reference numeral 904 denotes a stop hot folder monitoring button. When pressed, monitoring of the hot folder selected in the hot folder list 905 stops. Reference numeral 905 denotes a hot folder list. This acquires and displays the list of hot folders from the hot folder storage unit 401. Reference numeral 920 denotes an input section for detailed hot folder settings. Details will be explained in 921 to 928. Reference numeral 906 denotes a save hot folder button. When pressed, the current detailed settings and product template are saved and updated in the hot folder storage unit 401.

[0046] Reference numeral 910 denotes a hot folder creation screen. Reference numeral 911 denotes a button for canceling hot folder creation. Pressing this button closes the hot folder creation screen 910. The hot folder creation screen 910 further includes a hot folder detailed setting value input section 920 and a hot folder save button 906.

[0047] The hot folder detailed setting value input section 920 will now be described. 921 is a hot folder name input section. 922 is a product template selection section. 923 is a product template details button. When pressed, a product template details screen 940 opens. 924 is a product template selection button. When pressed, a product template selection screen 930 opens. 925 is an input folder input section. The folder set here is monitored by the hot folder monitoring section 404. 926 is an input folder reference button. When pressed, a file selection dialog opens, and the path of the selected folder is entered in the input folder input section 925. 927 is a log folder input section. The folder specified here becomes the log output destination for hot folder-related processing. 928 is a log folder reference button. When pressed, a file selection dialog opens, and the path of the selected folder is entered in the log folder input section 929.

[0048] Reference numeral 930 denotes a product template selection screen. Reference numeral 931 denotes a product template acquisition button. Pressing this button requests the cloud service 110 to acquire all product templates held by the cloud service 110, and synchronizes the product templates held in the template storage unit 602 with the product templates in the template storage unit 402. A configuration may be provided for logging in to the hot folder application 400, and a list of product templates corresponding to the logged-in user may be acquired. The user selects a desired product template from the acquired list of product templates. Reference numeral 932 denotes a button for canceling product template selection. Pressing this button closes the product template selection screen 930. Reference numeral 933 denotes a save selected product template button. Pressing this button sets the currently selected product template as the product template to be applied to the hot folder, and closes the product template selection screen 930. In other words, this screen allows one hot folder to be linked to one product template registered in the cloud service 110.

[0049] Reference numeral 940 denotes a product template details screen. It displays detailed information about the product template selected in the product template selection section 922. The information displayed is the data set in the product template description and the print settings of the product template. Alternatively, other information may be displayed in addition. Reference numeral 941 denotes a close button. Pressing this button closes the product template details screen 940.

[0050] This screen allows a hot folder to be created using the hot folder application 400 from the user interface of the information processing device 100. Also, a product template 1403 can be obtained from the cloud service 110 and applied to the created hot folder. In other words, it is possible to link the information on the hot folder stored locally on the information processing device with the information on the hot folder stored in the cloud service 110.

[0051] 10 is a diagram showing the display of the product template management screen 800 in the cloud service 110 and the flow of creating a product template. The following processing is executed by the CPU 201 of the cloud service 110. The processing in FIG. 10 does not necessarily have to be exactly as shown in FIG. 10 as long as it is possible to create a product template. The processing in this flowchart is started, for example, when a user starts the hot folder application 400 and requests the cloud service 110 to display the product template management screen 800 by selecting a specific button.

[0052] In S1001, the cloud service 110 requests the template management unit 601 to display the product template management screen 800.

[0053] In S1002, the template management unit 601 requests and acquires information about the product template from the template storage unit 602.

[0054] In S1003, the template management unit 601 provides the product template management screen 800 including a list of the acquired product templates.

[0055] In S1010, the template management unit 601 starts the product template creation process when the user presses the product template addition button 801 as a trigger.

[0056] In S1011 , the template management unit 601 uploads the preview file selected by the user on the preview file selection screen 810 to the cloud service 110 .

[0057] In S1012 , the template management unit 601 accepts a user operation in the print setting section 822 and selects the image forming device 101 .

[0058] In S1013, the template management unit 601 determines whether communication is possible with the image forming device 101 selected in S1012. To make this determination, the template management unit 601 sends a request to confirm communication with the image forming device 101 to the print job transmission / reception unit 408 of the information processing device 100. The print job transmission / reception unit 408 confirms communication with the image forming device 101 using a network command, and responds to the template management unit 601 whether communication is possible. If communication is possible, the process proceeds to S1015, and if communication is not possible, the process proceeds to S1014. It is assumed that the user has registered information about the image forming device in the cloud service 110 in advance.

[0059] In S1014, the template management unit 601 displays a communication error and transitions to S1012.

[0060] In S1015, the template management unit 601 acquires the capability information file 701 from the image forming apparatus 101 and reflects selectable print settings in the print setting unit 822.

[0061] In S1016, the template management unit 601 holds the print setting values ​​set by the user in the print setting unit 822. The setting values ​​here include, for example, paper settings, imposition settings, color settings, and number of copies settings.

[0062] In S1017 , the template management unit 601 holds the setting values ​​of the product template input by the user in the product template detailed setting value input area 840 .

[0063] In S1018, the template management unit 601 stores the created product template 1409 together with its identifier in the template storage unit 602 based on the user pressing the product template save button 805.

[0064] By performing the processing of this flowchart, the user can register a product template in the cloud service 110. This registration operation can be performed from any information processing device.

[0065] Fig. 11 is a diagram showing a flow of updating a product template in the cloud service 110. The following processing is executed by the CPU 201 of the cloud service 110. As long as the product template can be updated, the processing does not necessarily have to be exactly as shown in Fig. 11.

[0066] In S1101, the template management unit 601 identifies a product template selected by the user from the product template list 803.

[0067] In S1102, the template management unit 601 acquires information on the product template identified in S1101 and reflects the current setting values ​​in the product template detailed setting value input section 840.

[0068] In S1103, if the template management unit 601 determines that the user has pressed the edit product template button 804, that is, if it determines that the print settings are to be changed, the process proceeds to S1011. If it determines that the edit product template button 804 has not been pressed, for example, if the user is editing only the items included in the product template detailed setting value input section 840, the process proceeds to S1017.

[0069] The processing from S1011 onwards is the same as that in FIG. 10, so the same steps are given the same numbers and the description thereof will be omitted.

[0070] By performing the processing of this flowchart, the user can edit the product template 1409 managed by the cloud service 110 at any time from any client device.

[0071] 12 shows the display of the hot folder management screen 900 of the hot folder application 400 and the hot folder creation flow. The following processing is executed by the CPU 201 of the information processing device 100. The processing shown in FIG. 12 does not necessarily have to be exactly as shown, as long as a hot folder can be created. The processing of this flowchart is started, for example, when a user starts the hot folder application 400 and requests the display of the hot folder management screen 900 by selecting a predetermined button.

[0072] In step S1201, the information processing apparatus 100 sends a request from the user to the hot folder management unit 405 to display the hot folder management screen 900.

[0073] In S1202, the hot folder management unit 405 requests and acquires hot folder information from the hot folder storage unit 401.

[0074] In S1203, the hot folder management unit 405 displays the acquired list of hot folders on the hot folder management screen 900.

[0075] In S1211 , the hot folder management unit 405 holds the setting values ​​of the product template input by the user in the hot folder detailed setting value input unit 920 .

[0076] In S1212, the hot folder management unit 405 determines whether the user has pressed the product template acquisition button 931. If the product template acquisition button 931 has been pressed, the process proceeds to S1213. If the cancel button 932 or the save button 933 has been pressed, the process proceeds to S1215.

[0077] In S1213 , the hot folder management unit 405 requests product template information from the cloud service 110 , and stores the product template information acquired based on the request in the template storage unit 402 .

[0078] In S1214, the hot folder management unit 405 selects and holds the product template selected by the user in the product template selection unit 922.

[0079] In S1215, the hot folder management unit 405 creates a hot folder with the setting values ​​set in the hot folder detailed setting value input unit 920, triggered by the user pressing the save button 906, and saves the hot folder in the hot folder storage unit 401. Here, the identifier of the product template registered in the cloud service 110 is also saved.

[0080] This flowchart enables the hot folder application 400 to obtain a product template 1403 from the cloud service 110 and apply it to a hot folder created on the user's own device. By selecting a desired product template from the product templates centrally managed by the cloud service 110, the user can use the product template from the user's information processing device.

[0081] 13 is a flowchart showing the processing of the hot folder application 400 in this embodiment. Specifically, the hot folder application monitors a target folder and shows the processing when a file is stored in the folder. The hot folder application 400 is an application that runs on the information processing device 100 and is executed by the CPU 201 of the information processing device 100.

[0082] In step S1301, the hot folder application 400 is started, processing begins, and the process proceeds to step S1302.

[0083] In step S1302, the CPU 201 monitors whether a file is stored in a folder that is a hot folder monitoring target. Information about the monitoring folder is written in the hot folder setting file 1308. After step S1302, the process proceeds to step S1303.

[0084] In step S1303, the CPU 201 determines whether a file has been stored in a monitoring folder that is a target for hot folders. Based on the extension of the stored file, it is determined whether the file type is a target for processing. In this embodiment, the target file must be a PDF file with the extension ".pdf." If a file has been stored, the process proceeds to step S1304; if not, the process proceeds to step S1302.

[0085] In step S1304, the CPU 201 obtains the template identifier corresponding to the folder in which the file was stored from the hot folder settings file 1308. For example, if a file was added to the folder indicated by C:\Users\username\Desktop\Book_Product, the template identifier is {C821163A-4B80-4185-B87A-650F2CA8C4F3}. After step S1304 is completed, the process proceeds to step S1305. The hot folder application 400 associates the hot folder information in the hot folder application 400 with the product template information in the cloud service 110 and stores them in association with each other through the hot folder registration process described above.

[0086] In step S1305, the CPU 201 uploads the PDF file and the template identifier corresponding to the folder to the cloud service 110. The URL and access key of the upload destination are saved in advance in the hot folder application 400. In other words, it is assumed that URL information and an access key for accessing the cloud service 110 are set in advance in the hot folder application 400. The HTTP POST method is used for uploading. This step corresponds to step S1402 in FIG. 14, and the cloud service can receive the information sent by the CPU 201 of the information processing device 100 in this step in step S1402. The cloud service 110 has a WebAPI for accepting uploads. When step S1305 is completed, the process transitions to step S1306.

[0087] In step S1306, it is determined whether the upload performed in step S1305 was successful. This is determined by whether the response to the POST method uploaded in step S1305 is 200 (successful). Instead of the response to the POST method, a Web API that checks success or failure may be used. If the success of the upload is confirmed, the process proceeds to step S1302 to prepare for the next file upload. If the upload fails, the process proceeds to step S1307.

[0088] In step S1307, the CPU 201 notifies the user that an error has occurred by displaying a message on the screen. After step S1307 is completed, the application processing is terminated (S1309), restarted, and the process returns to step 1301.

[0089] According to this flowchart, when a target file is stored in a monitored folder, the hot folder application can upload the target file to the cloud together with its template identifier.

[0090] 14 is a flowchart of the cloud application in this embodiment. The cloud application is executed by the CPU 201 of the cloud service 110.

[0091] When the cloud application service starts, the CPU 201 starts executing processing from step S1401. The service is configured to be started when a WebAPI for receiving a PDF file and a template identifier is accessed.

[0092] When the start process of step S1401 is completed, the process proceeds to step S1402.

[0093] In step S1402, the CPU 201 receives the PDF file and template identifier from the hot folder API. This step corresponds to step S1305 in Fig. 13, and the hot folder application 400 can receive the PDF file and template identifier sent by the CPU 201 of the information processing apparatus 100. The CPU 201 saves the PDF file and template identifier in the job storage unit 603. After step S1402, the process proceeds to step S1403.

[0094] In step S1403, the CPU 201 retrieves a template from the template management unit 602 using the template identifier saved in the job storage unit 603 as a key. 1408 is a table for converting a template identifier into a template file name. In this example, the file name A4Booklet can be retrieved from the template identifier {C821163A-4B80-4185-B87A-650F2CA8C4F3}. The CPU 201 can retrieve a product template 1409 from the template management unit 602 by specifying the file name A4Booklet.

[0095] Product template 1409 shows the structure of a product template. This product template has the following fields: name, category, display, icon, and description. The name (Sample Temp) is the display name of the product template and corresponds to the data entered in the product template name input field 841. The category (booklet) corresponds to the data entered in the category selection field 842. The display corresponds to the data entered in the display checkbox 844. The icon corresponds to the data entered in the icon selection button 845. The product template also includes the print setting values ​​set in the print setting field 822: type of finish, print side, finished size, layout, cover, punching, imposition, product paper, and print mark. The update date and time also includes the date and time of the last update of the product template. The product template also includes a template identifier and the printer ID of the output destination. The set of setting values ​​included in the product template is not limited to those shown here and can include various printing conditions reflected in the printing device. After step S1403, the process proceeds to step S1404.

[0096] In step S1404, the CPU 201 executes imposition processing of the PDF stored in the job storage unit 603 in accordance with the product template 1409. The imposition processing is executed using the layout generation unit 607. Examples of imposition processing include 2-in-1 layout and bookbinding layout. Once the image formation processing is completed in step S1404, the process proceeds to step S1405.

[0097] In step S1405, the CPU 201 performs JDF creation processing. A JDF for printing is created using the print job information generation unit 609. In this embodiment, a JDF specifying A4, plain paper, and saddle stitching is created. Other necessary items may also be specified. After step S1405, the process proceeds to step S1406.

[0098] In step S1406, the CPU 201 performs job execution processing. Here, the imposition processing result generated in step S1404 is used to convert the result into PDF data for printing by the print data conversion unit 608. Furthermore, the job transmission unit 605 performs job transmission processing to the printer with the printer ID stored in the product template 1409. After step S1406, the process proceeds to step S1407.

[0099] Step S1407 is termination processing, and the cloud service resources are released until the hot folder API is accessed again. Note that, although this embodiment has been described as being configured to use a serverless service to access the hot folder API and then use the cloud service resources, the present invention is not limited to this, and it goes without saying that it can also be realized in a configuration in which a server is used at all times.

[0100] This flowchart enables printing using the appropriate imposition process based on the PDF file and template identifier uploaded to the cloud. Because image formation processes such as imposition are performed in the cloud, even users with client devices with low image formation processing capabilities can generate appropriate print jobs.

[0101] FIG. 15 is a flowchart showing the processing of the print job transmitting / receiving unit 408 in this embodiment.

[0102] The processing by the print job transmitting / receiving unit 408 is executed by the CPU 201 of the information processing apparatus 100 .

[0103] The CPU 201 executes the print job transmission / reception unit as a background service (1501).

[0104] In step S1502, the CPU 201 waits for a print job to be sent from the cloud service 110. When step S1406 is executed in the cloud service 110, the print job is sent and the process proceeds to step S1503.

[0105] In step S1503, the CPU 201 downloads the PDF file to be printed from the cloud service 110. This PDF file was generated in step S1406. The CPU 201 also downloads the JDF generated in step S1405. Once the download of the necessary data is complete, the process proceeds to step S1504.

[0106] In step S1504, the CPU 201 executes print processing by transmitting the PDF file and JDF downloaded in step S1503 to the image forming apparatus.

[0107] After executing the print process, the CPU 201 proceeds to step S1502 and waits again for the transmission of a print job.

[0108] According to this flowchart, an information processing device can download a print job generated in the cloud and instruct a printer to print. Here, an example is shown in which the information processing device 100 obtains a print job from the cloud service 110 and sends the print job to an image forming device, but this is not limiting. The cloud service 110 may also be configured to send the print job directly to the image forming device without going through the information processing device 100.

[0109] 16 is a diagram showing the structure of a job management table in this embodiment. The job management table is a table used by the cloud service 110 to manage the execution status of printing in each image forming apparatus via a hot folder.

[0110] FIG. 16(a) is an example of information stored in the job storage unit 603. 1601 is a job ID for uniquely identifying a job. 1602 is a job name indicating the name of the job. 1603 is a destination printer ID for indicating the printer to be used to print the job. 1604 is a paper ID for indicating the paper to be used to print the job. 1605 is an instruction job flag for indicating whether this job is an instruction job. If it is an instruction job, it is True; if it is not an instruction job, it is False.

[0111] Numeral 1606 is the main job, indicating which job the instruction is for, if it is an instruction job. If it is not an instruction job, this field is blank, and if it is an instruction job, the job ID of the target job is entered to indicate which job the instruction is for. Numeral 1607 is the printing end date and time of the job. This field is blank if printing has not finished. Numeral 1608 is the job status. Ready is stored if the job has not been sent to the printer, Printing is stored if printing is in progress, and Completed when printing has finished. One job is generated when a file is stored once in one hot folder.

[0112] 16(b) is an example of information stored in the image forming device information storage unit 604. 1621 is a printer ID for uniquely identifying the printer. 1622 is a printer name indicating the name of the printer. 1623 is the IP address of the printer. In this way, the cloud service 110 has information on multiple image forming devices, and can issue an instruction to execute a print job to an image forming device selected from that information.

[0113] FIG. 16C is an example of information stored in the job storage unit 603. 1631 is a job ID for uniquely identifying a job. 1632 is a job name indicating the name of the job. 1633 is a paper ID indicating the paper used to print the job. 1634 is the printing end date and time of the job. If printing has not finished, this field is blank. 1635 is the job status. If printing is not in progress, "Ready" is stored; if printing is in progress, "Printing" is stored; and if printing has finished, "Completed" is stored.

[0114] 17 is a management screen of the image forming apparatus 101, which is provided by the print job transmitting / receiving unit 408 in this embodiment. The management screen is displayed on the browser of the information processing apparatus 100. Each screen in FIG. 17 does not necessarily have to be exactly as shown in FIG. 17, as long as it is possible to register the image forming apparatus 101 in the cloud service 110. Furthermore, the screen may be displayed by means other than a browser.

[0115] Reference numeral 1700 denotes an image forming device management screen. Reference numeral 1701 denotes an image forming device search button. When pressed, an image forming device search screen 1710 opens. Reference numeral 1702 denotes an image forming device deletion button. This executes processing to delete the image forming device selected in the image forming device list 1703 from the image forming device information storage unit 604. Reference numeral 1703 denotes an area showing the image forming device list. A list of product templates saved in the image forming device information storage unit 604 is obtained from the image forming device information storage unit 604 and displayed.

[0116] Reference numeral 1704 denotes a detailed setting value display section for an image forming device, which displays device information of a specific image forming device acquired from the image forming device information storage section 604. Here, the device information of the image forming device selected in the image forming device list 1703 is displayed.

[0117] Reference numeral 1705 denotes an image forming device name input section. Reference numeral 1706 denotes an image forming device name change save button. The name of the image forming device changed in the image forming device name input section 1705 is saved in the image forming device information storage section 604. Reference numeral 1707 denotes an image forming device information display section, which displays the host name, device ID, etc. of the image forming device.

[0118] Reference numeral 1710 denotes an image forming device search screen. Reference numeral 1711 denotes an IP address input section. The range of IP addresses of image forming devices to be searched for is specified. Reference numeral 1712 denotes an image forming device search start button. When pressed, the local network to which the information processing device 100 is connected is searched for image forming devices having the IP addresses specified in the IP address input section 1711. At the same time, the image forming device search screen 1710 is closed. The search results are displayed on an image forming device search result display screen 1708. Reference numeral 1708 denotes an image forming device search result display screen. Reference numeral 1721 denotes a list of image forming device search results. Reference numeral 1722 denotes a cancel button. When pressed, the screen returns to the initial screen displaying reference numerals 1701 to 1707. Reference numeral 1723 denotes an add image forming device button. When pressed, a process is executed to save the image forming device selected in the image forming device search result list 1721 in the image forming device information storage unit 604. In other words, information about the added image forming device is sent to the cloud service 110, thereby newly registering information about the image forming device in the cloud service 110.

[0119] This screen allows the information of the image forming apparatus 101 to be registered in the cloud service 110 from the user interface of the information processing apparatus 100 .

[0120] Fig. 18(a) is a diagram showing the flow of adding an image forming device in the information processing device 100. The following processing is executed by the CPU 201 of the information processing device 100. Fig. 18(a) only requires that an image forming device can be added, and does not necessarily have to be exactly as shown in Fig. 18(a).

[0121] In step S1801 , the print job transmitting / receiving unit 408 searches for an image forming device within the range of IP addresses input by the user in the IP address input unit 1711 .

[0122] In S1802, the print job transmitting / receiving unit 408 determines whether or not there is an image forming apparatus to be searched for. If there is one or more, the process proceeds to S1804, and if there is no image forming apparatus, the process proceeds to S1803.

[0123] In S1803, the print job transmitting / receiving unit 408 displays "no match" on the browser of the information processing apparatus 100, and the process ends.

[0124] In step S1804 , the print job transmission / reception unit 408 holds information about the image forming device selected by the user from the image forming device search list 1721 and the name input by the user to the image forming device name input unit 1705 .

[0125] In S1805, the print job transmission / reception unit 408 transmits a registration request for the image forming apparatus to the cloud service 110. Here, the information held in S1804 is transmitted to the cloud service 110. The registration processing result from the cloud service 110 is displayed on the browser of the information processing apparatus 100, and the processing ends.

[0126] According to this flowchart, information about the image forming apparatus 101 can be registered in the cloud service 110 from the print job transmitting / receiving unit 408 .

[0127] Fig. 18(b) is a diagram showing the flow of adding an image forming device in the cloud service 110. The following processing is executed by the CPU 201 of the cloud service 110. Fig. 18(b) does not necessarily have to be exactly as shown in Fig. 18(b) as long as it is possible to add an image forming device.

[0128] In S1811, the image forming apparatus management unit 612 receives a registration request for the image forming apparatus from the information processing apparatus 100.

[0129] In S1812, the image forming device management unit 612 analyzes the registration request and determines whether a corresponding device exists by comparing it with the image forming device information stored in the image forming device information storage unit 604. If a corresponding device does not exist, the process proceeds to S1814, and if a corresponding device exists, the process proceeds to S1813.

[0130] In S1813, the image forming apparatus management unit 612 returns a response indicating that registration has failed to the information processing apparatus 100. Here, for example, the image forming apparatus management unit 612 notifies the user that the image forming apparatus that the user has attempted to register has already been registered.

[0131] In S1814, the image forming device management unit 612 registers the image forming device specified in the registration request in the image forming device information storage unit 604, returns a response indicating successful registration to the information processing device 100, and terminates the process. An example of the information about the image forming device 101 to be saved is as shown in FIG. 16(b).

[0132] According to this flowchart, the cloud service 110 can process the registration request for the image forming device 101 acquired from the print job transmission / reception unit 408 and register the image forming device 101.

[0133] By managing product templates using a cloud service according to this embodiment, the same product template can be used by information processing devices that are clients connected from different networks.

[0134] <Embodiment 2> In the second embodiment, an example will be described in which, when a file is stored in a hot folder and processing of a product template corresponding to the hot folder is executed, product template update processing is performed if the product template settings in the cloud have been changed. The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences will be described.

[0135] Fig. 19 is a diagram showing the flow of the product template update process when a file is stored in a hot folder. The basic process flow is the same as in Fig. 13, and is executed by the CPU 201 of the information processing device 100. The process in Fig. 19 only needs to be able to update the product template linked to the hot folder, and does not necessarily have to be exactly as shown in Fig. 19. The same reference numerals are used for the components already mentioned, and their explanations will be omitted.

[0136] In S1901, the hot folder application 400 uses the template identifier acquired in S1304 to acquire the update date and time of the target product template 1403 from the cloud service 110, from the product template update table 1910. The product template update table 1910 is saved in the template storage unit 602, and updates the update date and time of the relevant product template when the product template is created / updated.

[0137] In S1902, the hot folder application 400 determines whether the update date and time of the target product template acquired from the cloud service 110 is newer than the update date and time of the target product template stored in the template storage unit 402. If it is newer, the process proceeds to S1903; otherwise, the process proceeds to S1305.

[0138] In S1903, the hot folder application 400 acquires the target product template 1403 from the cloud service 110 and saves it in the template storage unit 402 by overwriting it.

[0139] In S1904, the hot folder application 400 notifies the user that the target product template has been updated.

[0140] This flowchart makes it possible to check whether the relevant product template has been updated before uploading print data from the hot folder application 400 to the cloud service 110. If the product template has been updated, the product template 1403 can be acquired from the cloud service 110 and synchronized with the locally stored product template.

[0141] According to this embodiment, even if a product template is updated by a cloud service, the target product template information held by the information processing device can be synchronized.

[0142] <Embodiment 3> In the third embodiment, a configuration for managing product templates from the hot folder application 400 using the cloud service 110 will be described with reference to Fig. 20. The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences will be described.

[0143] Fig. 20(a) is a software configuration diagram of the information processing device 100 in this embodiment. The same reference numerals are used for components already mentioned, and descriptions thereof will be omitted. The configuration in Fig. 20(a) is a functional configuration realized by executing a program on a computer, and does not necessarily have to be exactly as shown in Fig. 20(a). For example, there can be variations in the configuration, such as integrating multiple functional blocks, or having part of a certain functional block in Fig. 20(a) in another functional block.

[0144] A template management unit 2000 issues a request to the template management unit 601 of the cloud service 110 to display the product template management screen 800 and to create / update / delete a product template.

[0145] Fig. 20(b) is a hot folder management screen provided by the hot folder application 400 in this embodiment, and is displayed on the browser of the information processing device 100. Fig. 20(b) does not necessarily have to be exactly as shown in Fig. 20(b), as long as product templates can be created from the hot folder application 400. Display may also be by means other than a browser. The same reference numerals are used for components already mentioned, and descriptions thereof will be omitted.

[0146] A template management button 2010 is displayed. When the button is pressed, a product template management screen 800 is acquired from the cloud service 110 and displayed.

[0147] This screen allows the user to create and edit a product template 1403 using the hot folder application 400 from the user interface of the information processing device 100.

[0148] According to this embodiment, a product template can be created using the product template creation function of the cloud service from a hot folder application included in the information processing apparatus.

[0149] <Other embodiments> In the above example, files stored in a hot folder are printed, but this is not limited to this. For example, the present invention can also be applied to a configuration in which files stored in a hot folder are transferred to another device. Also, while the above example shows a hot folder configuration, the configuration is not limited to a folder, as long as processing is performed based on settings.

[0150] The present invention can also be realized by executing the following process: software (program) that realizes the functions of the above-described embodiments is supplied to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads and executes the program. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

[0151] The disclosure of this embodiment includes the following configurations, methods, and programs.

[0152] (Configuration 1) A server system capable of communicating with an information processing device, a providing means for providing information for displaying a setting screen for setting a hot folder in the information processing device to the information processing device; and a registration unit that registers information about a hot folder in association with a setting value associated with the hot folder based on an operation received from a user on the setting screen.

[0153] (Configuration 2) The server system according to configuration 1, further comprising an editing unit that edits setting values ​​associated with the hot folder registered by the registration unit.

[0154] (Configuration 3) 3. The server system according to configuration 1 or 2, wherein the setting values ​​associated with the hot folder are a group of setting values ​​related to print settings.

[0155] (Configuration 4) The server system according to any one of configurations 1 to 3, further comprising an acquisition means for acquiring capability information of the target image processing device, and the provision means for providing information for displaying a print setting screen according to the capability information acquired by the acquisition means.

[0156] (Configuration 5) 5. The server system according to any one of configurations 1 to 4, wherein the providing means further provides information for displaying a preview screen according to setting values ​​set by the user on the setting screen.

[0157] (Configuration 6) 6. The server system according to any one of configurations 1 to 5, wherein the providing means provides information for displaying a selection screen for selecting a file to be used on the preview screen.

[0158] (Configuration 7) 7. The server system according to any one of configurations 1 to 6, wherein the setting values ​​associated with the hot folder include the name and category of the hot folder.

[0159] (Configuration 8) 8. The server system according to any one of configurations 1 to 7, wherein the setting values ​​associated with the hot folder include paper settings, imposition settings, color settings, and number of copies settings.

[0160] (Configuration 9) 9. The server system according to any one of configurations 1 to 8, wherein the information registered by the registration means by the application executed on the information processing device is associated with a hot folder.

[0161] (Configuration 10) The server system described in any one of configurations 1 to 9, characterized in that when a file is stored in a hot folder in the information processing device, processing of the file is performed using setting values ​​linked to the hot folder by the registration means.

[0162] (Method 1) A control method executed by a server system capable of communicating with an information processing device, The control method a providing step of providing information for displaying a setting screen for setting a hot folder in the information processing device to the information processing device; and a registration step of registering information about a hot folder in association with a setting value associated with the hot folder, based on an operation received from a user on the setting screen.

[0163] (Program 1) A program for causing a computer to function as each means of the server system described in any one of configurations 1 to 10. [Explanation of symbols]

[0164] 100 Information processing device 101 Image forming device 110 Cloud Services 400 Hot Folder Application 601 Template Management Department 1403 Product Templates

Claims

1. A server system capable of communicating with an information processing device, a providing means for providing information for displaying a setting screen for setting a hot folder in the information processing device to the information processing device; and a registration unit that registers information about a hot folder in association with a setting value associated with the hot folder based on an operation received from a user on the setting screen.

2. 2. The server system according to claim 1, further comprising an editing unit that edits a setting value associated with the hot folder registered by the registration unit.

3. The server system according to claim 1 , wherein the setting values ​​associated with the hot folder are a group of setting values ​​related to print settings.

4. The server system according to claim 1, further comprising an acquisition means for acquiring capability information of the target image processing device, and the providing means for providing information to display a printing setting screen according to the capability information acquired by the acquisition means.

5. 2. The server system according to claim 1, wherein the providing unit further provides information for displaying a preview screen according to the setting values ​​set by the user on the setting screen.

6. 2. The server system according to claim 1, wherein said providing means provides information for displaying a selection screen for selecting a file to be used on said preview screen.

7. The server system according to claim 1 , wherein the setting values ​​associated with the hot folder include a name and a category of the hot folder.

8. The server system according to claim 1 , wherein the setting values ​​associated with the hot folder include paper settings, imposition settings, color settings, and number of copies settings.

9. 2. The server system according to claim 1, wherein the information registered by the registration means by the application executed on the information processing device is associated with a hot folder.

10. 2. The server system according to claim 1, wherein when a file is stored in a hot folder in the information processing device, processing of the file is executed using a setting value associated with the hot folder by the registration means.

11. A control method executed by a server system capable of communicating with an information processing device, The control method a providing step of providing information for displaying a setting screen for setting a hot folder in the information processing device to the information processing device; and a registration step of registering information about a hot folder in association with a setting value associated with the hot folder, based on an operation received from a user on the setting screen.

12. A program for causing a computer to function as each of the means of the server system according to any one of claims 1 to 10.

Images