Image processor, method for controlling the same, and program
Patent Information
- Application Number
- JP2025019365
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-07
- Publication Date
- 2025-05-08
- Estimated Expiration
- 2034-08-28
AI Technical Summary
Existing fax document management systems face issues with data loss due to overlapping file names, and users struggle to identify desired documents as unique identification numbers are used as file names, reducing visibility.
An information processing device is configured with a setting screen that allows users to create unique file names by selecting from multiple items, including date and time, to prevent file name duplication while maintaining user visibility.
This solution prevents data loss from overlapping file names without compromising user visibility, allowing users to easily identify and manage their fax documents.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device, a control method thereof, and a program. [Background technology]
[0002] In business using fax, fax documents received by MFP or fax are digitized using the scanning function of MFP or document scanner and stored in a file server. Here, MFP is an abbreviation of Multi Function Peripheral, which is an example of an image forming device having multiple functions such as a copier, scanner, and fax. In this case, in order to improve the efficiency of the digitization and storage work in the file server, a fax reception transfer system is constructed that digitizes fax documents and automatically stores them in the file server according to the attributes of the fax documents. In such a system, a file name is created according to the telephone number of the sender of the fax document and other attribute information, and the fax document is stored in the file server. In this case, if the file name is duplicated, the existing fax document is overwritten with the new fax document, which may result in the loss of the stored fax document.
[0003] As a countermeasure against such loss of stored fax documents, for example, Patent Document 1 discloses a technology in which a fax server assigns a unique identification number as a file name to fax documents received by the fax server and stores them. By using the technology of Patent Document 1, a unique identification number for the communication network or a unique identification number within the fax server is used as the file name of the fax document, so that a unique file name can be created and data loss due to duplication of file names can be prevented. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2002-64534 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, in the technology described in Patent Document 1, the system forcibly assigns a unique identification number as a file name, which reduces the visibility of the file for the user. This makes it difficult for the user to identify the desired fax document when using the stored fax documents, and it is troublesome to search for the desired document.
[0006] An object of the present invention is to solve the above problems of the prior art.
[0007] A feature of the present invention is to provide a technique that enables a file name to be set so as to be unique and with improved visibility for the user. [Means for solving the problem]
[0008] In order to achieve the above object, an information processing device according to one aspect of the present invention has the following configuration. A providing means for providing a setting screen for creating a file name of a file, The setting screen includes a plurality of items that can be used to create a file name, and the setting screen allows the user to select one or more of the plurality of items, and is characterized in that a display is provided to prevent the registration of an item to be used to create a file name when an item related to date and time included in the plurality of items is not selected. Effect of the Invention
[0009] According to the present invention, data loss due to file name duplication can be prevented without sacrificing user visibility while providing users with increased flexibility in setting file names.
[0010] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same reference numerals are used to designate the same or similar components throughout the drawings. [Brief description of the drawings]
[0011] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. [Figure 1] 1 is a diagram showing the overall configuration of an information processing system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram illustrating the hardware configuration of the MFP according to the first embodiment. [Diagram 3] FIG. 2 is a block diagram showing the hardware configuration of a file server according to the first embodiment. [Figure 4] 2 is a functional block diagram for explaining the configuration of a software module of the MFP according to the first embodiment. [Diagram 5] FIG. 2 is a functional block diagram for explaining the configuration of software modules of the file server according to the first embodiment. [Figure 6] 5A and 5B are diagrams for explaining an example of destination information stored in a destination information management unit of the MFP according to the first embodiment. [Figure 7] 4 is a view showing an example of a file storing transfer setting information stored in a transfer setting information management unit of the MFP according to the first embodiment. [Figure 8] 4 is a view showing an example of a status display screen displayed on the operation unit of the MFP according to the first embodiment. [Figure 9] 4 shows an example of a file server setting screen displayed by the MFP according to the first embodiment. [Figure 10] 6 shows an example of a setting screen for setting a file naming rule displayed by the MFP according to the first embodiment. [Figure 11] 6 is a view showing an example of a setting screen for setting a folder naming rule displayed by the MFP according to the first embodiment. [Figure 12] 4 is a view showing an example of a test transmission screen displayed by the MFP according to the first embodiment. [Figure 13] 6 is a flowchart for explaining processing for setting a file server, a file naming rule, and a folder naming rule by the MFP according to the first embodiment. [Figure 14] 4 is a sequence diagram for explaining a process in which the MFP according to the first embodiment receives image data by fax and transfers an image file of the received image data to a file server. [Figure 15] 5 is a flowchart for explaining a fax reception process by the MFP according to the first embodiment. [Figure 16] 16 is a flowchart for explaining the process of creating a file name for an image file to be transferred in S1505 of FIG. [Figure 17] 16 is a flowchart for explaining the process of creating a folder name of a file server in which an image file to be transferred is stored, in step S1506 of FIG. 15. [Figure 18] 14 is a flowchart for explaining the file naming rule setting process in S1306 of FIG. 13. [Figure 19] FIG. 11 shows an example of a confirmation dialog displayed on the MFP according to the second embodiment of the present invention. [Figure 20] 10 is a flowchart for explaining a confirmation dialog display process by the MFP according to the second embodiment. [Figure 21] FIG. 11 is a diagram showing an example of forwarding setting information according to the second embodiment. [Figure 22] FIG. 11 is a view showing an example of a setting screen for a folder naming rule displayed on an MFP according to a third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, the embodiments of the present invention will be described in detail with reference to the accompanying 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. [Embodiment 1] First, a first embodiment of the present invention will be described. In the first embodiment, an example of a transfer setting process for a fax document, and a fax reception and an associated file transfer process in a system including an MFP, which is an example of the image forming apparatus of the present invention, and a file server having a file storage function will be described.
[0013] FIG. 1 is a diagram showing the overall configuration of an information processing system according to a first embodiment of the present invention.
[0014] In this information processing system, an MFP 110 and a file server 120 are connected via a LAN 100 .
[0015] The MFP 110 is a multifunction peripheral (multifunction processing device) having an operation unit 111, a scanner unit 112, and a printer unit 113, and is capable of receiving faxes by connecting to a public line network 150. In the information processing system according to the first embodiment, the MFP 110 is used as a receiving terminal for fax documents. The file server 120 authenticates the connecting terminal, and stores and manages the received file with a specified file name and folder name. However, the system according to the first embodiment is not limited to the number of components shown in FIG. 1. For example, the MFP and the file server may be configured as a single device by having a file server function inside the MFP 110. Also, the file server may be configured as a server on the Internet or a cloud system.
[0016] FIG. 2 is a block diagram illustrating the hardware configuration of the MFP 110 according to the first embodiment.
[0017] The operation unit 111 has a display unit with a touch panel function, various hard keys, etc., and displays information to the user according to data from the control unit 200, and inputs information according to user operations to the control unit 200. The scanner unit 112 reads an image of an original document, creates image data of the image, and supplies the image to the control unit 200. The printer unit 113 prints an image on a paper (sheet) based on the image data received from the control unit 200.
[0018] The control unit 200 is electrically connected to the operation unit 111, the scanner unit 112, and the printer unit 113, and is also connected to the LAN 100 via a network interface (I / F) 206. This enables communication via the LAN 100 using a communication protocol such as TCP / IP. In the control unit 200, a CPU 201, a ROM 202, a RAM 203, a HDD 204, an operation unit I / F 205, a network I / F 206, a scanner I / F 207, an image processing unit 208, and a printer I / F 209 are connected via a system bus 211. The CPU 201 executes a boot program in the ROM 202 to load the OS and control programs stored in the HDD 204 into the RAM 203, and generally controls the MFP 110 according to the programs. This control includes the execution of a program for implementing a flowchart described later. The boot program and various data of the MFP 110 are stored in the ROM 202. The RAM 203 provides a work memory for the CPU 201 to operate, and also provides an image memory for temporarily storing received image data and the like. The HDD 204 is a hard disk drive, and stores the OS, various programs, and image data. The operation unit I / F 205 is an interface unit for connecting the system bus 211 and the operation unit 111. The network I / F 206 is connected to the LAN 100 and the system bus 211, and inputs and outputs information via the network (LAN) 100. The scanner I / F 207 controls the interface between the scanner unit 112 and the control unit 200. The image processing unit 208 performs image processing such as rotation, color conversion, and image compression / expansion processing on image data input from the scanner unit 112 and image data output to the printer unit 113. The printer I / F 209 receives the image data processed by the image processing unit 208, and controls printing by the printer unit 113 according to attribute data attached to the image data. The modem 210 is connected to the public line network 150 and a system bus 211 , and transmits and receives faxes to and from an external fax terminal (not shown) via the public line network 150 .In the first embodiment, an example of MFP 110 capable of displaying a UI using operation unit 111 will be described. However, instead of this MFP 110, an information processing device such as a general-purpose computer or other image processing device may be used.
[0019] FIG. 3 is a block diagram showing the hardware configuration of the file server 120 according to the first embodiment.
[0020] The file server 120 includes a CPU 301, a RAM 302, a ROM 303, an input unit 304, a network I / F 305, a hard disk drive (HDD) 306, and a display unit 307, which are connected to each other via a system bus 308 so as to be able to communicate with each other. The ROM 303 stores a boot program, and when the power is turned on, the CPU 301 reads out the boot program and loads the OS and control programs installed in the HDD 306 into the RAM 302. The CPU 301 executes the programs loaded into the RAM 302, thereby realizing the functions of the file server 120. The CPU 301 also communicates with other devices on the LAN 100 connected via the network I / F 305. The input unit 304 includes a keyboard, a pointing device, and the like, and receives instructions from a user. The display unit 307 displays a menu screen, messages, and the like to the user. The display unit 307 may have a touch panel function.
[0021] 4 is a functional block diagram illustrating the configuration of software modules of the MFP 110 according to the embodiment 1. These software modules are installed in the HDD 204 of the MFP 110, and are deployed in the RAM 203 at the time of execution and executed under the control of the CPU 201.
[0022] The fax receiving unit 401 performs a receiving process when the modem 210 receives a fax. The fax receiving unit 401 receives facsimile data received via the modem 210, converts the data into PDF or the like to create a fax document, and stores the fax document as an image file in the HDD 204 by the temporary storage unit 403. The fax receiving unit 401 also creates a control file including a reception date and time, which is the date and time when the fax was received, and a sender number, which is the telephone number of an external fax terminal (not shown) connected via the public line network 150. Then, the fax receiving unit 401 stores the control file together with an image file (fax document) in the HDD 204. Note that, although the expression "fax document" is used in the embodiment, it goes without saying that this fax document includes a general image.
[0023] The transfer unit 402 transfers the image file stored in the HDD 204 by the fax receiving unit 401 to the file server 120. At this time, the transfer unit 402 reads out the reception date and time and the sender number from the control file stored in the HDD 204 by the fax receiving unit 401. The transfer unit 402 also acquires transfer setting information, which will be described later with reference to Fig. 7, from the transfer setting information management unit 404. The transfer unit 402 also transmits the sender number to the destination information management unit 405, and acquires the registration name corresponding to the sender number from the telephone number of the destination information, which will be described later with reference to Fig. 6.
[0024] FIG. 6 is a diagram illustrating an example of destination information stored in the destination information management unit 405 of the MFP 110 according to the first embodiment.
[0025] This destination information is registered in advance in the destination information management unit 405 by the user via the operation unit 111 of the MFP 110. Columns 601 to 603 and column 607 indicate the columns of the data records from row 604 to row 606. Destination ID 601 is an identifier that uniquely identifies each destination. Registered name 602 indicates a specific user name. Phone number 603 indicates the sender number (phone number) corresponding to registered name 602 when receiving a fax. Destination table name 607 indicates the destination table (address book) group to which the destination corresponding to registered name 602 belongs.
[0026] FIG. 7 is a diagram showing an example of a file storing the transfer setting information stored in the transfer setting information management unit 404 of the MFP 110 according to the first embodiment.
[0027] This file stores the items set on the file server setting screen in Fig. 9, the file naming rule setting screen in Fig. 10, and the folder naming rule setting screen in Fig. 11, which will be described later. These setting screens will be described in detail later. The format of this file can be CSV, XML, or other formats, and the format is not important.
[0028] The hostname 701 indicates the host name of the file server 120. In the figure, "sharedserver" is specified as the host name of the file server 120. The IP address of the file server 120 may be used as this host name. The folderpath 702 indicates the path that is the starting point of the storage destination folder of the transferred image file. In the figure, "root" is specified as the storage destination folder path. The username 703 indicates the login user name for authentication to the file server 120. In FIG. 7, "administrator" indicating the administrator is specified as the login user name. The password 704 indicates the password for authentication to the file server 120. In the figure, "32942xc45" is specified as the password. The password character string may be obfuscated using an encryption method such as hashing. The filerule 705 indicates the file naming rule when saving an image file in the file server 120. The folderrule 706 indicates the folder path naming rule when saving an image file in the file server 120. These will be described in detail later.
[0029] The transfer unit 402 creates a file name for an image file to be transmitted to the file server 120 based on the filenamerule 705, the registration name, telephone number, reception date and time, destination book name, line name, serial number, random number, etc. The transfer unit 402 also creates a folder name for an image file to be transmitted to the file server 120 and stored therein based on the foldernamerule 706, the registration name, telephone number, reception date and reception month. The transfer unit 402 then reads out an image file stored in the HDD 204, assigns the above-mentioned file name and folder name to the image file, and transmits it to the file server 120 specified by the hostname 701. The transfer unit 402 can also perform a test transmission, which will be described later, using the telephone number and reception date and time received from the UI unit 406, and a test fax document previously stored in the HDD 204, with the same processing content as the above-mentioned file transfer processing.
[0030] The temporary storage unit 403 receives the image file and the control file, and stores and manages them in the HDD 204. The transfer setting information management unit 404 stores and manages the transfer setting information, for example, shown in FIG. 7, set by the UI unit 406 described later, in the HDD 204. The transfer setting information management unit 404 also transmits the stored transfer setting information to the transfer unit 402 in response to a request from the transfer unit 402. The destination information management unit 405 stores and manages the destination information, for example, shown in FIG. 6, set by the UI unit 406 described later, in the HDD 204. The UI unit 406 displays various screens on the display unit of the operation unit 111 via the operation unit I / F 205, and detects the contents input by the user via the pointing device, hardware keys, or the like of the operation unit 111. The UI unit 406 also displays a status display screen, described later with reference to FIG. 8, on the operation unit 111, and receives a user input as to whether or not to perform transfer settings. The UI unit 406 also displays a file server setting screen, which will be described later with reference to FIG. 9, acquires the file server setting input by the user, transmits it to the transfer setting information management unit 404, and requests the file server setting to be saved. The UI unit 406 also displays a file naming rule setting screen, which will be described later with reference to FIG. 9, on the operation unit 111, acquires the file naming rule input by the user, transmits it to the transfer setting information management unit 404, and requests the file naming rule to be saved. The UI unit 406 also displays a folder naming rule setting screen, which will be described later with reference to FIG. 10, on the operation unit 111, acquires the folder naming rule input by the user, transmits it to the transfer setting information management unit 404, and requests the folder naming rule to be saved. The UI unit 406 also displays a test transmission screen, which will be described later with reference to FIG. 12, on the operation unit 111, acquires the sender's phone number and the reception date and time input by the user, transmits them to the transfer unit 402, and requests the test transmission.
[0031] 5 is a functional block diagram illustrating the configuration of software modules of the file server 120 according to embodiment 1. These software modules are stored in the HDD 306 of the file server 120, and are deployed in the RAM 302 at the time of execution and executed under the control of the CPU 301.
[0032] The communication unit 501 has a file transmission service such as SMB (Server Message Block) and WebDAV (Web-based Distributed Authoring and Versioning). The communication unit 501 accepts a request via the LAN 100, processes the request, and responds with the processing result. The authentication unit 502 authenticates the client (here, the MFP 110) based on authentication information included in the request for the file transmission service. The file management unit 503 manages files stored in the HDD 306 in response to the request for the file transmission service. The file management unit 503 saves image files in the HDD 306 and reads image files according to the folder name and file name received from the MFP 110 via the communication unit 501. The file management unit 503 also checks whether a folder with a folder name received from the MFP 110 via the communication unit 501 exists in the HDD 306. The file management unit 503 also creates a folder in the HDD 306 according to the folder name received from the MFP 110 via the communication unit 501.
[0033] Next, the filerule 705, which is a file naming rule for saving an image file in the file server 120, will be described with reference to FIG.
[0034] The naming rule is stored in the format of [item name 1] separator (here, "_") [item name 2] separator (here, "_") [item name 3]. For example, when adding a new item name, the separator "_" and the added item name are added to the existing naming rule. For example, if "item name 4" is further added in FIG. 7, the naming rule becomes [item name 1]_[item name 2]_[item name 3]_[item name 4]. The item name [REGISTNAME] corresponds to the registered name in FIG. 6, the item name [FAXNUMBER] corresponds to the telephone number in FIG. 6, and [DATE] indicates the date and time of reception. Although not shown, the item name [ADDRESSLISTNAME] indicates the destination list, and the item name [LINENAME] indicates the line name. The item name [SERIAL] indicates a serial number generated by the system, specifically, a number such as "00000001", and a different serial number is set each time. The item name [RANDOM] indicates a random number generated by the system, for example, "a761232ed4211cebacd00aa0057b223", and a different random number is set each time. In Figure 7, [REGISTNAME]_[FAXNUMBER]_[DATE] is specified as the file naming rule, and in this case, the file name will be "Registration name_(sender's) phone number_date".
[0035] Folderrule 706 indicates a naming rule for a folder path when saving an image file in the file server 120. The format of this naming rule is held in the format of [item name 1] path delimiter (here, " / ") [item name 2] path delimiter (here, " / ") [item name 3]. When adding a new item name, the path delimiter (" / ") and the added item name are added to the existing naming rule. For example, when item name 4 is added, the naming rule for the folder path is [item name 1] (path delimiter) / [item name 2] / [item name 3] / [item name 4]. The item name [REGISTNAME] indicates the registration name, the item name [FAXNUMBER] indicates the telephone number, and [DATE] indicates the reception date and time. In FIG. 7, [REGISTNAME] / [FAXNUMBER] / [DATE] are specified as the naming rule for the folder path, and "registration name / telephone number / date" is the folder path for the save destination.
[0036] FIG. 8 is a diagram showing an example of a status display screen displayed on the operation unit 111 of the MFP 110 according to the first embodiment.
[0037] 4 operating on the MFP 110 and the operating status of the MFP 110. When the UI unit 406 displays this status display screen, the UI unit 406 checks the operating status of the software modules of the MFP 110 and each part of the system. When the software modules and each part of the system of the MFP 110 are operating normally, the UI unit 406 displays a message indicating normal operation, and when an abnormality occurs, displays the software module or part thereof in which the abnormality occurs and its status. A To Setting Screen button 802 instructs transition to a screen for changing the transfer setting information managed by the transfer setting information management unit 404 of the MFP 110. When the user presses (instructs) the To Setting Screen button 802, a process of changing the transfer setting, which will be described later with reference to FIG. 13, is started, and transition is made to a file server setting change screen shown in FIG. 9.
[0038] It should be noted that a GUI button for updating the status display 801 in accordance with the latest software module status of the MFP 110 and the operating status of each unit of the MFP 110 may be provided on the status display screen shown in FIG.
[0039] In addition, in the first embodiment, when the setting screen button 802 is pressed, the screen transitions to the file server setting screen of FIG. 9. However, it is also possible to provide GUI buttons on this status display screen for directly transitioning to each of the screens of FIG. 10, FIG. 11, and FIG. 12 described below.
[0040] FIG. 9 is a diagram showing an example of a file server setting screen displayed by the MFP 110 according to the first embodiment.
[0041] The host name input box 901 is an input field for inputting the host name of the file server 120 to which the image file (fax document) is to be transferred. The name input in the host name input box 901 is transmitted by the UI unit 406 of the MFP 110 to the transfer setting information management unit 404, and is saved as the hostname 701 (FIG. 7) of the transfer setting information. The folder path input box 902 is an input field for inputting the folder name of the file server 120 to which the image file is to be transferred. The name input in this input box 902 is transmitted by the UI unit 406 of the MFP 110 to the transfer setting information management unit 404, and is saved as the folderpath 702 (FIG. 7) of the transfer setting information. The login user name input box 903 is an input field for inputting the login user name required for authentication in the file server 120 to which the image file is to be transferred. The name entered in this input box 903 is transmitted by the UI unit 406 of the MFP 110 to the transfer setting information management unit 404 and is stored as username 703 (FIG. 7) of the transfer setting information. The login password input box 904 is an input field for entering a login password required for authentication at the file server to which the image file is transferred. In this input box 904, the input characters are displayed as "*" to conceal the contents entered by the user. The display of the input characters is not limited to "*", and may be other symbols such as "●", or may be displayed without being concealed. The password entered in this input box 904 is transmitted by the UI unit 406 of the MFP 110 to the transfer setting information management unit 404 and is stored as password 704 (FIG. 7) of the transfer setting information. The cancel button 905 is a button for canceling the change of the transfer setting information on this screen. When the user presses the cancel button 905, the change of the transfer setting via this screen is canceled and the screen transitions to the status display screen of FIG. 8.
[0042] The Next button 906 is a button for changing the file server settings in the transfer setting information and instructing transition to the next screen, which is a file naming rule setting screen shown in Fig. 10 described later. When the user presses the Next button 906, the UI unit 406 of the MFP 110 transmits the file server settings input on this file server setting screen to the transfer setting management unit 404, and the transfer setting information management unit 404 saves this file server setting. The UI unit 406 then transitions to a file naming rule setting screen described later with reference to Fig. 10.
[0043] In this embodiment 1, when the Next button 906 is pressed, the screen transitions to the file naming rule setting screen of FIG. 10. However, this file server setting screen may be provided with GUI buttons for directly transitioning to each of the screens of FIG. 11 and FIG. 12.
[0044] 10 is a diagram showing an example of a setting screen for setting a file naming rule displayed by the MFP 110 according to embodiment 1. The file name of the image file to be transferred to the file server 120 is determined according to the file naming rule set by the user via this file naming rule setting screen.
[0045] Items 1002 to 1004 are areas for specifying the item names to be used in the file name among the item names of registration name, telephone number, reception date and time, destination book name, line name, serial number, and random number. Here, registration name, telephone number, and reception date and time are selected. Here, item 1002 indicates the first item name of the file name, item 1003 indicates the second item name of the file name, and item 1004 indicates the third item name of the file name. Here, a method for selecting the file name of each item is provided by a pull-down menu. The options of each pull-down are "None", "Registered name", "Fax number", "Date", "Destination book name", "Line name", "Serial number", and "Random number". Note that the "Line name" is obtained as the registration name 602 corresponding to the telephone number 603 shown in FIG. 6, for example, based on the facsimile number specified as the destination. Also, if "None" is selected, it indicates that the item names below the options are not generated. For example, if "Registered Name" is selected in the first item 1002 and "None" is selected in the second item 1003, it is determined that the file name after the second item has not been specified, and the file name will be just "Registered Name." Item 1005 is a pull-down menu for selecting the separator symbol that separates each item, with separator options including "hyphen," "underscore," and "space," and any one of these can be selected as the separator.
[0046] A preview display 1006 displays what kind of file name will be created according to the selection of items 1002 to 1004. The display content displays a file name according to the selection of items 1002 to 1004. In the example of FIG. 10, "Registered Name" is selected in the first item 1002, "Fax Number (Phone Number)" is selected in the second item 1003, "Date" is selected in the third item name 1003, and an underscore "_" is selected as a separator. Therefore, a preview of "[Registered Name]_[Fax Number]_[Date]" is displayed as a file name. A message 1001 is displayed when a predetermined condition that any of the received date and time (date), serial number, and random number is selected in items 1002 to 1004 is not satisfied. This is because a file name that can be uniquely specified cannot be determined unless any of the received date and time (date), serial number, and random number is selected. In the example of FIG. 10, a date is selected in item 1004, but if no date is selected, for example, a message "Please select the received date and time" is displayed as message 1001. In the above-mentioned predetermined condition, for example, the reception date and time includes time information down to the second. Furthermore, the above-mentioned predetermined condition may include other information than the above, as long as the information is necessary to uniquely identify the file name.
[0047] The cancel button 1007 instructs the user to cancel the contents input via this setting screen. When the user presses the cancel button 1007, the screen transitions to a status display screen, for example, as shown in FIG. 8. The back button 1008 instructs the user to return to the previous screen. When the user presses the back button 1008, the screen transitions to a file server setting screen, for example, as shown in FIG. 9. The next button 1009 instructs the user to proceed to the next screen. When the user presses the next button 1009, the screen transitions to a folder naming rule setting screen, for example, as shown in FIG. 11.
[0048] It should be noted that the next button 1009 can be pressed when any one of the date, serial number, and random number is selected in the items 1002 to 1004. If none of these items is selected, the next button 1009 is in an unselectable state and cannot be pressed. This makes it possible to prevent file names from being created according to naming rules that do not result in unique file names.
[0049] 11 is a diagram showing an example of a setting screen for setting a folder naming rule displayed by the MFP 110 according to embodiment 1. Folder names for files stored in the file server 120 are determined according to the folder naming rule set on this screen.
[0050] Radio button 1101 is a checkbox for selecting whether or not to save image files in separate hierarchical levels. If this button 1101 is checked, a folder name is created according to the naming rules set on this screen, and the image file is saved. If button 1101 is not checked, the image file is saved directly under the folder path specified on the file server setting screen shown in FIG.
[0051] Items 1102 to 1104 indicate hierarchical names. Here, a first hierarchy 1102, a second hierarchy 1103, and a third hierarchy 1104 of folders are included. A method for selecting a folder name corresponding to each hierarchy is provided by pull-down menus 1105 to 1108. Here, the options of the pull-down menu include "None", "Registered name", "Fax number", "Received date", "Received month", "Address book name", and "Line name". When "None" is selected, it indicates that the hierarchy below the option is not generated. For example, when "Registered name" is selected in the first hierarchy 1102 and "None" is selected in the second hierarchy 1103, it is determined that the folder name below the second hierarchy is not specified, and the folder name is only "Registered name". Preview display 1108 shows a preview display of the folder name according to the selection result of items 1102 to 1104. In the example of Figure 11, "Registered name" is selected in the first layer 1102, "Fax number" is selected in the second layer 1103, and "Date received" is selected in the third layer 1104, so the preview display 1108 shows "[Registered name] / [Fax number] / [Date received]."
[0052] The cancel button 1109 instructs the user to cancel the operation via this screen. When the user presses the cancel button 1109, the screen transitions to a status display screen as shown in FIG. 8, for example. The back button 1110 instructs the user to return to the previous screen. When the user presses the back button 1110, the screen transitions to a file naming rule setting screen as shown in FIG. 10, for example. The next button 1111 instructs the user to proceed to the next screen. When the user presses the next button 1111, the screen transitions to a test transmission screen as shown in FIG. 12, for example.
[0053] FIG. 12 is a diagram showing an example of a test transmission screen displayed by the MFP 110 according to the first embodiment.
[0054] The sender number input box 1201 is an input field for inputting information to be used as the sender's phone number when performing a test transmission. The phone number input in the sender number input box 1201 is transmitted to the transfer unit 402 by the UI unit 406 of the MFP 110 and used as the sender number (phone number) during the test transmission. The reception date and time input box 1202 is an input field for inputting the date and time to be used as the reception date and time when performing a test transmission. The date and time input in the reception date and time input box 1202 is transmitted to the transfer unit 402 by the UI unit 406 of the MFP 110 and used as the reception date and time during the test transmission.
[0055] 9, 10, and 11. When the user presses the setting confirmation button 1203, the UI unit 406 of the MFP 110 displays a setting confirmation screen for displaying the forwarding setting information input in FIG. 9, 10, and 11. The test transmission button 1204 is a button for instructing to perform a test transmission using the forwarding setting information input in FIG. 9, 10, and 11, and the information input in the sender number input box 1201 and the reception date and time input box 1202. When the user presses the test transmission button 1204, the UI unit 406 of the MFP 110 transmits the telephone number in the sender number input box 1201 and the date and time in the reception date and time input box 1202 to the transfer unit 402, and a test transmission request is sent to the transfer unit 402. When the test transmission button 1204 is pressed, the transfer unit 402 assumes that a fax document has been received with the received sender number and date and time, and performs a test transmission to the file server 120. When the test transmission is completed, the transfer unit 402 displays a test transmission result screen (not shown) for displaying the result of the test transmission.
[0056] Cancel button 1205 is a button for canceling the setting of the transfer setting information. When the user presses cancel button 1205, the screen transitions to the status display screen of FIG. 8. Back button 1206 is a button for transitioning to the previous screen. When the user presses back button 1206, the screen transitions to the previous screen, the folder naming rule setting screen of FIG. 11. OK button 1207 is a button for ending the setting of the transfer setting information and transitioning to the status display screen shown in FIG. 8. When the user presses OK button 1207, UI unit 406 of MFP 110 transitions to the status display screen shown in FIG. 8.
[0057] In the first embodiment, the sender number used during the test is input in a sender input box 1201, and the reception date and time is input in a reception date and time input box 1202. However, other input boxes or input buttons for designating a fax document to be used for the test transmission may also be provided.
[0058] 13 is a flowchart for explaining the setting of a file server, the setting of file naming rules, and the setting of folder naming rules by MFP 110 according to the first embodiment. Note that each operation (step) shown in this flowchart is realized by CPU 201 of MFP 110 expanding a control program stored in HDD 204 into RAM 203 and executing it. Also, this flowchart is executed when the user selects a control program for executing this flowchart via operation unit 111 of MFP 110.
[0059] First, in S1301, the CPU 201 displays a status display screen such as that shown in Fig. 8. Next, the process proceeds to S1302, where the CPU 201 determines whether or not the Go to Settings Screen button 802 has been pressed on this status display screen. If the Go to Settings Screen button 802 has been pressed, the process proceeds to S1303, where the CPU 201 displays a file server setting screen such as that shown in Fig. 9. The user then inputs the name of the file server to be the transfer destination, the folder path, authentication information, and the like via this file server setting screen.
[0060] Next, the process proceeds to S1304, where the CPU 201 determines whether the user has pressed the Cancel button 905 or the Next button 906 on this file server setting screen. If it is determined that the Next button 906 has been pressed, the process proceeds to S1305, and if it is determined that the Cancel button 905 has been pressed, the process returns to S1301. In S1305, the CPU 201 stores the file server setting information input via this file server setting screen in the HDD 204 of the MFP 110.
[0061] Next, the process proceeds to S1306, where the CPU 201 displays a file naming rule setting screen, for example, as shown in FIG. 10. The user then executes file naming rule setting processing, inputting file naming rule setting information via this setting screen. Next, the process proceeds to S1307, where the CPU 201 determines which button the user has pressed on this file naming rule setting screen. If it is determined in S1307 that the Next button 1009 has been pressed, the process proceeds to S1308, but as described above, there are cases where the Next button 1009 cannot be pressed. This file naming rule setting processing will be described later with reference to FIG. 18. On the other hand, if it is determined that the Cancel button 1007 has been pressed, the process proceeds to S1301, and if it is determined that the Back button 1008 has been pressed, the process proceeds to S1303.
[0062] FIG. 18 is a flowchart for explaining the file naming rule setting process in S1306 of FIG.
[0063] First, in S1801, CPU 201 acquires information selected from items 1002 to 1004 on a file naming rule setting screen shown in FIG. 10, for example. Next, the process proceeds to S1802, where CPU 201 determines whether or not an item that allows a unique file name to be set has been selected based on the information acquired in S1801. As described above, the items that allow a unique file name are "date," "serial number," and "random number," and the process determines whether or not one or more of these items are included. If one or more unique items are included, the process determines that an item that allows a unique file name to be set has been selected, and proceeds to S1805. In S1805, CPU 201 stores the file naming rule determined on this screen in HDD 204.
[0064] On the other hand, if CPU 201 determines in S1802 that the file name does not include an item that will make the file name unique, the process proceeds to S1803. In S1803, CPU 201 displays a warning message prompting the user to select an item that will make the file name unique in message 1001 in Fig. 10. In Fig. 10, "Please select the date and time of receipt" is displayed as message 1001, but a message prompting the user to select another item that will make the file name unique may also be displayed.
[0065] Next, the process proceeds to S1804, and the CPU 201 prevents the user from pressing the Next button 1009. Specifically, the Next button 1009 is grayed out to make it invalid (the button cannot be pressed), and transition to the next screen is not possible. This prevents a non-unique file name from being given to an image file. In this way, when a unique file name is specified on the file naming rule setting screen, the Next button 1009 becomes pressable, and when the user presses the Next button 1009, the file naming rule is finalized and the process proceeds to S1308.
[0066] In S1308, the CPU 201 displays a folder naming rule setting screen, for example, as shown in FIG. 11. Then, in S1309, the user executes a folder naming rule setting process to input setting information for the folder naming rule via this setting screen. Then, the process proceeds to S1310, and the CPU 201 determines which button the user has pressed on this folder naming rule setting screen. If it is determined in S1310 that the user has pressed the Next button 1111, the process proceeds to S1311. Here, if the user has pressed the Cancel button 1109, the process proceeds to S1301, and if the user has pressed the Back button 1110, the process proceeds to S1306. In S1311, the CPU 201 stores, for example, the information input by the user on the folder naming rule setting screen in the HDD 204.
[0067] Next, the process proceeds to S1312, where the CPU 201 displays a test transmission screen shown in, for example, FIG. 12. The process proceeds to S1313, where the CPU 201 determines which button the user has pressed on this test transmission screen. If the user has not pressed any button, the process executes S1312. If the CPU 201 determines that the user has pressed the OK button 1207, the process ends. On the other hand, if the CPU 201 determines that the user has pressed the cancel button 1205, the process proceeds to S1301. If the CPU 201 determines that the user has pressed the back button 1206, the process proceeds to S1309. If the CPU 201 determines that the user has pressed the test transmission button 1204, the process proceeds to S1314. In S1314, the CPU 201 performs a transmission test based on the contents set on the file server setting screen (FIG. 9), the file naming rule setting screen (FIG. 10), the folder naming rule setting screen (FIG. 11), and the test transmission screen (FIG. 12), and proceeds to S1312.
[0068] Next, a fax reception process by MFP 110 according to this embodiment will be described. The following mainly describes the process in which MFP 110 receives a fax document and transfers the fax document as an image file. Here, the received fax document is transferred to file server 120 as an image file using the above-mentioned transfer setting information (FIG. 7) and destination information (FIG. 6). At this time, a file name and folder name for the fax document (image file) are created and transferred to file server 120. Note that the destination information has been registered in advance by the user in destination information management unit 405 via operation unit 111 of MFP 110 as shown in FIG. 6. Here, a description of the process of registering the destination information will be omitted.
[0069] FIG. 14 is a sequence diagram for explaining a process in which the MFP 110 according to the first embodiment receives image data (document data) by fax and transfers an image file of the received image data to the file server 120. In FIG.
[0070] In step 1401, a fax image is sent from an external fax terminal to the MFP 110. When the MFP 110 receives this fax image, the fax receiving unit 401 and the transfer unit 402 perform fax reception processing.
[0071] 15 is a flowchart for explaining fax reception processing by the MFP 110 according to the first embodiment. Note that each operation shown in this flowchart is realized by the CPU 201 of the MFP 110 loading a control program stored in the HDD 204 into the RAM 203 and executing it.
[0072] First, in S1501, CPU 201 receives a fax from an external fax terminal via public line 150 using modem 210. CPU 201 also uses modem 210 to acquire the telephone number of the external fax terminal as the sender number, and further acquires the date and time of fax reception as the reception date and time. Next, the process proceeds to S1502, where CPU 201 converts the fax document received in S1501 into an image file such as PDF. CPU 201 also creates a control file that describes the sender telephone number and reception date and time acquired in S1501. Then, the image file including the fax document is temporarily stored in HDD 204 together with the control file.
[0073] Next, the process proceeds to S1503, where the CPU 201 determines whether the image file has been successfully temporarily stored in the HDD 204. If the image file has been successfully stored, the process proceeds to S1504, where the CPU 201 acquires the sender's telephone number and the date and time of reception, etc., that have been temporarily stored in the HDD 204. On the other hand, if the image file has not been temporarily stored, error processing is performed and the process ends. An example of a temporary storage failure here is a lack of capacity in the HDD 204. The error processing here may include sending the fax document to the printer unit 113 via the printer I / F 209 to have it printed, and displaying a status display screen (FIG. 8) on the operation unit 111 to display the error status, etc.
[0074] Next, the process proceeds to S1505, and the CPU 201 refers to the sender number and reception date and time acquired in S1504, the transfer setting information (FIG. 7), and the destination information (FIG. 6) to create a file name for the image file when it is transferred to the file server 120. Details of the process of S1505 will be described with reference to the flowchart in FIG.
[0075] Fig. 16 is a flowchart for explaining the process of creating a file name for an image file to be transferred in S1505 in Fig. 15. Note that each operation shown in this flowchart is realized by CPU 201 of MFP 110 expanding a control program stored in HDD 204 into RAM 203 and executing it, so here, the main subject of the operations will be explained as CPU 201.
[0076] First, in S1601, the CPU 201 acquires the filenamerule 705 (file naming rule) stored in the HDD 204. Next, the process proceeds to S1602, where the CPU 201 acquires destination information (FIG. 6) based on the telephone number. Here, the registered name 602 is searched for and acquired using the telephone number 603 as a key. Next, the process proceeds to S1603, where the CPU 201 determines whether or not the registered name 602 corresponding to the telephone number 603 exists. If the registered name 602 exists, the process proceeds to S1604, where the corresponding registered name is acquired, and the process proceeds to S1606. On the other hand, if the registered name 602 does not exist, the process proceeds to S1605, where the CPU 201 acquires a default registered name that is set in advance, and the process proceeds to S1606. Note that, as an example of the default registered name, it is assumed that "not applicable" or the like is set. Also, this default registered name may be stored in the ROM 202 or the HDD 204 in advance. Also, an input box for setting the default registered name may be provided on, for example, the file naming rule setting screen of FIG. 10, so that the user can change the default name. In step S1606, the CPU 201 creates a file name using the registered name, the sender's telephone number, the reception date and time, the destination book name, the line name, and the like, in accordance with the file naming rules acquired in step S1601.
[0077] Then, the process proceeds to S1506 in Fig. 15. In S1506, the CPU 201 creates a folder name for the transfer based on the sender's telephone number and the reception date and time acquired in S1504, the transfer setting information (Fig. 7), and the destination information (Fig. 6). Details of the process in S1506 will be described with reference to the flowchart in Fig. 17.
[0078] Fig. 17 is a flowchart for explaining the process of creating a folder name of file server 120 in which an image file to be transferred is stored, in S1506 of Fig. 15. Note that each operation shown in this flowchart is realized by CPU 201 of MFP 110 expanding a control program stored in HDD 204 into RAM 203 and executing it, and therefore, the operation will be explained here as being performed by CPU 201.
[0079] First, in S1701, the CPU 201 acquires the foldernamerule 706 stored in the HDD 204. Next, the process proceeds to S1702, where the CPU 201 acquires destination information and searches for and acquires the corresponding registered name using the telephone number acquired in S1504 as a key. Then, the process proceeds to S1703, where the CPU 201 determines whether or not a registered name corresponding to the telephone number exists. If it is determined that a registered name exists, the process proceeds to S1704, where the CPU 201 acquires the corresponding registered name, and proceeds to S1706. On the other hand, if it is determined in S1703 that a registered name corresponding to the telephone number does not exist, the process proceeds to S1705, where the CPU 201 acquires a default registered name that is set in advance, and proceeds to S1706. Note that, as an example of the default registered name, it is assumed that "not applicable" or the like is set. Also, this default registered name may be stored in the ROM 202 or the HDD 204 in advance. Also, an input box for setting a default registered name may be provided on the folder naming rule setting screen of FIG. 11, for example, so that the default name saved in the HDD 204 or the like can be changed by user input.
[0080] In S1706, the CPU 201 creates a folder name using the registered name, the sender's telephone number, the received date and time, etc., in accordance with the foldernamerule 706 acquired in S1701. Then, the process proceeds to S1707, where the CPU 201 sets the folder path 703 at the beginning of the folder name, and ends this process.
[0081] 14, in 1402, the MFP 110 performs authentication processing with the file server 120. This authentication processing is executed from S1507 in FIG.
[0082] 15, the CPU 201 reads the transfer setting information (FIG. 7) from the HDD 204 and acquires the hostname 701, username 703, and password 704. The CPU 201 then accesses the address specified by the hostname 701 and transmits the username 703 and password 704 as the user name and password, respectively, together with an authentication request to the file server 120. Then, the process proceeds to S1508.
[0083] 14 will be described again. In 1402, when the communication unit 501 of the file server 120 receives an authentication request from the MFP 110, it acquires a user name and password from the authentication request and transmits them to the authentication unit 502. The authentication unit 502 uses the authentication information stored in the HDD 306 to compare the user ID and password, and transmits the authentication result to the communication unit 501. In response, the communication unit 501 transmits the received authentication result to the MFP 110.
[0084] 15, CPU 201 determines whether or not an authentication result has been received from file server 120. If it determines that an authentication result has not been received, then S1508 is executed, and if an authentication result has been received, then the process proceeds to S1509, where CPU 201 determines whether or not the authentication result received in S1508 indicates successful authentication. If CPU 201 determines that authentication has been successful, then the process proceeds to S1510, but if not, then error processing is performed and the process ends. Examples of error processing here include displaying a status display screen (FIG. 8) on operation unit 111 to display the error status, and so on.
[0085] 14, in the case where the MFP 110 has been successfully authenticated, the MFP 110 queries the file server 120 as to whether or not a folder with the name of the folder created in S1506 exists, and if not, requests the creation of the folder. At this time, the MFP 110 executes the process of S1510 in FIG.
[0086] In step S1510, the CPU 201 transmits the name of the folder created in step S1506 to the file server 120, and transmits a request to confirm the existence of a file with that folder name.
[0087] 14, when the communication unit 501 of the file server 120 receives a folder existence confirmation request from the MFP 110, it transmits the folder name included in the folder existence confirmation request to the file management unit 503 and requests the folder existence confirmation process. In response, the file management unit 503 determines whether or not a folder with the received folder name exists in the HDD 306, and transmits the confirmation result to the communication unit 501 as the folder existence confirmation result. In response, the communication unit 501 transmits the folder existence confirmation result to the MFP 110. Then, the process proceeds to S1511 in FIG. 15.
[0088] In S1511, CPU 201 determines whether a folder existence confirmation result has been received from file server 120. If it is determined that a folder existence confirmation has not been received, processing proceeds to S1511 again. If it is determined in S1511 that a folder existence confirmation has been received, processing proceeds to S1512. In S1512, CPU 201 determines from the folder existence confirmation received in S1511 whether a folder with the folder name created in S1506 exists in file server 120. If it is determined here that a folder with the same name exists, processing proceeds to S1515, but if it is determined that a folder with the same name does not exist, processing proceeds to S1513.
[0089] In step S1513, the CPU 201 transmits the name of the folder created in step S1506 to the file server 120, and requests the file server 120 to create the folder.
[0090] 14 , in 1403, when the communication unit 501 of the file server 120 receives a folder creation request from the MFP 110, it transmits the folder name included in the folder creation request to the file management unit 503 and requests the creation of a folder with the folder name. The file management unit 503 creates a folder with the received folder name in the HDD 306 and transmits a response to the created folder to the communication unit 501. When the communication unit 501 receives the folder creation response, it transmits the folder creation response to the MFP 110.
[0091] In S1514, the CPU 201 determines whether or not a folder creation response has been received from the file server 120. If a folder creation response has not been received, the process executes S1514, and if a folder creation response has been received, the process proceeds to S1515. In S1515, the CPU 201 reads out the fax document stored in the HDD 204, and transmits it to the file server 120 together with the file name created in S1505 and the folder name created in S1506, and transmits a file save request.
[0092] This corresponds to 1404 in Fig. 14. In 1404, the MFP 110 transmits a fax document (image file) to the file server 120 by specifying the file name created in S1505 and the folder name created in S1506. When the communication unit 501 of the file server 120 receives this file save request in this way, it acquires the file, folder name, and file name from the file save request. The communication unit 501 then transmits the acquired file, folder name, and file name to the file management unit 503, requesting storage under the specified folder name and file name. The file management unit 503 stores the received file in the location of the specified folder name and file name in the HDD 306, and transmits a storage response to the communication unit 501. The communication unit 501 transmits the storage response to the MFP 110 as a file transmission response.
[0093] 15, CPU 201 determines whether a file transmission response has been received from file server 120. If a file transmission response has not been received, the process proceeds to S1516 again, but if a file transmission response has been received, this process ends.
[0094] By the above-described process, when the MFP 110 receives a fax, it creates a file name for the received image file (fax document) according to the file naming rules of the transfer setting information, the sender number, the reception date and time, the registered name of the destination information corresponding to the sender number, etc. The MFP 110 also creates a folder name according to the folder path and folder naming rules of the transfer setting information, the sender number, the reception date and time, the registered name of the destination information corresponding to the sender number, etc. The MFP 110 also checks the file server 120 for the existence of the created folder, and if the same folder does not exist in the file server 120, it requests the creation of the folder and stores the image file in the location of the created folder name and file name.
[0095] As described above, according to the first embodiment, by setting the file naming rule and the folder naming rule in advance, a desired file name can be given to an image file received by fax and stored in a desired folder in a file server. In addition, the file naming rule and the folder naming rule can search for destination information from the telephone number of the sender of the received fax and obtain and use a registered name corresponding to the destination information. In addition, in the file naming rule, a separator can be set as a separator between each item. Furthermore, in the file naming rule, an item can be selected so that the file name is unique in a format that the user can recognize. This can improve the work efficiency while increasing the flexibility of file name setting for the user.
[0096] In addition, since the desired folder can be created in the file server for storing the image file, the user can save the image file therein, which has the effect of reducing the time and effort required for searching for the desired image file.
[0097] [Embodiment 2] Next, a second embodiment of the present invention will be described. In the second embodiment, an example of file name setting process control different from that of the first embodiment will be described. In the second embodiment, the naming rule is saved without executing the item check process (S1802) of the file naming rule setting process in FIG.
[0098] 19 is a diagram showing an example of a confirmation dialog displayed on the MFP 110 according to the second embodiment of the present invention. Note that the configurations and system configurations of the MFP 110 and the file server 120 according to the second embodiment are the same as those of the first embodiment described above, and therefore a description thereof will be omitted.
[0099] Message 1901 indicates a message to be displayed in this confirmation dialog. Yes button 1902 is pressed when the user agrees with the contents displayed in this confirmation dialog. When the user presses the Yes button, the screen transitions to, for example, the folder naming rule setting screen shown in FIG. 11 described above. No button 1903 is instructed when the user does not agree with the contents displayed in this confirmation dialog. When the user presses the No button 1903, the screen transitions to, for example, the file naming rule setting screen shown in FIG. 10.
[0100] 20 is a flowchart for explaining a process for displaying a confirmation dialog by MFP 110 according to embodiment 2. Note that each operation shown in this flowchart is realized by CPU 201 of MFP 110 expanding a control program stored in HDD 204 into RAM 203 and executing it, and therefore the main subject of the operation will be explained here as CPU 201. The process shown in this flowchart is implemented when the folder naming rule setting screen is displayed in S1309 in FIG.
[0101] First, in S2001, the CPU 201 acquires the information of the filenamerule 705 stored in the transfer setting information (FIG. 7). Next, the process proceeds to S2002, where the CPU 201 determines whether the display conditions of the confirmation dialog are met based on the naming rule acquired in S2001. Details of the display conditions of the confirmation dialog will now be described using the transfer setting information.
[0102] Fig. 21 is a diagram showing an example of forwarding setting information according to embodiment 2. In Fig. 21, 2101 to 2106 are the same as the forwarding setting information 701 to 706 in Fig. 7 according to the above-mentioned embodiment 1, and therefore a description thereof will be omitted.
[0103] Dialogrule 2107 indicates conditions for displaying the confirmation dialog. This condition is specified by displaying a display setting screen (not shown) for the confirmation dialog via UI unit 406, or by using a Web browser to specify the condition via a display setting screen (not shown) for the confirmation dialog. In dialogrule 2107, the following can be specified: "Registered name", "Fax number", "Date", "Address book name", "Line name", "Serial number", "Random number", etc. In FIG. 21, [REGISTNAME] (registered name) and [FAXNUMBER] (fax number) are specified, and if these are not included in filenamerule 2105, the above conditions are met and the confirmation dialog is displayed.
[0104] If the CPU 201 determines in S2002 of Fig. 20 that the display conditions for the confirmation dialog are met, the process proceeds to S2003, where a confirmation dialog such as that shown in Fig. 19 is displayed, and the process ends. On the other hand, if the CPU 201 determines in S2002 that the display conditions are not met, the process ends without displaying such a confirmation dialog.
[0105] As described above, according to the second embodiment, by specifying any condition, it is possible to impose restrictions on subsequent processing (in the second embodiment, a confirmation dialog is displayed). Therefore, by setting conditions to be confirmed by the user according to a linked system or device, for example, it becomes possible to execute processing according to the system or device, thereby improving user convenience.
[0106] [Embodiment 3] In the above-mentioned first embodiment, the folder naming rule is set via a setting screen for folder naming rule as shown in Fig. 11. In this third embodiment, an example will be described in which the folder naming rule is set via a setting screen different from that of the above-mentioned first embodiment. Note that the configurations and system configurations of the MFP 110 and the file server 120 according to the third embodiment are the same as those of the above-mentioned first embodiment, and therefore the description thereof will be omitted.
[0107] Fig. 22 is a diagram showing an example of a setting screen for folder naming rules displayed on MFP 110 according to the third embodiment of the present invention. This screen is displayed as a setting screen for folder naming rules to be displayed on operation unit 111 in S1306 of Fig. 13, and a folder name to be used when transferring to file server 120 is determined according to the folder naming rule set on this screen.
[0108] 22, 2201 to 2203 show options for folder naming rules, and one checked naming rule is applied as the folder naming rule. When naming rule 2201 is selected, a folder name consisting of "Registration name / Fax number / Date" is generated. When naming rule 2202 is selected, a folder name consisting of "Date / Registration name / Fax number" is generated. When naming rule 2203 is selected, a folder name consisting of "Fax number / Registration name / Date" is generated.
[0109] Cancel button 2204 indicates that processing via this screen should be cancelled. When the user presses cancel button 2204, the screen transitions to, for example, the status display screen of Fig. 8. Back button 2205 instructs the user to return to the previous screen. When the user presses back button 2205, the screen transitions to, for example, a file naming rule setting screen shown in Fig. 10. Next button 2206 indicates that the user can proceed to the next screen. When the user presses next button 2206, the screen transitions to, for example, a test transmission screen shown in Fig. 12.
[0110] In the transfer setting process shown in the flowchart of Fig. 13 described above, the folder naming rule setting screen shown in Fig. 19 is used instead of the folder naming rule setting screen of Fig. 11 in the first embodiment. Then, in S1309, the folder naming rule setting screen shown in Fig. 22 is displayed. Then, in S1310, it is determined which button the user has pressed on this folder naming rule setting screen. If the user has pressed the Next button 2206, the process proceeds to S1311. If the user has pressed the Cancel button 2204, the process proceeds to S1301. Also, if the user has pressed the Back button 2205, the process proceeds to S1306. In S1311, the CPU 201 stores the information input on the folder naming rule setting screen of Fig. 22 in the HDD 204.
[0111] As described above, according to the third embodiment, the same effects as those of the first embodiment can be obtained. In addition, when setting a folder name, the user can select and set a desired naming rule from among predetermined folder naming rules, which has the effect of simplifying the user's operation. This makes it easy to set a folder for storing received fax documents.
[0112] [Other embodiments] In the first embodiment, the registration name, telephone number, and date can be specified as the folder name, but for example, if two fax lines are connected to the modem 210 of the MFP 110, the line number may be specified as the folder name.
[0113] In the above first to third embodiments, the setting screen is in a wizard format and multiple screens are used to perform the settings, but it is also possible to configure all the settings on a single screen.
[0114] In the above first to third embodiments, the user controls operation unit 111 of MFP 110 to display and operate a setting screen on operation unit 111, but the setting screen may be operated from a web browser of a general-purpose personal computer.
[0115] (Other embodiments) The present invention can also be realized by executing the following process: That is, software (programs) that realize the functions of the above-described embodiments are 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 programs.
[0116] The present invention is not limited to the above-described embodiments, and various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, the following claims are appended to apprise the public of the scope of the present invention. [Explanation of symbols]
[0117] 110: MFP, 111: operation unit, 120: file server, 201, 301: CPU, 204, 306: HDD, 402: transfer unit, 403: temporary storage unit, 404: transfer setting information management unit, 405: destination information management unit.
Claims
1. An information processing device having a provision means for providing information on a setting screen related to the creation of a file name, on said setting screen, it is possible to select one or more items from a plurality of items that can be used for creating a file name, and a message is displayed prompting the user to select an item that will make the created file name unique, An information processing device characterized in that the information processing device has a storage means capable of accepting settings from a user specifying a folder within the information processing device in which to save the created file with the file name, and which saves the file with the file name in the folder specified by the settings accepted from the user.
2. The information processing device according to claim 1, characterized in that the setting for identifying the folder includes a setting for identifying the name of the folder.
3. An information processing device having a provision means for providing information on a setting screen related to the creation of a file name, on said setting screen, it is possible to select one or more items from a plurality of items that can be used for creating a file name, and a message is displayed prompting the user to select an item that will make the created file name a unique file name, An information processing device characterized in that it has a storage means capable of accepting settings from a user regarding the path of a folder within the information processing device in which the created file with the file name is saved, and which saves the file with the file name in the folder of the set path.
4. An information processing device as described in any one of claims 1 to 3, characterized in that the items that make the created file name a unique file name include items related to date and time.
5. An information processing device as described in any one of claims 1 to 4, characterized in that the data contained in the file to which the file name is assigned includes data created by a scanner function.
6. An information processing device as described in any one of claims 1 to 4, characterized in that the data contained in the file to which the file name is assigned includes data obtained by fax reception.
7. An information processing device as described in any one of claims 1 to 6, characterized in that the item having the file name as a unique file name includes multiple items.
8. The information processing device according to any one of claims 1 to 7, characterized in that the information processing device is a device equipped with a scanner function.
9. The information processing device according to any one of claims 1 to 8, characterized in that the information processing device is a device having a fax receiving function.
10. An information processing device as described in any one of claims 1 to 9, characterized in that the data contained in the file to which the file name is assigned includes data converted into PDF.
11. An information processing device as described in claim 1 or 2, characterized in that in the setting for identifying the folder, the user can include any character string in the name of the folder.
12. The information processing device according to claim 3, characterized in that the settings relating to the path of the folder allow the user to include any character string in the path of the folder.
13. An information processing device as described in claim 1 or 2, characterized in that in the setting for identifying the folder, it is possible to include a date in the name of the folder.
14. An information processing device as described in claim 3, characterized in that the settings regarding the folder path make it possible to include a date in the folder path.
15. A computer comprising: Execute a procedure to provide a setting screen for creating a file name; A program in which it is possible to select one or more items from a plurality of items that can be used to create a file name on the setting screen, and a message is displayed prompting the user to select an item that will make the created file name unique, The computer is capable of accepting a setting from a user to specify a folder in the computer in which the created file having the file name is to be saved; The program is characterized in that it causes the computer to execute a storage procedure for saving the created file with the file name in a folder specified by the settings received from the user.
16. The program of claim 15, wherein the settings for identifying the folder include settings for identifying the name of the folder.
17. A computer comprising: A program that allows a user to select one or more items from a plurality of items that can be used to create a file name on a setting screen, and displays a message prompting the user to select an item that will make the created file name unique, The computer is capable of accepting, from a user, a setting regarding a path of a folder in the computer in which the created file having the file name is to be saved; The program further causes the computer to execute a storage procedure for saving the created file given the file name in a folder of the set path.
18. A program as described in any one of claims 15 to 17, characterized in that the items that make the file name a unique file name include items related to date and time.
19. A program as described in any one of claims 15 to 18, characterized in that the data contained in the file to which the file name is assigned includes data created by a scanner function.
20. A program as described in any one of claims 15 to 18, characterized in that the data contained in the file to which the file name is assigned includes data obtained by fax reception.
21. A program as described in any one of claims 15 to 20, characterized in that the item that makes the file name a unique file name includes multiple items.
22. The program described in any one of claims 15 to 21, characterized in that the information processing device having the computer is a device equipped with a scanner function.
23. The program described in any one of claims 15 to 22, characterized in that the information processing device having the computer is a device having a fax receiving function.
24. A program as described in any one of claims 15 to 23, characterized in that the data contained in the file to which the file name is assigned includes data converted into PDF.
25. The program according to claim 15 or 16, characterized in that the setting for identifying the folder allows the user to include any character string in the name of the folder.
26. The program according to claim 17, characterized in that the settings relating to the folder path allow the user to include any character string in the folder path.
27. The program according to claim 15 or 16, characterized in that in the setting for identifying the folder, it is possible to include a date in the name of the folder.
28. The program according to claim 17, characterized in that the settings relating to the path of the folder make it possible to include a date in the path of the folder.
29. A control method for controlling an information processing device having a providing means for providing information on a setting screen related to file name creation, comprising: displaying, on the setting screen, a message that allows the user to select one or more items from a plurality of items that can be used to create a file name, and prompts the user to select an item that will make the created file name unique; receiving, from a user, a setting for specifying a folder in the information processing device in which the created file having the file name is to be saved; saving the file with the file name in a folder specified by the setting received from the user; A control method comprising the steps of:
30. A control method for controlling an information processing device having a providing means for providing information on a setting screen related to file name creation, comprising: displaying, on the setting screen, a message that allows the user to select one or more items from a plurality of items that can be used to create a file name, and prompts the user to select an item that will make the created file name unique; receiving, from a user, a setting regarding a path of a folder in the information processing device in which the created file having the file name is to be saved; saving the file with the file name in the folder of the set path; A control method comprising the steps of: