JP2017151915A - Information processor, data transfer system, control method for data transfer system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress occurrence of mismatching when transferring setting information of an application.SOLUTION: A client PC 101 as an information processor comprises: reception means for receiving selection of setting as an export object of a document management application 300 which performs export processing; acquisition means for acquiring related setting related to the received setting of the export object; addition means for adding the acquired related setting to the export object; and export means for performing the export processing of the setting of the export object. The acquisition means acquires the related setting when the setting as the export object received by the reception means is a part of setting of the application.SELECTED DRAWING: Figure 12

Description

  The present invention relates to an information processing apparatus, a data migration system, a data migration system control method, and a program.

  When there are many application setting items or when a common setting change according to work is required, it is complicated for each user to set the application. Therefore, there is a technology for transferring the setting information by exporting the setting information of the application and importing the setting information to the transfer destination in order to simplify the setting work at the time of introducing the application. Patent Document 1 changes environment-dependent information included in application setting information according to a migration destination by changing or deleting setting information including folder path information that varies depending on an OS (Operating System) according to the migration destination. The technology is disclosed.

Japanese Patent Laying-Open No. 2015-45971

  However, Patent Document 1 is intended for a case where all application settings are migrated. When migrating only some function settings, inconsistencies caused by dependency between settings are not taken into account, and when only some setting information of the application is migrated, the application may not operate normally Can be considered.

  An object of the present invention is to provide an information processing apparatus that suppresses inconsistencies that occur when application setting information is migrated.

  In order to solve the above-described problem, an information processing apparatus according to an aspect of the present invention includes a reception unit that receives selection of a setting that is an export target of an application that performs export processing, and a relationship related to the received setting of the export target. An acquisition unit configured to acquire a setting; an adding unit configured to add the acquired related setting to the export target; and an export unit configured to perform an export process of the setting of the export target. The acquisition unit acquires the related setting when the setting to be exported received by the receiving unit is a part of the application setting.

  ADVANTAGE OF THE INVENTION According to this invention, the information processing apparatus which suppresses generation | occurrence | production of inconsistency when migrating the setting information of an application can be provided.

It is a figure which shows an example of a system configuration. It is a figure which shows an example of the hardware constitutions of information processing apparatus. FIG. 3 is a diagram illustrating an example of a software configuration of a document management application. It is a figure which shows an example of UI of the main screen of a document management application. It is a figure which shows an example of the data structure of a setting file. It is a figure which shows an example of the data structure of a setting file. It is a figure which shows an example of the data structure of a setting file. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. It is a flowchart which shows an example of the export process of setting information. It is a flowchart which shows an example of the import process of setting information. It is a figure which shows an example of the related setting table of setting information. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. It is a flowchart which shows an example of the import process of setting information. It is a flowchart which shows an example of the import process of setting information. FIG. 10 is a diagram illustrating an example of a UI of a setting transition screen of a document management application. It is a flowchart which shows an example of the confirmation process of a related setting. It is a figure which shows an example of a software structure of client PC. It is a flowchart which shows an example of the import process of setting information. It is a flowchart which shows an example of the import process of setting information.

(First embodiment)
First, a first embodiment of the present invention will be described. FIG. 1 is an overall view of an information processing system (data migration system). On the LAN 100, a client PC 101, a client PC 110, a file server 102, and an MFP 103 are connected so as to communicate with each other. LAN is an abbreviation for Local Area Network, PC is an abbreviation for Personal Computer, and MFP is an abbreviation for Multifunction Peripheral.

  The client PC 101 and the client PC 110 are an example of an information processing apparatus. A predetermined OS is installed and various applications that execute specific function processing are also installed. Here, the specific function processing includes, for example, document processing, spreadsheet processing, presentation processing, image processing, graphic processing, and the like, and each application has a unique data structure (file structure). The client PC 101 and the client PC 110 are installed with a document management application 300 for performing document management and printing. In the present embodiment, an example in which setting information of the document management application 300 installed on the client PC 101 is exported and imported to another client PC 110 is shown. Hereinafter, the client PC 101 and the client PC 110 may be collectively referred to as a client PC.

The file server 102 is an example of an external server, and the client PCs 101 and 104 can browse and operate files and folders stored in the file server 102.
The MFP 103 is an example of an image processing apparatus, and includes a printer function, a FAX function, a copy function, a scanner function, a file transmission function, and the like, and executes printing and fax transmission according to instructions from the client PCs 101 and 104. Note that the file server 102 and the MFP 103 are added to the configuration for explaining the functions of the document management application 300 in the present embodiment, but are not essential in the system configuration.

FIG. 2 is a hardware configuration diagram of the client PC 101 and the client PC 110. The client PC includes a CPU 201, a display 202, a RAM 203, a ROM 204, an input device 205, an external memory 206, and an I / O 207.
The CPU 201 implements various processes by executing a program. An external memory 206 such as a RAM 203, ROM 204, HDD (Hard Disk Drive) or FDD (Floppy (registered trademark) disk drive) is a storage device for storing various programs and execution information. The processing described in the present embodiment is realized by loading a program stored in the ROM 204 or the external memory 206 into the RAM 203 and executing it by the CPU 201.
The display 202 is a display unit that gives visual output information feedback to the user. The input device 205 is an input unit that receives user operation inputs such as a keyboard and a pointing device. The interface device I / O 207 communicates with an external device. The client PC communicates with the file server 102 and the MFP 103 via the interface device I / O 207.

  FIG. 3 is a diagram illustrating an example of a software configuration of the document management application 300 executed on the client PC. The document management application 300 is installed in the client PC 101, and the program is stored in the ROM 204 or the external memory 206 of the client PC 101. That is, the CPU 201 loads the program into the RAM 203 and executes it, thereby realizing the functions of the document management application 300 and the processing related to the flowcharts described later.

The document management application 300 includes an input management unit 301, a screen display management unit 302, an output control unit 304, an application information management unit 303, a setting transition unit 305, and a management unit 306.
The input management unit 301 detects the operation of the input device 205 by the user via the GUI (Graphical User Interface) of the document management application 300 displayed by the screen display management unit 302, and acquires user operation information. The input management unit 301 detects an input operation by the user by monitoring a mouse or keyboard operation event processed by the OS in addition to the operation on the GUI displayed by the screen display management unit 302.
The screen display management unit 302 executes processing related to screen display control such as GUI display of the document management application 300 and accepting user operations on the GUI.
The application information management unit 303 manages application settings and states while the document management application 300 is running. The application information management unit 303 further performs a process of reading and writing application settings and states to and from the setting file in the external memory 206. An example of a specific setting file will be described later.

The output control unit 304 executes various output processes according to user operations received via the screen display management unit 302. For example, in response to receiving a print or fax instruction, an image is transmitted to the MFP 103 via a printer driver or fax driver. Further, the output control unit 304 converts a stamp attached to a document stored in the local drive or the file server 102 and converts the file format of the document in accordance with an instruction from the management unit 306 and saves the document.
The setting migration unit 305 executes export processing and import processing for migrating application settings.
A management unit 306 controls the document management application 300 to give instructions and management to the above-described units.

FIG. 4 is a diagram illustrating an example of a UI screen of the document management application 300.
The main screen 400 includes, for example, a ribbon 410, a quick access toolbar 420, an address bar 430, a library pane 440, a file list pane 450, a preview pane 460, and an output bar 470 as main UI components.
The ribbon 410 is composed of a plurality of tabs classified for each application, and buttons having functions suitable for the application can be arranged on the tabs. This allows quick access to user-desired functions. One tab can be composed of a plurality of groups, and a plurality of buttons can be arranged in one group. There are tabs and groups that are prepared in advance as application defaults, and in addition, tabs and groups created with a user's preferred configuration can be added. For example, FIG. 4 shows an example in which the ribbon 410 of the main screen 400 is configured with files, home, fax, print, which are default tabs, and my tab 411, which is a tab added by the user. FIG. 4 shows a state in which the home tab is selected, and the home tab includes a clipboard that is a default group, an open operation, a PDF operation, and a my group 412 that is a user added group. . In the my group 412, a file transfer button 473, a fax button 474, and a print button 475 of an output bar 470, which will be described later, are arranged. This is realized by quoting the setting information of the output bar 470.

Although the quick access toolbar 420 is not classified by tabs or groups, function buttons can be arranged, and the function desired by the user can be quickly accessed like the ribbon 410. Therefore, operability in using the application can be improved by arranging frequently used functions.
The address bar 430 can display URL (Uniform Resource Locator) information of the storage location of the document currently displayed in the file list pane 450, or can display the designated storage location by inputting a URL character string.

  In the library pane 440, an external storage location such as a folder on a local drive or a folder on a network can be registered as a library, and documents and folders in the library can be viewed and operated. In FIG. 4, local folders 441 (local folder 01 and local folder 02) indicating folders on the local drive are registered as libraries. In addition, a network folder 442 (a network folder 01, a local folder 02, and a network folder 03) indicating folders on the file server 102 is registered as a library. FIG. 4 shows a state in which the network folder 01 is expanded and a lower “01” folder is selected. A “monitoring folder 443” under the network folder 03 represents a folder monitoring function and indicates a state in which the network folder 03 is a monitoring target. The folder monitoring function is a function that can set a folder under the library as a monitoring target and monitors the state (new arrival, update, etc.) of a document in the folder set as the monitoring target and notifies when there is a change. As another example, a hot folder function can be set for a folder under the library. This function uses an arbitrary folder on the local drive or file server 102 as a transfer source, and sets a folder under the library as a transfer destination, so that a document stored in the transfer source can be transferred to a transfer destination under the library. This is a function to automatically transfer to a folder.

The file list pane 450 can display information on documents and folders in the library in a list format or a thumbnail format. In the list display, it is possible to display attribute information of documents and folders such as name, file type, size, update date and time. Various operations such as copying and deleting can be executed by selecting a document or folder on the file list pane 450. FIG. 4 shows a state in which documents in the “01” folder under the network folder 01 selected in the library pane 440 are displayed as a list, and “Document-B” is selected.
Preview pane 460 displays a preview of the document selected in file list pane 450.

  Function buttons for executing document output processing can be arranged on the output bar 470. A document is selected in the file list pane 450 and the button of the output bar 470 is executed. Alternatively, by dragging a document on the file list pane 450 and dropping it on the button of the output bar 470, output processing of the button is executed. In FIG. 4, a print setting button 471, a mail button 472, a file transfer button 473, a fax button 474, and a print button 475 are arranged as buttons on the output bar 470. The print setting button 471 and the mail button 472 are buttons arranged by default, and the file transfer button 473, the fax button 474, and the print button 475 are buttons added by the user according to the user's usage.

A print setting button 471 displays a print preview of the selected document, and opens a print setting screen (not shown) of the document management application 300 that can specify the print setting.
The mail button 472 is a button for transmitting the selected document by mail, and displays the mail transmission screen of the default mail application of the OS in a state where the selected document is made an attached file by executing the button.
The file transfer button 473 is a button for transferring the selected document to a specific folder, and the selected document can be moved or copied to the transfer destination by executing the button. The transfer destination can be specified by the setting of this button, and the folder under the library can be specified as the transfer destination. In addition, processing contents at the time of execution (move or copy, file name specification at the time of execution, etc.) can be set.
A fax button 474 is a button for sending a selected document by fax, and instructs the MFP 103 to send a fax of the selected document by executing the button. An OS fax (queue) can be assigned as the setting of this button, and at the time of execution, fax transmission is executed by instructing the fax.
A print button 475 is a button for printing the selected document. Like the fax button 474, the print button 475 instructs the MFP 103 to print the selected document by executing the button. An OS printer (queue) can be assigned as the setting of this button, and at the time of execution, printing is executed by instructing the printer. In addition, a print template 476 having print setting information can be set. If the print template 476 is set, printing is executed by reflecting the print setting of the print template 476.

  5 to 7 are diagrams showing examples of the data structure of the setting file of the document management application 300. FIG. By saving the setting information of the document management application 300 in the external memory 206 as a setting file, the application can be used with the same setting as the previous time when the document management application 300 is restarted next time. 5 to 7 show an example of saving in the Extensible Markup Language (XML) format as an example of the setting file saving format. The storage format may be a general text format storage and is not particularly limited to XML.

  As shown in FIG. 4, the document management application 300 is composed of a plurality of UI components and has a plurality of functions. The document management application 300 stores and manages setting files separately for each UI component and function. For example, the setting information of the ribbon 410 and the setting information of the quick access toolbar 420 are stored as separate setting files. In this embodiment, as an example of a setting file of the document management application 300, a data structure of a ribbon setting 500, a library setting 520, an output bar setting 530, a monitoring folder setting 540, and a hot folder setting 550 will be described.

A ribbon setting 500 (RibbonSetting.xml) in FIG. 5 is a setting file for ribbon settings, and defines the configuration of tabs, groups, and buttons of the ribbon 410. A list 501 (RibbonSettings) is a list of ribbon settings, tab information 502 (“Ribbon”) is 1 tab information, group information 503 (“Group”) is 1 group information, and button information 504 (“Control”) is 1 button information. Show. The home tab 505 is information corresponding to the home tab in FIG. 4, and includes a clipboard 506 that is clipboard group information during the definition of the home tab 505, and a copy button 507 that is a definition of the copy button during the definition of the clipboard 506. . The clipboard 506 is defined as a default ID (“GROUP_CLIPBOARD”).
The my group 508 is information corresponding to the my group 412 added by the user, and a GUID (Globally Unique Identifier) dynamically generated at the time of setting is assigned to the definition as id information. A fax button 509 indicates information on a fax button arranged on the my group 412, and a GUID generated when a fax button is added to the output bar is assigned as id information. This id is the same as the definition in the setting of the output bar described later, and the “fax” button in the output bar can be identified using this id information as a key. A My Tab 510 shows the definition of the My Tab 411 in FIG. 4 added by the user.

  A library setting 520 (LibrarySetting.xml) in FIG. 6A is a library setting setting file, and defines information on a registered library. A list 521 (LibrarySettings) indicates a list of library settings, and a library 522 (Library) indicates setting information of one library. In the library 522, a library display name (DisplayName) and library path information (RootPath) are defined as library information. In addition, the library type is defined so that the library type can be classified according to the library type (Type). A local library 523 indicates a local library that is a library on a local drive, and a network library 524 indicates a network library that is a library on a network folder.

  An output bar setting 530 (“OutputButtonSetting.xml”) in FIG. 6B is an output bar setting file and defines a button configuration on the output bar. A list 531 (“OutputButtonSettings”) shows a list of button settings on the output bar, and a button 532 (“OutputButton”) shows the definition of one button on the output bar. Button information 533 to 537 defines button information corresponding to each button in FIG. Button information 533 is a print setting button 471, button information 534 is a mail button 472, button information 535 is a file transfer button 473, button information 536 is a fax button 474, and button information 537 is a definition of a print button 475. A GUID is assigned to the button information 535 of the file transfer button as ID information (ID) serving as an identifier of the button, and information on a display name (Display), a transfer destination folder path (FolderPath), and an execution process type (ActionType) is provided. Define. In this example, a folder under the network folder 03 of the library is designated as the transfer destination folder path. In the button information 536 of the fax button, ID information and a display name are defined as described above. Further, the button information 536 defines a fax name (FaxName) indicating the name of an OS fax, a fax driver name (DriverName) used for fax transmission, and address (Address) information of the MFP 103 that is the target of fax transmission. The button information 537 of the print button defines ID information, a display name, and a printer name (PrinterName) indicating the name of the OS printer. Further, the button information 537 defines the name of the printer driver (DriverName) used for printing, the address (Address) of the MFP 103 that is the object of the print instruction, and the print template (Template) information.

  A monitoring folder setting 540 (MonitorSetting.xml) in FIG. 7A is a setting file for monitoring folder setting, and defines monitoring folder information. A list 541 (MonitorSettings) indicates a list of monitoring folder settings, and a monitoring folder information 542 (Monitor) indicates setting information of one monitoring folder. As the monitoring folder setting information, a library path (LibraryPath) to be monitored and a folder path (FolderPath) to be monitored are defined. In this example, a monitoring folder under the network folder 03 of the library is designated as the monitoring folder.

  7B is a hot folder setting setting file, and defines hot folder setting information. A list 551 (HotFolderSettings) shows a list of hot folder settings. Information 552 (HotFolder) indicates the setting information of one hot folder, which defines a transfer source folder path (SourcePath) and a transfer destination folder path (DestPath) as the hot folder setting information. The upper folder is designated, and the “transfer” folder under the library “network folder 03” is designated as the transfer destination.

  The UI and setting file of the document management application 300 have been described with reference to FIGS. As described above, the document management application 300 includes a plurality of UI components and functions, and the setting information is managed separately for each UI and function. In addition, there may be a dependency relationship between setting information, such as a ribbon and an output bar, a monitoring folder and a library, and a print button and a print template of the output bar. In such a case, there is a problem in that consistency between setting information for transferring only a part of the settings cannot be obtained, and the application does not operate normally after the migration. For example, when the output bar button is placed on the ribbon and only the ribbon setting is to be migrated and migrated to another environment, the definition of the output bar button does not exist in the migration destination environment. Therefore, the corresponding button information on the output bar cannot be referred to when using the document management application 300 after the migration, and is not displayed on the ribbon, or cannot be executed (error) when the button is executed.

Next, an example of setting migration processing by the document management application 300 is shown. 8 to 12 are diagrams showing examples of the UI screen of the document management application 300. FIG.
The setting transfer screen 600 is a setting transfer screen for the document management application 300. This screen can be activated independently of the main screen 400 described above, and is a screen for exporting or importing the setting information of the document management application 300. When the export is executed, an export file enclosed with export information including information such as a setting file, application version information, user name, export type (all settings / part) is generated and output. On the other hand, when importing, the export file is expanded, and the included setting file is placed in the storage location of the application setting file. In this way, the setting information is transferred.

First, the screen transition of the setting transition screen 600 when the document management application 300 performs the export will be described with reference to FIGS.
An import button 601 and an export button 602 in FIG. 8A are radio buttons for designating whether to execute import or export. When the import button 601 is selected and executed, import is performed, and when the export button 602 is selected and executed, export is performed. A check box 603 is a check box for designating whether to select a setting item to be exported, and is displayed when the export button 602 is selected. When the check box 603 is turned off and executed, the export is executed for all setting information. On the other hand, when the check box 603 is checked and executed, the process proceeds to the export target selection list 607 shown in FIG. The execution button 604 is a button for executing selection. When the check box 603 is ON, the display of the button is set to “next”, and the execution transits to the item designation selection list 607. A cancel button 605 is a button for canceling the import or export operation. When the cancel button 605 is pressed, the setting transfer screen 600 is closed. In the setting migration screen 600 of FIG. 8A, the export button 602 is selected, and the export target check box 603 is ON. By designating in this way and pressing the execution button 604, the screen shifts to the setting transition screen 606 in FIG.

A setting transition screen 606 in FIG. 8B is a screen displayed when the check box 603 is checked in FIG. 8A and executed. A selection list 607 is a list for selecting a setting item to be exported, and the setting information selected here is exported. In FIG. 8B, as setting information of the document management application 300, ribbon setting, library setting, output bar setting, stamp setting, and print template setting are listed and displayed in a selectable state. In the present embodiment, only a part of the settings of the document management application 300 can be selected. However, all the settings of the document management application 300 may be listed in the selection list 607 and can be selected. The execution button 604 is a button for executing processing. On the screen on which the selection list 607 is displayed, the button display is “OK”, and execution is performed to execute export or import processing. The return button 608 is displayed only in the state of the item designation selection list 607, and returns to the previous screen when pressed. In the setting migration screen 611 in FIG. 8B, setting items to be exported are specified. Here, the ribbon setting and the library setting are selected in the selection list 607. By executing the execution button 604 in this state, the screen shifts to a setting transfer screen 609 in FIG.
The setting migration screen 609 in FIG. 8C displays a storage destination designation screen for designating the export file storage destination. By specifying the file storage location and file name on the designation screen and executing the OK button 610, the export file is output to the designated storage location with the designated file name.

A setting transition screen 611 in FIG. 9A is a screen indicating that the export process is in progress. When the export is completed, a message indicating the completion of the export is displayed on the setting transition screen 612 illustrated in FIG. Exit.
The setting migration screen 613 in FIG. 9C is displayed when some, but not all, setting information is selected as an export target, and there are settings related to the setting selected as the export target. It is a screen. When exporting some setting information by selecting the export target, check whether there is a setting related to the setting selected as the export target. If related settings exist, check whether the relevant settings are included in the export target. If not, notify that there are related settings and whether to export the settings. Ask the user whether or not. For example, if a ribbon setting that includes an output bar button is specified as an export target, a screen is displayed to confirm to the user whether to export including the output bar setting, which is a setting related to this ribbon setting. indicate. By executing the Yes button 614 on the setting transition screen 613, the settings of the output bar, which are related settings, can be exported together. When the No button 615 is executed, the export is performed without including related settings. By exporting related settings together, it is possible to prevent the ribbon buttons from being disabled at the migration destination.

Next, screen transition of the setting transition screen 600 when importing the document management application 300 will be described with reference to FIGS. 10 and 11.
A setting transition screen 616 in FIG. 10A is a screen that is displayed when the import button 601 is selected for import. A box 617 is a text box for designating setting information (export file) to be imported, and is displayed when the import button 601 is selected for import. The export file can be specified by directly inputting into the box 617, but the export file can also be specified by displaying a file reference screen with a reference button 618 and selecting a file. A reference button 618 is a button for designating an export file, and displays a file reference screen for designating a file when pressed. When the execute button 604 is pressed, the export file specified in the box 617 is imported. In the setting migration screen 619 in FIG. 10A, an import button 601 is selected, and an export file to be imported is specified in a box 617. The import is executed by designating in this way and executing the execute button 604.
A setting migration screen 619 in FIG. 10B is a screen indicating that import processing is in progress. When the import is completed, a message indicating the import completion on the setting migration screen 620 shown in FIG. 10C is displayed and the import process is terminated.

The setting migration screen 621 in FIG. 11A is displayed when a setting file exists in the import destination environment. At the time of import execution, it is confirmed whether or not the setting file exists in the environment of the import destination, and if it already exists, the user is notified that the setting is overwritten.
In addition, when importing some exported settings, replacing only some functions may cause the settings already used at the import destination to not work properly. Specifically, if there is another setting related to the setting that is overwritten by import, the function may not operate normally due to overwriting. Therefore, the user is informed that there is a possibility that it will not operate normally due to overwriting, and the user is asked how to perform the import process.

  A setting transition screen 622 in FIG. 11B is a screen for notifying the user that there is a possibility that the operation may not be normally performed due to overwriting, and asking the user how to perform the import processing. As import processing, it is possible to select one of merge that adds import settings to existing settings, invalidate related settings that invalidate (discard) related settings, continue importing, or cancel. On the setting migration screen 622, press the merge button 623 to merge, press the invalidate related settings button 624 to invalidate related settings, press the continue button 625 to import as it is, and cancel button 626 to end the process. To do. Here, an example is shown in which the library settings are to be imported, and if the library settings are overwritten, the migration destination monitoring folder function will not operate normally (the monitoring folder cannot be referenced). In this case, when the merge button 623 is executed, the library setting to be imported is added to the existing library setting. When the invalidation button 624 is executed, the setting of the import destination monitoring folder is deleted. When the continue button 625 is executed, the settings of the import destination library are deleted, and the library settings to be imported are copied.

Next, the flow of the export process and the import process will be described with reference to FIGS. FIG. 12 is a diagram illustrating an example of a flowchart relating to the export processing of the document management application 300. This processing is started by executing export on the setting migration screen 600 in FIG.
In step S <b> 701, the management unit 306 receives selection of settings to be exported. Specifically, when the input management unit 301 receives an execution operation of the execution button 604 on the setting transfer screen 600, the input management unit 301 notifies the management unit 306 of the execution instruction. Upon receiving the notification, the management unit 306, which is a reception unit, acquires the setting value specified by the user on the setting transfer screen 600 via the screen display management unit 302, and instructs the setting transfer unit 305 to execute the process. The setting value refers to a range to be exported (part or all), a setting item targeted for partial export, and is obtained by referring to the check box 603 and the selection list 607 on the setting migration screen 600.
In step S <b> 702, the setting transfer unit 305 refers to the setting value acquired in step S <b> 701 and determines whether the export target is specified in part or all in the check box 603. If the export target is specified for all, the process advances to step S703 to set all settings as the export target. If the export target is specified as a part, the process proceeds to S704.

In step S704, the setting migration unit 305 refers to the setting value acquired in step S701, and adds the setting designated as the export target in the selection list 607 to the export target list.
Next, the presence / absence of a setting related to each export target setting is checked. In step S705, the setting migration unit 305 sets one of the export target lists as a confirmation target, and acquires a setting related to the setting in step S706. Specifically, with reference to the related setting table shown in FIG. 14, the setting associated with the setting to be exported is determined and acquired from the information of the related setting table. In addition, the definition of the relevant setting in the current operating environment of the document management application 300 is referred to via the application information management unit 303, and depends on the setting determined to be associated with the export target and the relevant setting table. Check if the relationship exists. Here, when there is a dependency relationship, the setting is set as a related setting.

Here, the related setting table will be described with reference to FIG. FIG. 14 is a diagram schematically showing relevance and determination conditions for determining setting information of the document management application 300 and setting information related thereto.
In the related setting table 900 indicating the relationship of the setting information, the target setting file 901 and the related setting file 905 are classified, and the setting file in which the target setting file 901 and the related setting file 905 paired therewith are related. Is defined as The setting file name 902 indicates the setting file name of the target setting file, and the setting file name 906 indicates the setting file name of the related setting file. A target attribute 903 and a target attribute 907 indicate the definition of the target attribute in the setting file. This target attribute indicates the presence of a related setting when there is a corresponding definition in the setting file (if there are more conditions, a definition that matches the conditions). In addition, when the related setting exists, the condition that the reference relationship with the related setting matches can be identified by whether or not the key 904 and the key 908 match the condition of the comparison 909. The reference relationship will be described in S814 in the import flowchart.

  For example, RibbonSetting. In xml, the existence of a related setting can be confirmed when the following two conditions are met. The first condition is that “Control” is defined in the target attribute 903. The second condition is that “type” is defined as “OutputButtonPrint”, “OutputButtonFax”, and “OutputButtonSend” in the definition of “Control”. If there is no matching definition in the first place, it can be considered that there is no related setting. There is a matching definition, and its associated setting OutputButtonSetting. When the attribute definition “OutputBarButton” exists in xml, the setting values can be regarded as related settings in the following cases. The setting values can be regarded as related settings when the values defined in the keys 904 and 908 meet the condition of “Equal” (same) shown in the comparison 909.

  The related setting table 900 is information held on the program by the setting migration unit 305 of the document management application 300, and the setting items shown in this embodiment indicate some setting items of the document management application 300. In addition to the items shown in the present embodiment, it is assumed that related information is similarly defined for settings having related settings in the definition of setting items held by the document management application 300.

Returning to the flowchart of FIG. In S706, for example, when the ribbon setting is to be exported, the definition of the output bar button is included or not included in the setting of the ribbon for the output bar setting which is the setting associated with the ribbon setting. To check if it exists in the top bar. When there is a definition of the output bar button in the output bar, it is determined that there is a dependency between the ribbon setting and the output bar setting, and is regarded as a related setting.
In step S707, the setting migration unit 305 refers to the relevant setting information acquired in step S706. If the relevant setting exists, the process proceeds to step S708. If not, the process proceeds to step S715.

In step S708, the setting migration unit 305 refers to the related setting information acquired in step S706, and sets one of the related setting information as a processing target.
In step S <b> 709, the setting migration unit 305 refers to the export target list and determines whether or not the related setting that is the processing target is included in the list. If it is already included in the list, the process proceeds to S714. If not included in the list, the process proceeds to S710.

In step S <b> 710, the setting migration unit 305 instructs the screen display management unit 302 to notify that there is a related setting and display a message for confirming whether to include this setting as an export target. An example of this is a setting transition screen 613 shown in FIG.
In step S <b> 711, the input management unit 301 determines whether the related setting is included in the export target. Specifically, the input management unit 301 accepts a user operation for the message, and makes a determination with reference to a message selection result via the screen display management unit 302. If it is determined that the Yes button 614 has been executed, the process proceeds to S712. If it is determined in step S711 that the No button 615 has been executed, the process advances to step S714 without including the related setting as an export target. When the cancel is executed, the export process is stopped and this processing flow is ended.
In step S712, the setting migration unit 305 adds related settings to the export target.

  In step S713, the setting transfer unit 305 determines whether all the related settings included in the related setting information acquired in step S706 have been confirmed. If there is an unconfirmed related setting, the process advances to step S708 to repeat the confirmation process as to whether or not the next related setting should be included in the export target. If all have been confirmed, the process proceeds to S714 to determine whether all export targets have been confirmed. If there is an unconfirmed export target, the process proceeds to S705 and related settings are similarly set for the next export target. Check if there is any.

In step S <b> 715, the setting migration unit 305 exports the settings that are the export target in the above-described processing. Here, an export file that includes setting information to be exported among the setting information in the current operating environment of the document management application 300 is generated.
When you export some settings by the above process, check the settings related to the export target, and if there are related settings, make those settings also the target of export, and also set the settings that have dependencies. Can be exported.

FIG. 13 is a diagram illustrating an example of a flowchart relating to import processing of the document management application 300. This processing is started by executing import on the setting migration screen 600 in FIG.
In step S <b> 801, the management unit 306 receives a setting to be imported. Specifically, when the input management unit 301 receives an execution operation of the execution button 604 on the setting transition screen 600, the input management unit 301 notifies the management unit 306 of the execution instruction. Upon receiving the notification, the management unit 306, which is a reception unit, acquires the specified value on the setting transfer screen 600 via the screen display management unit 302, and instructs the setting transfer unit 305 to execute the process. The specified value here indicates the path of the export file used for import.

Upon receiving the execution instruction in S802, the setting migration unit 305 confirms whether the setting information (setting file) of the document management application 300 in the import destination environment that is currently operating already exists. For example, a setting file exists in an environment in which the document management application 300 is already used, and does not exist in an unused state such as at the time of introduction.
In step S803, the setting migration unit 305 refers to the confirmation result in step S802 and determines whether a setting file already exists. If a setting file already exists, the process proceeds to S804. If the setting file does not exist, the process proceeds to S807.

In step S804, the setting migration unit 305 instructs the screen display management unit 302 to display a message notifying that an existing setting file is overwritten. An example of the displayed message is a setting transition screen 621 shown in FIG.
In step S <b> 805, upon receiving a user operation for the message displayed in step S <b> 804, the input management unit 301 refers to the message selection result via the screen display management unit 302. If it is determined that the “Yes button” indicating selection to overwrite and execute import has been executed, the process advances to step S806 to continue the process. If it is determined that the “No button” indicating the selection to cancel the import execution has been executed, the import process is stopped and the process flow ends.
In step S806, the setting migration unit 305 creates a backup file of the setting file to be overwritten at the import destination. Specifically, the setting file in the current operating environment is copied to the backup destination. This backup file is a file that is saved so that it can be manually restored when the setting file is overwritten due to an erroneous operation.

In step S807, the setting migration unit 305 reads the export file specified by the screen setting value acquired in step S801. The export file is a file that includes the setting file and the export information as described above, and the information is expanded here.
In step S808, the setting migration unit 305 sets the setting file included in the export file as an import target and adds it to the import target list. The information to be imported is the import file name and the import method information (replacement (default) / merge), and has such information in a list. When the list to be imported is created, the default “Replace” is selected as the import method.
In step S809, the export type of the export information included in the export file is referenced to determine whether the import target is “partial” or “all”. If the target is “all”, the process advances to step S824 to execute import processing. When the target is “partial”, the process proceeds to S810.

In step S810, the setting migration unit 305 sets one of the import target lists created in step S808 as a check target.
In step S811, the setting migration unit 305 acquires settings related to settings to be overwritten by import. The settings that are overwritten by the import are the same settings at the import destination as the settings to be imported. For example, when a library setting that is one of the import targets is set as a check target, the setting that is overwritten by the import is the library setting at the import destination. Specifically, the setting transfer unit 305 refers to the related setting table 900 shown in FIG. 14 held in the setting transfer unit of the document management application of the import destination, and sets a setting that refers to an overwritten setting as a related setting. Judge and get. For example, when the import target is set as a library setting, the monitoring folder setting, hot folder setting, and output bar setting that refer to the library setting are acquired as related settings.
In step S812, the setting transition unit 305 determines whether there is a related setting as a result of step S811. If it is determined that the related setting exists, the process proceeds to S813. If it is determined that the related setting does not exist, the process proceeds to S822.

In step S813, the setting migration unit 305 determines whether the related setting determined to exist in step S812 is included in the import target list. If it is included in the list, it has already been designated as the import target by the user, so the process proceeds to S822. If it is not included in the list, the process proceeds to S814.
In step S814, the setting migration unit 305 determines whether the reference relationship condition is satisfied between the setting to be imported and the setting related to the existing setting that may be overwritten by the import. The condition of this reference relationship is whether there is a possibility that the function of the setting related to the existing setting cannot be used when an existing setting (overwritten setting) is replaced with the imported setting. It is for judging. Even when a certain existing setting is replaced with the imported setting, if the function of the setting related to the existing setting can be used, it is determined that the reference relationship condition is satisfied. In the determination of this condition, it is confirmed whether definition information (XML attribute) having a reference relationship exists, and if it exists, it is confirmed whether the reference relationship of the set value is established.

  Specifically, first, as a first determination, it is determined whether a setting that relates to an existing setting includes a definition that refers to the existing setting. If a definition that refers to the existing setting is not included, it is not necessary to refer to the existing setting, so it is determined that the reference relationship condition is satisfied. If a definition that refers to the existing setting is included, a second determination is made. In the second determination, it is determined whether or not the setting related to the existing setting is a relationship in which the setting to be imported can be referred to. Specifically, it is determined based on whether or not a root path to a setting related to an existing setting is defined in the setting to be imported. If the setting related to the existing setting is a relationship that can refer to the setting to be imported, it is determined that the condition of the reference relationship is satisfied. For example, in the case of the monitoring folder setting, first, as a first determination, it is confirmed whether a monitoring folder definition (“Monitor” of the monitoring folder setting 540 in FIG. 7A) exists during the setting. If there is no monitoring folder definition, it is assumed that there is no definition that requires a reference relationship, and it is determined that the condition is satisfied. If the definition of the monitoring folder exists, it is confirmed as a second judgment whether the library information of the monitoring folder exists in the library setting to be imported. The library information of the monitoring folder is the LibraryPath of the monitoring folder setting 540 of FIG. 7A, and the library setting to be imported is the Library RootPath of the library setting 520 of FIG. 6A. When the LibraryPath exists in the RootPath of the Library, the reference condition is satisfied, and when the LibraryPath does not exist, it is determined that the reference condition is not satisfied. If it is determined that the condition is satisfied, the process proceeds to S822. If it is determined that the condition is not satisfied, the process proceeds to S815.

In step S815, the setting migration unit 305 instructs the screen display management unit 302 to notify that another existing function related to the setting to be imported may not work, and displays a message asking about the import method. . An example of the message asking about this import method is the migration setting screen 622 in FIG.
In step S <b> 816, when the input management unit 301 receives a user operation for the message displayed in step S <b> 815, the input management unit 301 refers to the message selection result via the screen display management unit 302. In the migration setting screen 622, when it is determined that the merge button 623 for adding the import setting to the existing setting has been executed, the process proceeds to S817, and otherwise, the process proceeds to S818.
In step S817, the setting migration unit 305 determines that the import method of the import target that is the current processing target is merge, and proceeds to step S822. Specifically, the import method information is merged (added) as the import target information in the import target list described above.

In step S818, the input management unit 301 determines whether the user's selection result for the message displayed in step S815 is discard of the related setting. When the related setting invalidation button 624 is executed on the migration setting screen 622, it is determined that discarding of the related setting is selected, and the process proceeds to S819. Otherwise, the process proceeds to S820.
In step S819, the setting transfer unit 305 adds the related setting as a discard target, and the process proceeds to step S822. Here, the discard target to be added in this process is held in a list, and the corresponding setting is discarded in the process of S823 described later for the list.

In step S820, the input management unit 301 determines whether the user's selection result for the message displayed in step S815 is to perform import as it is. When the continue button 625 is executed on the migration setting screen 622, it is determined that the import is performed as it is, and the process proceeds to S822. In other cases, the cancel button 626 is executed, and the process proceeds to S821.
In step S821, the input management unit 301 cancels the import process by discarding the backup file created in step S806, which is no longer necessary, and stops the processing flow.

In step S822, the setting migration unit 305 determines whether all targets in the import target list have been confirmed. If there is an unconfirmed target, the process proceeds to S810, and the confirmation process is similarly executed for the next import target. If all have been confirmed, the process proceeds to S823.
In S823, if there is a related setting to be discarded, the setting transfer unit 305 discards the setting. This discard target refers to a related setting that is set as the discard target in S818, and an existing setting file corresponding to the discard target existing in the import destination is deleted. Note that the corresponding setting value may be retained as the discard information, and only the corresponding setting value in the setting file may be deleted. When the deletion of the discard target is completed, the process proceeds to S824.

  In step S824, the setting migration unit 305 imports the settings of the import target list. Specifically, the setting file that matches the import file name is imported from the export file expanded in S807 to the import destination. As an import method, there are replacement and merging. The merge is a case where merge is designated in S817, and the other processing is performed as replacement. In case of import by replacement, replace the configuration file existing in the import destination environment with the import file of the same name in the export file. When importing by merging, add the information of the import file with the same name to the configuration file existing at the import destination. For example, when a library setting is imported by merging, the setting file of the library at the import destination and the setting file to be imported are read, and the definition that does not exist in the definition of the import destination is added and saved. Note that the setting file reading process and writing process are processed by instructing the application information management unit 303 from the setting transfer unit 305. This processing flow ends when the import processing in S824 is completed.

  As described above, when some settings are exported in this embodiment, the settings related to the export target are confirmed, and if there are related settings, the settings are also exported and the dependency relationship is Some settings can also be exported. In addition, when importing some exported settings, the migration method of adding to the existing settings at the import destination prevents the related settings that depend on the existing settings from working properly. it can. Therefore, according to the present embodiment, it is possible to suppress the occurrence of inconsistency when only a part of the setting information of the application is migrated.

(Second Embodiment)
In the first embodiment, an example is shown in which setting items to be exported are selected at the time of export. However, a configuration may be selected that is selected at the time of import. This embodiment considers such a configuration, and an example in which setting items to be targeted at the time of import are selected will be described with reference to FIGS. 15 to 17. It should be noted that all the configurations and processes not particularly specified are the same as those in the first embodiment.

  Screen transition of the setting transition screen of the document management application 300 at the time of import execution in the present embodiment will be described with reference to FIG. FIG. 15 shows an example of a UI screen of the document management application 300. Note that the setting transfer screen of the document management application 300 in the present embodiment is the same as the setting transfer screen shown in FIGS. 8 to 11, and the configuration not specifically described is the same as the setting transfer screen of FIGS. 8 to 11.

  The setting migration screen 1000 in FIG. 15A is a screen for selecting whether to execute import or export. A check box 1001 on the setting migration screen 1000 is a check box for designating whether to select a setting item to be imported, and is displayed when the import button 601 is selected. When executing with the check box 1001 OFF, the import is executed for all the setting information in the export file to be imported. On the other hand, when the chuck is inserted into the chuck box and executed, a transition is made to the selection screen shown in FIG. When the check box 1001 is ON, the execution button 604 changes the display of the button to “next” and transitions to the item designation setting transition screen 1002 by execution. When the cancel button 605 is pressed, the operation is canceled and the setting transfer screen 600 is closed without executing the import. In FIG. 15A, an import button 601 is selected, and an export file to be imported is designated in a box 617. In addition, a check box 1001 for selecting an import target is selected to be ON. By executing the execute button 604 in this state, the screen shifts to the setting transfer screen 1002.

  A setting transition screen 1002 in FIG. 15B has a selection list 1003. A selection list 1003 is a list for selecting a setting item to be imported, and the setting information selected here is imported. In FIG. 15B, ribbon setting, library setting, output bar setting, stamp setting, and print template setting are listed and displayed as setting information of the document management application 300 in a list. In the present embodiment, only a part of the settings of the document management application 300 can be selected. However, all the settings of the document management application 300 may be listed in 606 and selected. In FIG. 15B, the ribbon setting and the library setting are selected as setting items to be imported.

  When importing some settings, the setting migration screen 1004 in FIG. 15C notifies that there is a related setting in the setting, and a message for confirming whether or not this related setting is included in the import target. Is a screen for displaying. When part of the setting information is imported as in the present embodiment, it is confirmed whether the setting related to the setting selected as the import target exists in the setting in the export file. If there is a related setting, the user is notified that there is a related setting and asks the user whether to import the setting including that setting. For example, if the ribbon setting is specified as the import target and the output bar button is included in the ribbon setting, importing the output bar setting also disables the ribbon button at the migration destination. Can be suppressed.

  FIG. 16 is a diagram illustrating an example of a flowchart relating to import processing of the document management application 300. The import process is started by executing the import on the setting migration screen 1000 in FIG. Note that the import processing in the present embodiment is based on the import processing shown in FIG. 13, and the configuration that is not particularly described is the same as the processing flow shown in FIG.

In step S <b> 1101, when the input management unit 301 receives an execution operation of the execution button 604 while the import button 601 is selected on the setting migration screen 1000, the input management unit 301 notifies the management unit 306 of the execution instruction. Upon receiving the notification, the management unit 306 instructs the setting migration unit 305 to read the export file. Specifically, the export file information specified in the box 617 of the setting migration screen 1000 is expanded.
In step S1102, the setting migration unit 305 sets the setting file included in the export file as an import target and adds it to the import target list. The list has an import file name and import method information (replacement (default) / merge) as information to be imported. When the list to be imported is created, the default “Replace” is selected as the import method.

In step S1103, the setting migration unit 305 determines whether the import target is all setting information or some setting information. If the check box 1001 is checked on the setting migration screen 1000, it is determined that the import target is some setting information, and the process advances to S1004. On the other hand, if it is determined that the import target is all setting information, the process proceeds to S1006.
In step S1104, the setting migration unit 305 instructs the screen display management unit 302 to display the import target selection screen. Upon receiving the instruction, the screen display management unit 302 displays a setting migration screen 1002 including an import target selection list 1003 for allowing the user to select setting information to be imported based on the import target list created in S1102. . An example of this is shown in FIG.

In step S <b> 1105, when the input management unit 301 accepts pressing of the execution button 604 or the cancel button 605 on the setting transition screen 1002, the input management unit 301 notifies the management unit 306 of the execution instruction. Upon receiving the notification, the management unit 306 refers to the execution information of the button, and when it is determined that the execution button 604 is executed, the management unit 306 proceeds to S1106. On the other hand, if it is determined that the cancel button 605 has been pressed, the screen display management unit 302 is instructed to close the setting transition screen 600, stop the import process, and end the present processing flow.
In step S <b> 1106, the management unit 306 receives selection of an import target, acquires a specified value on the setting migration screen 1002 via the screen display management unit 302, and instructs the setting migration unit 305 to update the import target list. The value specified here is a setting item selected in the import target range and the import target selection list 1003 with part or all of the import target.

Next, it is checked whether there is a setting related to each import target setting.
The setting transfer unit 305 that has received the execution of the import process in S1107 sets one of the import target lists as a check target.
In step S1108, the setting migration unit 305 acquires settings related to the settings set as confirmation targets in step S1107. Specifically, with reference to the related setting table 900 shown in FIG. 14, settings related to the setting to be imported are determined and acquired from the information of the related setting table 900. Further, the definition of the related setting included in the export file is referred to via the application information management unit 303, and it is confirmed whether there is a dependency relationship with the import target. Here, when there is a dependency relationship, the setting is set as a related setting. For example, when importing ribbon settings, the output bar settings that are related to the ribbon settings are targeted, and if the ribbon settings include or include output bar button definitions, the definitions are output. To check if it exists in the top bar. If it exists, it is regarded as a related setting.
In step S1109, the setting transition unit 305 refers to the related setting information acquired in step S1108. If the related setting exists, the process proceeds to step S1110, and if not, the process proceeds to step S1117.

In step S1110, the setting migration unit 305 refers to the related setting information acquired in step S1108, and sets one of the related setting information as a processing target.
In step S1111, the setting migration unit 305 determines whether the related setting that is the processing target in step S1110 is already included in the import target list. If it is included in the list, the process proceeds to S1115, and if it is not included in the list, the process proceeds to S1112.

In step S <b> 1112, the setting migration unit 305 instructs the screen display management unit 302 to notify that there is a related setting and display a message for confirming whether to include this setting as an import target. An example of this is a setting transition screen 1004 shown in FIG. By executing the Yes button 1005 on the setting transition screen 1004, the relevant settings are imported together.
In step S1113, when the input management unit 301 receives a user operation for the message on the setting transition screen 1004, the input management unit 301 refers to the message selection result via the screen display management unit 302, and proceeds to step S1114 when determining that the yes button 1005 has been executed. move on. If it is determined in step S1113 that the No button 1006 has been executed, the process advances to step S1115 without including the related setting as an import target. When the cancel button 1007 is executed, the export process is stopped and the process flow ends.
In step S1114, the setting migration unit 305 adds related settings to the import target.

In step S1115, the setting migration unit 305 determines whether all the related settings acquired in step S1108 have been confirmed. If there is an unconfirmed related setting, the process proceeds to S1110 and the confirmation process is similarly executed for the next related setting. If all have been confirmed, the process proceeds to S1116.
In step S1116, the setting migration unit 305 determines whether all export targets have been confirmed. If there is an unconfirmed export target, the process proceeds to step S1107, and the related setting is similarly set for the next export target. Check for presence. If all have been confirmed, the process proceeds to S802.

  The subsequent processing is the same as the flow shown in FIG. However, the determination in S1117 whether the setting of the import target is “partial” or “all” is different from the determination in S809 of FIG. Therefore, only the difference will be described, and other processes will be omitted. Since the processing flow shown in FIG. 13 is not a flow for selecting an import target at the time of import, in S809, part of the settings for import or all of them are determined by referring to the export type included in the export file. On the other hand, this embodiment is processing when selecting an import target at the time of import, and the determination in S1117 is that the range of import targets specified by the user acquired in S1106 indicates “partial” or “all”. Judgment by. Therefore, in S1117, it is determined that a part of the setting is to be imported when the check box 1001 in FIG. 15A is specified to be ON (a part of the setting item is imported).

  As described above, when some settings are selected and imported in this embodiment, the settings related to the import target are checked, and if there are related settings, the settings are also set as the import target. Settings with dependencies can also be exported. Further, by adopting a migration method of adding to existing settings at the import destination, it is possible to suppress the possibility that related settings depending on the existing settings will not operate normally. Therefore, according to the present embodiment, it is possible to suppress the occurrence of inconsistency when only a part of the setting information of the application is migrated.

(Third embodiment)
In the third embodiment, the transition of the setting transition screen displayed when selecting the setting to be imported is different from that in the second embodiment. Only the parts different from the second embodiment will be described below.
FIG. 18 is an example of a UI screen of the document management application 300, and shows a screen transition of a setting transition screen at the time of import execution.
FIG. 18A is an example of a screen that is displayed when a selection to import only some of the settings is made. The setting transfer screen 1200 includes a selection list 1201 that is displayed when the execution button 604 is executed in the setting transfer screen 600 when the import target check box 1001 is ON. The selection list 1201 indicates that the setting to be imported is not selected. Check if there is a related setting for the output bar setting selected here, and if there is a related setting, notify that there is a related setting and whether to import including that setting. Ask the user. For example, a setting transition screen 1004 in FIG. 15C is displayed as a screen for notifying that there is a related setting.
For example, when the output bar setting is checked on the setting transition screen 1200, a screen asking the user whether to import including the setting of the print template, which is a related setting, is displayed. Here, when the import including the setting of the print template is selected, a setting transition screen 1202 shown in FIG. 18B is displayed. In the selection list 1203 on the setting transfer screen 1202, in addition to the output bar setting, the check box for setting the print template is also ON.

FIG. 19 is a diagram illustrating an example of a flowchart relating to the related setting confirmation process on the setting transition screen of the document management application 300. This process is started when the import button 601 is selected on the setting migration screen 1000 and the execution button 604 is pressed while the check box 1001 is ON.
In step S1301, the screen display management unit 302 displays a setting transition screen 1200 and waits for a user operation. The setting migration screen 1200 displays an import target selection list 1201.
In step S <b> 1302, when the input management unit 301 receives an execution operation on the import target selection list 1201 on the setting migration screen 600, the input management unit 301 notifies the management unit 306 of the execution instruction. Upon receiving the notification, the management unit 306 determines whether or not the check box of the item is designated ON in the import target selection list 1201. If it is designated ON, the process advances to step S1303 to confirm settings related to the selected setting item. Otherwise, it waits for a user operation in S1301.

In step S <b> 1303, the management unit 306 acquires the specified value on the setting transition screen 1200 via the screen display management unit 302, and instructs the setting transition unit 305 to execute related setting confirmation processing. The value specified here indicates the setting item selected in the selection list 1201 to be imported.
In step S <b> 1304, the setting migration unit 305 sets a setting item selected in the import target selection list 1003 as a check target, and acquires settings related to the setting. Specifically, the related setting table shown in FIG. 14 is referred to, and the setting associated with the setting is acquired. Further, the definition of the related setting included in the export file is referred to via the application information management unit 303, and it is confirmed whether there is a dependency relationship with the import target. Here, when there is a dependency relationship, the setting is set as a related setting. For example, if ribbon settings are to be imported, the output bar settings that are related to the ribbon settings are included in the output bar buttons, or the definitions of the output bar buttons are included in the output. To check if it exists in the top bar. If it exists, it is regarded as a related setting.

In step S1305, the setting migration unit 305 refers to the related setting information acquired in step S1304. If there is a related setting, the process proceeds to step S1306. If there is no related setting, the confirmation process is terminated and the present process flow is terminated.
In step S1306, the setting migration unit 305 refers to the related setting information acquired in step S1304, and sets one of the related setting information as a processing target.
In step S <b> 1307, the setting migration unit 305 determines whether the related setting that is the processing target in step S <b> 1306 is already included in the import target. If it is included in the import target, the process proceeds to S1311 without executing the processes after S1308. If it is not included in the import target, the process advances to step S1308.

In step S1308, the setting migration unit 305 instructs the screen display management unit 302 to notify that there is a related setting, and displays a message for confirming whether or not to include this setting as an import target. An example of this is shown in FIG.
In step S <b> 1309, when the input management unit 301 receives a user operation for the message, the input management unit 301 refers to the message selection result via the screen display management unit 302. If it is determined that the YES button 1005 has been executed, the process advances to step S1310 to add related settings to the import target. If it is determined that the No button 1006 has been executed, the process proceeds to S1311 without including the related setting as an export target.
In step S1311, the setting migration unit 305 determines whether all the related settings included in the related setting information acquired in step S1304 have been confirmed. If there is an unconfirmed related setting, the process proceeds to S1306, and the confirmation process is similarly executed for the next related setting. If all have been confirmed, the process proceeds to S1312.

  In step S1312, the setting transition unit 305 instructs the screen display management unit 302 to display the selection list 1003 to be imported on the setting transition screen 600 so that the setting check box added in step S1310 on the selection list 1201 is turned on. Update. For example, if the check box for the output bar setting is turned ON in the setting transfer screen 1200, a message asking whether to include the setting of the print template, which is the related setting, in the import target is displayed. Therefore, if the user selects to include the print template setting as an import target, a setting transfer screen 1202 having a selection list 1203 in which the check box for the print template setting shown in FIG. 18B is also displayed is displayed.

  As described above, when some settings are selected and imported in this embodiment, the settings related to the import target are checked, and if there are related settings, the settings are also set as the import target. Settings with dependencies can also be exported. Further, by adopting a migration method of adding to existing settings at the import destination, it is possible to suppress the possibility that related settings depending on the existing settings will not operate normally. Therefore, according to the present embodiment, it is possible to suppress the occurrence of inconsistency when only a part of the setting information of the application is migrated.

(Fourth embodiment)
In the first to third embodiments, the relationship between the settings of the document management application 300 is considered, and if there is a related setting, the setting is also exported or imported to maintain consistency between the settings. An example of processing so as to lean is shown. However, there is a case where a configuration related to the setting other than the setting of the document management application 300 is required. Specifically, an image processing apparatus that performs printing or fax transmission can be used. In the setting of a function that uses a printer of an OS that is an example of an image processing apparatus, the corresponding function of the document management application 300 cannot be used when the printer that corresponds to the setting transfer destination OS is not registered.
The present embodiment takes such a configuration into consideration, and in the import processing of the document management application 300, when importing settings that refer to a printer of the OS, a processing example relating to the presence confirmation of the printer and a countermeasure method for the printer will be described. . Specifically, an example of reference change to a printer when a driver exists but a printer with the same configuration exists, and an example of registering a printer in the OS when a printer with the same configuration does not exist are shown. Furthermore, an example of driver installation processing when no driver exists is shown.

Hereinafter, a description will be given with reference to FIGS. All configurations and processes not particularly specified are the same as those in the first embodiment or the second embodiment.
FIG. 20 is a diagram illustrating an example of a software configuration of the document management application 300 executed on the client PC 101 and the client PC 110. The document management application 300 is installed in the client PC 101, and the program is stored in the ROM 204 or the external memory 206 of the client PC 101. That is, the CPU 201 loads the program into the RAM 203 and executes it, thereby realizing the functions of the document management application 300 and the processing related to the flowchart described later.

  The document management application 300 includes an input management unit 301, a screen display management unit 302, an output control unit 304, an application information management unit 303, a setting transition unit 305, a management unit 306, and a printer management unit 1401. The input management unit 301, the screen display management unit 302, the output control unit 304, the application information management unit 303, the setting transition unit 305, and the management unit 306 are the same as those in FIG.

  The printer management unit 1401 executes printer-related operations such as OS printer information acquisition, printer registration, and driver installation. Printer registration is performed using an API provided by the OS. For example, in the case of Windows (registered trademark), it is performed by using AddPrinter of Windows API. The driver is installed by the document management application 300 including an installation package that requires driver installation and executing it. The printer registration process and the printer driver installation process are not particularly specific to the configuration of the document management application 300, and a general configuration can be applied.

FIG. 21 and FIG. 22 are flowcharts illustrating an example of printer confirmation processing during import processing of the document management application 300. This process is executed in the course of the setting information import process of the document management application 300. Specifically, this process is executed in the setting file import process of S824 in FIG. In the following, for the sake of distinction, the printer included in the settings to be imported may be referred to as printer A, and the printer existing at the import destination may be referred to as printer B.
In step S <b> 1501, the setting migration unit 305 sets one setting in the import target list as a processing target, and executes confirmation processing in steps S <b> 1502 to S <b> 1515 regarding the setting.

  In step S1502, the setting migration unit 305 determines whether the setting related to the printer is included in the current processing target setting. Specifically, a list of setting information or setting file names related to the printer, and related setting names (XML attribute names, etc.) of the setting information are held as a table, and it is determined whether or not the corresponding information is satisfied. If it is determined in S1502 that it is related, the process proceeds to S1503, and if it is determined that it is not applicable, the process proceeds to S1516.

In step S <b> 1503, the setting migration unit 305 determines whether the same printer as the processing target setting printer exists in the import destination. Specifically, in step S1502, the printer name (printer queue name) determined to be the relevant setting is referred to, and the printer management unit 307 is inquired to determine whether the printer is registered in the import destination OS. If it is determined that it exists, the process proceeds to S1516. If it is determined that it does not exist, the process proceeds to S1504.
In step S <b> 1504, the setting migration unit 305 refers to the driver name and address information (IP address) of the printer to be processed, and is configured with the same driver name and address information as the import destination OS via the printer management unit 307. Check if a printer exists. If it is determined that a printer having the same configuration is registered in the OS, the process advances to step S1505. If it is determined that it does not exist, the processing proceeds to S1508.

In step S <b> 1505, the setting migration unit 305 instructs the screen display management unit 302 to change the reference of the currently configured printer A to the printer B with the same configuration existing at the import destination, or to add the printer B with the same configuration. A message confirming whether to do so is displayed. Assume that there are “Change reference”, “Add printer”, and “No” buttons as message options.
In step S <b> 1506, the setting transition unit 305 refers to the message button result via the screen display management unit 302. If it is determined that the “reference change” button has been executed, the process advances to step S1507. If it is determined that the “add printer” button or the “no” button has been executed, the process advances to step S1510.
In step S1507, the setting migration unit 305 rewrites and changes the printer name of the current setting information in the setting file to the printer name of the printer determined to have the same configuration in step S1504.

If it is determined in S1504 that there is no printer having the same driver name and address information in the import destination OS, the process advances to S1508.
In step S1508, the setting migration unit 305 instructs the printer management unit 307 to check whether the driver assigned to the printer A having the current target setting is installed in the import destination OS. If it is determined that it is installed, the process advances to step S1509.
In step S1509, the screen display management unit 302 is instructed to display a message asking whether or not to confirm that a printer with the same name is to be added to the import destination. As message options, there are an “add printer” button for adding a printer and a “no” button for not adding a printer.

In step S1510, the setting transition unit 305 refers to the message result in step S1505 or S1509, and proceeds to step S1511 when determining that the “add printer” button has been executed. When determining that the execution of the “no” button has been executed, Go to S1516 without doing anything.
In step S1511, the setting migration unit 305 instructs the printer management unit 307 to register the printer having the same name as the printer A in the current setting information in the import destination OS, and the process advances to step S1516.

If it is determined in S1508 that the driver is not installed, the process advances to S1512.
In step S <b> 1512, the setting migration unit 305 instructs the printer management unit 307 to determine whether the driver assigned to the printer A is bundled with the document management application 300. Specifically, the driver name is referred to, and it is determined whether or not it exists in the list of drivers bundled with the document management application 300. It is assumed that the included driver is a driver that is suitable for cooperation with the document management application 300 and recommended for using the function of the document management application 300. If it is determined that the driver assigned to the printer A is associated with the document management application 300, the process advances to step S1513. On the other hand, if it is determined that they are not compatriots, the process proceeds to S1516.

In step S1513, the setting transition unit 305 instructs the screen display management unit 302 to display a message for confirming whether to add a driver to the OS (and add the printer together). Assume that there are “Yes” button for adding a driver and “No” button for not adding a driver as message options.
In step S1514, the setting transition unit 305 refers to the button result for the message via the screen display management unit 302. If it is determined that the “Yes” button for adding a driver is to be executed, the processing proceeds to step S1515. In step S1511, the printer of the driver is added. On the other hand, if it is determined to execute the “No” button without adding a driver, the process proceeds to S1516 without doing anything.
In step S1515, the setting migration unit 305 instructs the printer management unit 307 to execute driver installation. In step S1511, a printer is added to the OS.

In step S <b> 1516, the setting migration unit 305 imports the setting file of the current target setting to the import destination. Specifically, the setting file in the export file is copied to the import destination.
In step S1517, the setting migration unit 305 determines whether all import targets have been imported. If it is determined that all import targets have been processed, the import process ends and the process flow ends. If there is an unprocessed target, the above-described confirmation processing is executed for the next setting in S1501.

  As described above, according to the present embodiment, even if the setting to be imported is a setting that refers to a setting value other than the setting of an application such as an OS printer, the reference destination in the setting can be changed, or a printer can be imported to the import destination. And drivers can be added. Therefore, according to the present embodiment, it is possible to suppress the occurrence of inconsistency when migrating application setting information.

(Other embodiments)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  As mentioned above, although preferable embodiment of this invention was described, this invention is not limited to these embodiment, A various deformation | transformation and change are possible within the range of the summary.

Claims (18)

An information processing apparatus,
An accepting means for accepting selection of settings to be exported by an application that performs export processing;
Obtaining means for obtaining a related setting related to the accepted setting to be exported;
Adding means for adding the acquired related setting to the export target;
And export means for performing an export process of the setting to be exported,
The information processing apparatus according to claim 1, wherein the acquisition unit acquires the related setting when the setting to be exported received by the receiving unit is a part of an application setting. The information processing apparatus further includes storage means for storing a target setting file and a related setting table in which a setting file related to the target setting file is defined.
The related setting is a setting referred to by the setting to be exported,
The acquisition unit acquires the related setting based on the related setting table stored in the storage unit,
The addition means checks whether the related setting is included in the export target, and adds the related setting to the export target when the related setting is not included in the export target. The information processing apparatus described in 1. The information processing apparatus according to claim 1, wherein the export unit generates an export file including a setting file for the setting to be exported and export information, and performs an export process. The information processing apparatus according to claim 3, wherein the export information includes information indicating whether the setting to be exported is all or a part of the settings of the application. An information processing apparatus,
Accepting means for accepting the setting of the import target for import processing,
An acquisition means for acquiring a related setting related to a setting to be overwritten by the received setting to be imported;
Determining means for determining whether the acquired related setting does not normally operate by the import process;
Display means for displaying a result of determination by the determination means and a selection screen for an import method;
A designation means for accepting a user's selection of the import method and designating the import method;
And import means for performing the import processing of the setting to be imported by a designated import method,
The information processing apparatus according to claim 1, wherein the acquisition unit acquires the related setting when the setting of the import target received by the receiving unit is a part of an application setting. The accepting means accepts the setting of the import target by reading an export file,
The acquisition means determines whether the setting to be imported is a part of the settings of the application based on information on whether the setting of the export target included in the export file is all or a part of the settings of the application. The information processing apparatus according to claim 5, wherein it is determined whether or not. The information processing apparatus further includes storage means for storing a target setting file and a related setting table in which a setting file related to the target setting file is defined.
The related setting is a setting for referring to the setting to be overwritten,
The acquisition unit acquires the related setting based on the related setting table stored in the storage unit,
The determination means confirms whether the related setting is included in the import target, and determines that the related setting does not operate normally by the import process when the related setting is not included in the import target. The information processing apparatus according to claim 5, wherein: When the determination unit determines that the related setting does not operate normally by the import process,
The display means, as an import method, adds an import target setting to an overwritten setting, discards the related setting and replaces the overwritten setting with an import target setting, and overwrites the related setting without discarding it. The information processing apparatus according to claim 5, wherein a method for discarding the setting and replacing the setting with an import target setting is displayed. The information processing apparatus further includes a generation unit that generates a list of settings to be imported received by the reception unit,
The list holds import method information for each setting to be imported,
The import method information is an addition to add the setting to be imported to the setting to be overwritten, or a replacement to discard the setting to be overwritten and replace it with a setting to be imported.
When the list is generated by the generation means, the import method information of all the settings to be imported is replacement,
9. The specification means, when the received import method is a method of adding a setting to be imported to a setting to be overwritten, additionally specifies the import method information in the list. The information processing apparatus described in 1. If the importing method accepted by the specifying unit is a method of discarding the related setting and replacing the overwritten setting with the setting to be imported, the importing unit discards the related setting and then performs the import process. The information processing apparatus according to claim 8, wherein the information processing apparatus is performed. The accepting unit accepts a setting selected as the import target for performing the import process from a setting read from an export file,
The information processing apparatus further includes an additional unit that acquires a related setting related to the setting of the import target, and adds the related setting to the import target when the related setting is not included in the import target. The information processing apparatus according to claim 5, comprising: an information processing apparatus according to claim 5. The information processing apparatus further includes:
A determination unit configured to determine whether the image processing apparatus includes an image processing apparatus referred to by the import target setting when the import target setting is a setting referring to the image processing apparatus;
Changing means for rewriting the setting of the import target for the image processing apparatus referred to by the setting of the import target;
Registration means for registering the image processing apparatus in the information processing apparatus,
Although there is no image processing apparatus that the determination means refers to in the information processing apparatus, the image processing apparatus that has the same IP address as the image processing apparatus, the printer driver, and the reference to which the setting to be imported is referred to. 12. The apparatus according to claim 5, wherein if it is determined that the image processing apparatus is present, the changing unit rewrites the image processing apparatus referred to by the setting to be imported into an image processing apparatus having the same IP address as that of the driver. The information processing apparatus according to item 1. When the determination unit determines that there is no image processing apparatus referred to by the setting to be imported in the information processing apparatus, the registration unit determines that the information if the printer driver exists in the information processing apparatus. The information processing apparatus according to claim 12, wherein when the image processing apparatus is added to a processing apparatus and a printer driver does not exist, the printer driver and the image processing apparatus are added to the information processing apparatus. A data migration system having a first information processing apparatus and a second information processing apparatus,
The first information processing apparatus includes:
First receiving means for receiving selection of a setting to be exported by an application that performs export processing;
First acquisition means for acquiring a first related setting related to the accepted setting to be exported;
Adding means for adding the acquired first related setting to the export target;
And export means for performing an export process of the setting to be exported,
The second information processing apparatus
A second accepting unit for accepting an import target setting for import processing;
Second acquisition means for acquiring a second related setting related to the setting overwritten by the received setting to be imported;
Determining means for determining whether or not the acquired second related setting is not normally operated by the import process;
Display means for displaying a result of determination by the determination means and a selection screen for an import method;
A designation means for accepting a user's selection of the import method and designating the import method;
And import means for performing the import processing of the setting to be imported by a designated import method,
The first acquisition unit acquires the first related setting when the setting to be exported received by the first reception unit is a part of the application setting,
The second acquisition unit acquires the second related setting when the setting of the import target received by the second reception unit is a part of the setting of the application. Migration system. A control method for a data migration system having a first information processing apparatus that performs an export process and a second information processing apparatus that performs an import process,
The step of performing the export process includes:
A first accepting step for accepting selection of a setting to be exported by an application that performs the export process;
A first acquisition step of acquiring a first related setting related to the accepted setting to be exported;
An additional step of adding the acquired first related setting to the export target;
An export process for performing an export process of the setting to be exported,
In the first acquisition step, the first related setting is acquired when the setting to be exported received in the first reception step is a part of the setting of the application. Control method. The step of performing the import process includes:
A second accepting step of accepting an import target setting for performing the import process;
A second acquisition step of acquiring a second related setting related to a setting to be overwritten by the received setting to be imported;
A determination step of determining whether or not the acquired second related setting is not normally operated by the import process;
A display step for displaying a result of determination in the determination step and a selection screen for an import method;
Accepting user selection for the import method and specifying the import method; and
An import process for performing the import processing of the setting to be imported by a designated import method,
In the second acquisition step, the second related setting is acquired when the setting of the import target received in the second reception step is a part of an application setting. Item 17. The control method according to Item 16.   A program that causes a computer to function as each unit of the information processing apparatus according to any one of claims 1 to 4.   A program that causes a computer to function as each unit of the information processing apparatus according to any one of claims 5 to 13.

Images