Undo-processing execution program, recording medium storing undo-processing execution program, and undo-processing execution method

Abstract

To provide an UNDO processing execution program for making a computer execute UNDO processing for efficiently returning tabular data which can be updated by an arbitrary operation to a state before update.SOLUTION: The UNDO processing execution program 10 includes a recording step for recording pre-update information when the work shift table 30 is updated by manual operation, an UNDO processing reception step for receiving a cancellation request, and an UNDO processing execution step for executing restoration operation corresponding to the pre-update information on the basis of the pre-update information and the cancellation request. In the recording step, when the first information is input to the input region 31 by the manual operation, the pre-update information of the input region 31 to which the first information is input is recorded, and when the second information corresponding to the first information is input to another input region 31 by the auto-complete operation, the pre-update information of the input region 31 to which the second information is input is recorded together with the pre-update information of the input region 31 to which the first information is input.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an UNDO processing execution program for causing a computer to execute UNDO processing that returns tabular data that can be updated by any operation to the state before the update, a recording medium on which this UNDO processing execution program is recorded, and an UNDO processing execution method. [Background technology]

[0002] Conventionally, some software that processes or manipulates various data through operations such as inputting text or images has been equipped with an UNDO function that undoes the most recent operation and returns the data to the state before the update. Generally, the UNDO function records the details of operations performed on the data in chronological order as an operation history, and when the UNDO function is executed, it does not undo the operation that was the target of the UNDO function execution, but rather executes a restoration operation to return the data to the state immediately before the operation, based on the details of the operation recorded in the operation history.

[0003] Conventional UNDO functions record the details of operations performed on data in an operation history for each operation. Therefore, if an operator wants to undo all operations performed, the operator must repeatedly execute the UNDO function until all operations performed up to that point appear to have been undone. Patent Document 1, therefore, proposes a computer system equipped with an undo function that can undo all commands executed up to that point at once. The information processing means of the computer system in Patent Document 1 has an undo function that allows the operator to select either "all the way (all commands)" or "last stored." When "all the way (all commands)" is selected, the undo function is automatically executed repeatedly from the command (operation) most recently stored in the storage means to the command (operation) first stored in the storage means. On the other hand, when "last stored" is selected, the undo function is executed only for the command (operation) most recently stored in the storage means. Therefore, even if an operator wants to undo all operations performed up to that point, the operator does not need to repeatedly execute the undo function; all operations up to that point can be undone by executing the undo function once. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-310116 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, some software and applications (hereinafter, "software and applications" are referred to as "software, etc.") that handle various data are configured to automatically execute other operations in response to specific operations performed by a worker. For example, when creating a work shift schedule, there is a constraint that the day after a "night shift" must always be designated as "after a night shift." In some software, such as dedicated spreadsheet software that assists in creating work shift schedules, when a "night shift" work type is entered, the software is configured to automatically enter a "night shift after a night shift" work type the day after the "night shift" work type was entered. In such a case, if a worker wishes to undo the operation of entering the "night shift" work type and performs an UNDO process, conventional UNDO processes only undo the operation performed immediately before the UNDO process was performed—for example, in the above case, the operation of automatically entering the "night shift after a night shift" work type—and not the entry of the "night shift" work type that the worker originally wanted to undo. As a result, the UNDO process intended by the worker cannot be performed.

[0006] Therefore, the present invention aims to provide an UNDO processing execution program for causing a computer to execute UNDO processing that can efficiently return tabular data that can be updated by any operation to the state before the update, a recording medium on which this UNDO processing execution program is recorded, and an UNDO processing execution method. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, an UNDO processing execution program according to the present invention is for causing a computer to execute UNDO processing for returning tabular data that can be updated by any operation to a state before the update, and includes a recording step for recording pre-update information that is information indicating the state of the data immediately before the update when the data is updated by a manual operation that is an operation performed by an operator, an UNDO processing reception step for receiving a cancellation request that requests cancellation of the manual operation, and an operation for returning the data to a state before the update based on the pre-update information recorded by the recording step and the cancellation request received by the UNDO processing reception step. and an UNDO processing execution step of executing a restoration operation corresponding to the pre-update information, wherein the recording step, when first information is input into the data input area by the manual operation, records the pre-update information of the input area into which the first information is input, and, when, after the first information is input by the manual operation, the second information is input into an input area different from the input area into which the first information is input by an auto-completion operation that automatically inputs second information corresponding to the first information, records the pre-update information of the input area into which the second information is input together with the pre-update information of the input area into which the first information is input.

[0008] In the above invention, the data may be a work shift schedule, the first information may include a work type, and the second information may include another work type corresponding to the work type entered in the input area as the first information.

[0009] In the above invention, the second information may include supplemental information for the work type input in the input area as the first information.

[0010] In the above invention, when the first information is input collectively into a plurality of the input areas by the manual operation, the recording step may record the pre-update information of each of the input areas into which the first information is input, and may also collectively record the pre-update information of the input areas into which the second information corresponding to each of the first information is input.

[0011] In the above invention, the manual operation may include a sorting operation, which is an operation for rearranging the values ​​input into the input area according to a predetermined criterion, and / or a filtering operation, which is an operation for narrowing down the values ​​input into the input area according to a predetermined condition.

[0012] In the above invention, the manual operation may include a background color change operation, which is the operation for changing the background color of the input area.

[0013] In the above invention, the number of undo requests that can be consecutively accepted by the UNDO process accepting step may be limited to a predetermined number.

[0014] The UNDO process execution program may be recorded on a computer-readable recording medium.

[0015] In order to solve the above-mentioned problems, the present invention provides an UNDO processing execution method for a computer to execute UNDO processing for returning tabular data that can be updated by any operation to a state before the update, the UNDO processing execution method including: a recording step for recording pre-update information that indicates the state of the data immediately before the update when the data is updated by a manual operation that is an operation performed by an operator; an UNDO processing reception step for receiving a cancellation request that requests cancellation of the manual operation; and an operation for returning the data to the state before the update based on the pre-update information recorded by the recording step and the cancellation request received by the UNDO processing reception step. and an UNDO processing execution step for executing a restoration operation corresponding to the pre-update information, wherein the recording step, when first information is input into the data input area by the manual operation, records the pre-update information of the input area into which the first information is input, and, when, after the first information is input by the manual operation, the second information is input into an input area other than the input area into which the first information is input by an auto-completion operation that automatically inputs second information corresponding to the first information, records the pre-update information of the input area into which the second information is input together with the pre-update information of the input area into which the first information is input. [Effects of the Invention]

[0016] According to the UNDO processing execution program of the present invention, when data is updated by a manual operation by an operator, the program includes a recording step of recording pre-update information, which is information indicating the status of the data immediately before the update, an UNDO processing receiving step of receiving a cancellation request to cancel the manual operation, and an UNDO processing execution step of executing a restoration operation corresponding to the pre-update information, which is an operation for returning the data to the state before the update, based on the pre-update information recorded by the recording step and the cancellation request received by the UNDO processing receiving step.The recording step records the pre-update information of the input field into which the first information is input when first information is input by manual operation, and when second information is input into an input field different from the input field into which the first information is input by an auto-completion operation that automatically inputs second information corresponding to the first information after the first information is input by manual operation, the recording step records the pre-update information of the input field into which the second information is input together with the pre-update information of the input field into which the first information is input. In this way, even when second information is automatically input in conjunction with the input of first information, the pre-update information of the first input area into which the first information is input and the pre-update information of the second input area into which the second information is input are recorded together, so that in the UNDO processing execution step, restoration operations corresponding to the pre-update information can be executed together based on the pre-update information of the first input area and the pre-update information of the second input area that are recorded together. Therefore, even when an automatic completion operation is performed in conjunction with a manual operation after the operator performs a manual operation, data can be efficiently restored to the state before the manual operation by executing a single UNDO processing. Furthermore, because the operation contents of the manual operation and the operation contents of the automatic completion operation can be targeted together in a single UNDO processing, the UNDO processing intended by the operator can be executed.

[0017] According to the UNDO processing execution program of the present invention, the data is a work shift schedule, the first information includes a work type, and the second information includes another work type corresponding to the work type entered in the input area as the first information. Therefore, when a work type is manually entered as first information into an input field of the work shift schedule by a worker, another work type corresponding to the work type entered as first information is automatically entered into another input field of the work shift schedule by an auto-completion operation. In this way, in the UNDO processing execution step, it is possible to cancel the input of these work types all at once by executing a single UNDO process, and return the work shift schedule to the state before it was updated.

[0018] According to the UNDO process execution program of the present invention, the second information includes supplemental information on the work type input in the input area as the first information. Therefore, even if supplementary information for the work type entered as the first information is entered through an automatic completion operation, the entry of both the work type and the supplementary information can be canceled at once by executing a single UNDO process, and the work shift schedule can be returned to the state it was in before the update.

[0019] According to the UNDO processing execution program of the present invention, when first information is input collectively into multiple input areas by manual operation, the recording step records pre-update information for each input area into which the first information is input, and also collectively records pre-update information for input areas into which second information corresponding to each first information is input. Therefore, even when the first information is input into multiple input fields collectively by manual operation, the pre-update information of each input field into which the first information is input and the pre-update information of the input field into which the second information is input can be recorded collectively, and by executing a single UNDO process, the first information and second information input into the multiple input fields can be canceled collectively, thereby efficiently returning the work shift schedule to its pre-update state.

[0020] According to the UNDO processing execution program of the present invention, the manual operation includes a sorting operation, which is an operation for rearranging values ​​entered in the input field according to predetermined criteria, and / or a filtering operation, which is an operation for narrowing down the values ​​entered in the input field according to predetermined conditions. Therefore, sorting and narrowing down of values ​​entered in the input area can also be subject to UNDO processing.

[0021] According to the UNDO process execution program of the present invention, the manual operation includes a background color change operation, which is an operation for changing the background color of the input area. Therefore, changes to the background color of the input area can also be subject to UNDO processing.

[0022] According to the UNDO processing execution program of the present invention, the number of undo requests that can be consecutively accepted by the UNDO processing accepting step is limited to a predetermined number. In this way, since the number of cancellation requests that can be accepted is limited to a predetermined number, the pre-update information recorded by the recording step can also be limited to match the number of the predetermined number, thereby reducing the capacity of the recording area for recording the pre-update information.

[0023] Furthermore, according to the recording medium on which the UNDO processing execution program of the present invention is recorded and the UNDO processing execution method of the present invention, it is possible to achieve the same effects as the UNDO processing execution program described above. [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 is a block diagram showing an outline of an UNDO processing execution program according to an embodiment of the present invention, a work shift creation system in which this UNDO processing execution program is incorporated, and a computer on which the UNDO processing execution program and the work shift creation system are installed. [Figure 2] This figure shows a portion of a work shift schedule created by a work shift creation system incorporating an UNDO processing execution program according to an embodiment of the present invention, where (a) shows the state before the work type is deleted, and (b) shows the state after the work type is deleted. [Figure 3] (a) is an explanatory diagram for explaining supplementary information in the UNDO processing execution program according to an embodiment of the present invention, and (b) is an explanatory diagram for explaining the ancillary work type in the UNDO processing execution program according to an embodiment of the present invention. [Figure 4] An explanatory diagram to explain the relationship between the first information and the second information in the UNDO processing execution program of an embodiment of the present invention, where (a) shows the state before the work type is changed and (b) shows the state after the work type is changed. [Figure 5] 10 is a flowchart showing the flow of an UNDO recording process in a recording step of an UNDO processing execution program according to the embodiment of the present invention. [Figure 6] 10 is a flowchart showing the flow of an UNDO execution process in an UNDO process execution step of an UNDO process execution program according to an embodiment of the present invention. [Figure 7] 10A and 10B are explanatory diagrams for explaining the NULL information input confirmation function in a work shift creation system incorporating an UNDO processing execution program according to an embodiment of the present invention, where (a) shows the state before the confirmation display is displayed, and (b) shows the state after the confirmation display is displayed. [Figure 8] 10A and 10B are explanatory diagrams for explaining the case where multiple input areas are selected and an input operation is performed in an UNDO processing execution program according to an embodiment of the present invention, where (a) shows the state before the operation is performed, (b) shows the state in which a confirmation message is displayed after the operation is performed, and (c) shows the state after the operation is performed. DETAILED DESCRIPTION OF THE INVENTION

[0025] Next, an embodiment of the UNDO processing execution program according to the present invention will be described with reference to the accompanying drawings. In the following, an example will be described in which the UNDO processing execution program is incorporated into a work shift creation system, which is software for creating a work shift schedule, which is tabular data.

[0026] FIG. 1 is a schematic diagram showing the configuration of a computer 1 for executing an UNDO processing execution program 10 and a work shift creation system 20. The computer 1 is an information processing terminal such as a personal computer or a tablet terminal. The computer 1 includes a control unit 2 that controls various functions of the computer 1, a display unit 3 that outputs and displays various information on a display device 2a such as a monitor, an input unit 4 that accepts input via an input device 4a such as a keyboard, a mouse, or a touch panel provided on the surface of the display, and a communication unit 5 that connects the computer 1 to a network (not shown) such as the Internet to communicate with external devices (not shown) other than the computer 1. The control unit 2 is a microcomputer that includes a CPU (Central Processing Unit), a ROM (Read Only Memory), which is a storage device that stores electronic data such as programs for operating the CPU and from which the stored electronic data can be read, and a RAM (Random Access Memory), which is a storage device that can both read and write electronic data.

[0027] The UNDO processing execution program 10 and the work shift creation system 20 are installed and used in the computer 1 configured as described above. Specifically, the work shift creation system 20 is software or the like that assists in the creation of a work shift schedule 30 (FIGS. 2(a) and 2(b)), which is tabular data, and the UNDO processing execution program 10 is a program that is installed and used in the computer 1 as part of the work shift creation system 20. When an operator makes changes to the work shift schedule 30 created by the work shift creation system 20, the UNDO processing execution program 10 causes the computer 1 to execute UNDO processing that returns the work shift schedule 30 to the state before the changes were made, i.e., the state before the work shift schedule 30 was updated. The UNDO processing execution program 10 and the work shift creation system 20 are not limited to being installed on the computer 1. For example, they may be configured as programs or software that are recorded on a recording device, such as a hard disk drive (HDD) or solid state drive (SSD) capable of reading and writing electronic information, external to the computer 1, or on a recording medium, such as a memory card or optical disk capable of reading and writing electronic information, and can be called up when needed. Furthermore, the UNDO processing execution program 10 and the work shift creation system 20 may be realized as programs or software that function as SaaS (Software as a Service) provided by an ASP (Application Service Provider) without being recorded on the computer 1, a recording device, or a recording medium. In this case, the UNDO processing execution program 10 and the work shift creation system 20 are provided as a cloud service via a network. Furthermore, the UNDO processing execution program 10 may be configured as a program independent of the work shift creation system 20.

[0028] Figures 2(a) and 2(b) show a portion of a work shift schedule 30 created by the work shift creation system 20. Note that in Figures 2(a), 2(b), 4(a), 4(b), 7(a), 7(b), and 8(a) to 8(c) shown below, in order to make it easier to understand the operations and update statuses performed by the UNDO processing execution program 10 and the work shift creation system 20, only a portion of the shifts of a specific employee (name: Tetsudo Taro) is shown, and the rest are omitted.

[0029] The work shift creation system 20 automatically creates a work shift schedule 30 that satisfies predetermined conditions, such as work shift creation rules established by work regulations or internal agreements, based on the rules. The work shift creation system 30 also displays the work shift schedule 30 on the display unit 3 of the computer 1 and accepts manual operations, which are operations performed manually by workers via the input unit 4, to assist in changes to the work shift schedule 30. The work shift schedule 30 created by the work shift creation system 20 has multiple input areas 31 divided into a grid. Various information can be stored in each input area 31 and updated by any operation. The input area 31 of the work shift schedule 30 includes a first input area 32 arranged in a single row and a second input area 33 arranged in a single row below the first input area 32. The details of one person's work shift are displayed in the two-row input area 31 consisting of the first input area 32 and the second input area 33. The first input area 32 is used to input the work type as the first information input by manual operation, and the work type (ancillary work type described below) as the second information corresponding to the first information, while the second input area 33 is used to input supplementary information as the second information corresponding to the first information.

[0030] The first information includes work types and NULL information for deleting work types. Work types include "day shift," "day shift A," "afternoon," "day shift B," and "public holiday." "Day shift" refers to a regular day shift, "day shift A" refers to the first day of a day shift that requires work over two consecutive days, and "afternoon" refers to a day shift that is set the day after "day shift A." "Day shift B" refers to a day shift with longer working hours than regular day shifts, and "public holiday" refers to a holiday stipulated by work regulations. NULL information is information that indicates that the input area 31 is empty, and is used in the work shift creation system 20 and the UNDO processing execution program 10 to overwrite and delete input information, for example, the input work type. Note that the operation of inputting NULL information corresponds to a "NULL input operation." The second information includes ancillary work types, which are different work types corresponding to the work type manually input into the first input area 32 as the first information, supplementary information corresponding to the work type manually input into the first input area 32 as the first information, and NULL information for deleting work types, ancillary work types, supplementary information, etc. that are no longer necessary due to the input of the first information. An additional work type is a special work type that must be set up in conjunction with a specific work type according to the rules for creating work shifts. Among the work types mentioned above, the "morning" work type is an additional work type that corresponds to the "day shift A" work type.

[0031] In the work shift creation system 20, when "Day shift A" and "Dawn" are entered side by side across dates (FIG. 2(a)), to delete "Day shift A" or "Dawn," NULL information is manually entered as the first information in either or both of the first input areas 32 storing "Day shift A" and "Dawn." Here, when NULL information is entered in either the first input area 32 storing "Day shift A" or the first input area 32 storing "Dawn," the work shift creation system 20 is configured so that, in conjunction with the deletion of either "Day shift A" or "Dawn," the other is also deleted (NULL information is entered) as shown in FIG. 2(b). In this case, for example, if NULL information is manually entered as the first information to delete the work type of "Day shift A," NULL information is automatically entered as the second information to delete the unnecessary work type of "Dawn" in conjunction with this manual operation. At this time, the operation of automatically inputting the NULL information, which is the second information, by the work shift creation system 20 corresponds to an automatic completion operation.

[0032] Furthermore, in the work shift creation system 20, as described above, if "Day shift A" and "morning" are deleted from a state in which they are entered side by side across dates, and then UNDO processing is performed in the UNDO processing execution program 10 of this embodiment, as shown in FIG. 2(a), a single UNDO process cancels the deletion of both "Day shift A" and "morning," and the work shift schedule 30 is returned to its pre-update state in which both "Day shift A" and "morning" were entered again in the first input field 32. In this way, when there is an automatic completion operation, which is an operation performed in conjunction with a manual operation, the UNDO processing execution program 10 targets not only the manual operation content but also the automatic completion operation content together in the UNDO process to return the work shift schedule 30 to its pre-update state.

[0033] FIG. 3(a) is an explanatory diagram for explaining the supplementary information of the second information. Supplementary information is information that supplements the content of the work type. For example, it is information such as "Annual Leave" or "Arrangements" displayed in the second input area 33 in FIG. 3(a), or information such as comments 34 added to the second input area 33, and each supplementary information corresponds to a work type. Specifically, for example, "Annual Leave" displayed in the second input area 33 for the "2nd" column indicates that the "Public Holiday" work type displayed in the first input area 32 for the "2nd" column is annual paid leave applied for by the company. Furthermore, "Arrangements" displayed in the second input area 33 for the "3rd" column indicates that the "Day Shift A" work type displayed in the first input area 32 for the "3rd" column is a shift designated by instructions from the company. Comments 34 indicate detailed information such as working hours for each shift type entered in first input area 32, and are added to second input area 33. For example, in second input area 33 for the "3rd" column, detailed information on working hours for "Day shift A" is added as "Work start: 07:00, Work end: 17:00," corresponding to the "Day shift A" shift type entered in first input area 32 for the "3rd" column. Note that, as shown in FIG. 3(a), when "Day shift A" entered in first input area 32 for the "3rd" column is changed to "Day shift B," detailed information on working hours for "Day shift B" is added as new comment 34 corresponding to "Day shift B," as "Work start: 09:00, Work end: 20:00." In this case, "Day shift B," which is used to change "Day shift A," corresponds to the first information, and comment 34 corresponding to "Day shift B" corresponds to the second information. The second information such as the type of auxiliary work and supplementary information is not limited to the above, and can be set arbitrarily as long as it corresponds to the first information.

[0034] In the work shift creation system 20, values ​​such as a work type as first information or NULL information for deleting a work type can be manually input into the first input area 32. Therefore, by manually inputting a work type or NULL information, a worker can adjust the shift on the work shift schedule 30 by performing operations such as inputting, changing, or deleting a work type. Furthermore, an auxiliary work type or NULL information is input into the first input area 32 as second information corresponding to the first information by an automatic completion operation, which is an operation automatically performed by the work shift creation system 20 in response to a manual operation. Note that the first information input by manual operation may also be input by a pasting operation such as copy and paste, in which a work type stored in another first input area 32 is copied and pasted. On the other hand, the second input area 33 is used to input supplementary information or NULL information corresponding to the work type manually input into the first input area 32, which is second information corresponding to the first information, and manual input, modification, deletion, etc. of supplementary information is restricted. In this way, the work type and NULL information are manually input as the first information, or the auxiliary work type and NULL information are automatically input as the second information by an automatic completion operation into the first input area 32. Meanwhile, the second input area 33 is automatically input with an automatic completion operation, such as supplementary information and NULL information corresponding to the work type and NULL information input as the first information into the first input area 32. Among the automatic completion operations automatically performed by the work shift creation system 20, the operation of inputting the auxiliary work type as second information into the first input area 32 corresponds to the "auxiliary work type input operation", and the operation of inputting supplementary information corresponding to the work type manually input into the first input area 32 as second information into the second input area 33 corresponds to the "supplementary information input operation".

[0035] As described above, the work shift creation system 20 is set up so that when a change is made (updated) by manual operation to the automatically created work shift schedule 30, the creation of the work shift is assisted by an automatic completion operation corresponding to the manual operation. In other words, in the work shift creation system 20, when there is second information (ancillary work type, supplementary information, etc.) corresponding to the first information (work type, etc.) input by manual operation, the second information is automatically input, and when there is a work type, ancillary work type, or supplementary information that is no longer necessary corresponding to the first information (work type, etc.) input by manual operation, NULL information is automatically input. For example, as shown in the upper part of Figure 3(b), if the work type "Shift A" is manually entered as the first information in the first input area 32 of the "1st" column, the work type "morning", which is an auxiliary work type corresponding to the work type "day shift A", is automatically entered as the second information in the first input area 32 of the "2nd" column of the following day by an auto-completion operation. Also, as shown in the lower part of Figure 3(b), if either "Shift A" or "morning" entered in the first input area 32 is deleted, the other is automatically deleted. Specifically, in order to delete the work type "Shift A" entered in the first input area 32 of the "1st" column, or the work type "morning" entered in the first input area 32 of the "2nd" column, when NULL information is entered as the first information in the first input area 32 of either the "1st" column or the "2nd" column, NULL information is automatically entered as the second information in the other first input area 32 by an auto-completion operation, and both the "Shift A" and "morning" work types are deleted.

[0036] For example, as shown in FIG. 3(a), when "Day shift B" is manually entered as the first information in the first input area 32, where "Day shift A" in the "3rd day" column was entered, the "Arrangements" (supplementary information) displayed in the second input area 33 is deleted. This is because the change from "Day shift A" to "Day shift B" was made manually by the worker and not by instructions from the company. At this time, NULL information is automatically entered as the second information in the second input area 33, where "Arrangements" in the "3rd day" column was stored, through an auto-completion operation. Furthermore, when the work type in the first input area 32 is changed from "Day shift A" to "Day shift B," the comment 34 added to the second input area 33 is also changed to correspond to "Day shift B," as described above.

[0037] Furthermore, for example, as shown in Figure 4(a), when the work type "Shift A" is stored in the first input area 32 of the "17th" column, the work type "Day shift A" is stored in the first input area 32 of the "18th" column, and the work type "Public holiday" is stored in the first input area 32 of the "19th" column, and when the work type "Day shift A" is manually entered as the first information in the first input area 32 of the "18th" column as shown in Figure 4(b), the work type "Day shift A" is automatically entered as the second information in the first input area 32 of the "19th" column for the following day by an auto-completion operation, and NULL information is automatically entered as the second information in the first input area 32 of the "17th" column for the previous day by an auto-completion operation. In this case, the work type "morning," which is an auxiliary work type corresponding to the work type of "day shift A," is automatically entered as the second information in the first input area 32 of the "19th" column, and furthermore, NULL information is automatically entered as the second information in the first input area 32 of the "17th" column to delete "day shift A" from the first input area 32 of the "17th" column, which has become unnecessary due to the entry of the first information ("day shift A") in the first input area 32 of the "18th" column. Note that at this time, the NULL information automatically entered to delete the work type of "day shift A" is NULL information serving as second information corresponding to the first information, "day shift A." In the work shift creation system 20, if a work type of "Day shift A" is manually entered into the first input field 32 of the "18th" column, and then a work type of "morning" is entered into the first input field 32 of the "19th" column for the following day by an automatic completion operation, and then NULL information is entered into the first input field 32 of the "17th" column for the previous day by an automatic completion operation, and then UNDO processing is executed in the UNDO processing execution program 10 of this embodiment, the input of "Day shift A," the input of "morning," and the input of NULL information are all canceled by a single UNDO processing, and the work shift schedule 30 can be restored to the state before the update shown in Figure 4(a). The UNDO execution processing for executing such UNDO processing will be described later.

[0038] Here, operations performed in the work shift scheduling system 20, such as manual operations and automatic completion operations (such as inputting ancillary work types and inputting supplemental information), are each performed as a single operation. Therefore, in a conventional UNDO process that undoes the most recent operation in the reverse order of the operations performed, only operations unintended by the worker may be subject to the UNDO process. For example, in the relationship between "Day Shift A" and "Dawn" shown in FIG. 3(b), when "Work A" is manually entered into the first input field 32 of the "1st" column, "Dawn" is automatically entered into the first input field 32 of the "2nd" column through the automatic completion operation. Therefore, even if a worker performs UNDO processing to cancel the manual entry of "Day Shift A" and return to the state before the update, the previous automatic completion operation of automatically entering "Dawn" into the first input field 32 of the "2nd" column would be subject to the undo process. Therefore, in a conventional UNDO process, only the most recent automatic completion operation of automatically entering "Dawn" into the first input field 32 of the "2nd" column would be deleted, and only the work type "Dawn" entered into the work shift schedule 30 would be deleted. In this case, to cancel the input for "Day Shift A" and return to the state before the update, two UNDO processes must be executed in succession, which is not the behavior the worker intended.

[0039] For example, if "Shift A" entered in the first input field 32 was set by company instruction and the supplemental information "Arrangements" is already stored in the second input field 33, and a manual operation is performed to change "Shift A" to "Shift B," after the manual operation of entering "Shift B" as the first information in the first input field 32, an auto-completion operation is automatically performed to enter NULL information as the second information in the second input field 33 to delete the supplemental information "Arrangements." In this case, conventional UNDO processing would only undo the auto-completion operation of entering NULL information in the second input field 33, and the operation of changing "Shift A" to "Shift B" would not be undone, resulting in a state in which "Day Shift B" and "Arrangements" are paired together. In this case, conventional UNDO processing not only fails to produce the behavior intended by the worker, but also may result in a work shift that is not anticipated by the work shift creation rules. Therefore, the UNDO processing execution program 10 executes UNDO processing as follows.

[0040] The UNDO process execution program 10 creates an operation list in response to a manual operation by an operator. The operation list records pre-update information, which is information indicating the status of the work shift schedule 30 immediately before the update, when the work shift schedule 30 is updated by manual operation or automatic completion operation in the work shift creation system 20. The operation list is created each time a manual operation is performed, and records the details of the performed operation in chronological order. For example, when first information is manually input into the first input area 32, the operation list first records pre-update information for the first input area 32 into which the first information is input. Thereafter, if, after the first information is manually input, second information corresponding to the first information is input into another input area 31 (the first input area 32 or the second input area 33) by automatic completion operation, the pre-update information for the first input area 32 or the second input area 33 into which the second information is input is recorded together with the pre-update information for the first input area 32 into which the first information is input in the operation list.

[0041] Therefore, for example, when first information is input by manual operation and there is no second information corresponding to the first information, the pre-update information of the first input area 32 that is updated by the manual operation of inputting the first information is recorded in one operation list. On the other hand, when there is second information that corresponds to the first information input by manual operation, the pre-update information of the first input area 32 that is updated by the manual operation of inputting the first information and the pre-update information of either or both of the first input area 32 and the second input area 33 that is updated by the auto-completion operation of inputting the second information are recorded together in one operation list. In other words, in the UNDO processing execution program 10, when first information is entered into the first input area 32 by manual operation in the operation list and second information corresponding to this first information is automatically entered into either or both of the first input area 32 or the second input area 33 by automatic completion operation, the manual operation and the automatic completion operation are regarded as one operation, and the pre-update information of the first input area 32 into which the first information is entered and the pre-update information of either or both of the first input area 32 or the second input area 33 into which the second information is entered are recorded together in one operation list. On the other hand, if the manual operation performed by the worker is an operation other than an input operation for inputting the first information, such as a sorting operation, a filtering operation, a background color change operation, or a comment addition operation, which will be described later, pre-update information indicating the status of the work shift schedule 30 immediately before it is updated by performing those operations is recorded in a single operation list. A specific example of the pre-update information will be described in detail in the description of the recording step below.

[0042] Here, manual operations other than the operation of inputting first information performed by a worker include, for example, a sorting operation for rearranging values ​​input into the input area 31 according to a predetermined criterion, a filtering operation for narrowing down the values ​​input into the input area 31 according to a predetermined condition, a background color change operation for changing the background color of the input area 31, and a comment addition operation for adding a comment 34 to the input area 31. When these operations are performed manually, the operation list records pre-update information indicating the status of the work shift table 30 immediately before it is updated by the sorting operation, pre-update information indicating the status of the work shift table 30 immediately before it is updated by the filtering operation, pre-update information indicating the status of the work shift table 30 immediately before it is updated by the background color change operation, and pre-update information indicating the status of the work shift table 30 immediately before it is updated by the comment addition operation. Note that the input values ​​include all values ​​input into the input area 31 of the work shift table 30, such as name, job title, employee number, and group, in addition to the first information and second information. Furthermore, the manual operations are not limited to the above-mentioned operations, and may include other operations performed by the worker in the work shift creation system 20.

[0043] Next, when the UNDO processing execution program 10 receives a cancellation request requesting cancellation of a manual operation, it executes a restoration operation corresponding to the pre-update information, which is an operation for returning the work shift schedule 30 to its pre-update state based on the pre-update information recorded in the operation list. At this time, in the UNDO processing execution step that performs the restoration operation, if multiple pieces of pre-update information are recorded together in one operation list, restoration operations corresponding to all of the pre-update information in the operation list are executed. In this way, in the UNDO processing using the UNDO processing execution program 10, not only updates made by manual operations but also updates made by automatic completion operations that were automatically executed in conjunction with the manual operations can be undone in a single UNDO processing operation.

[0044] Therefore, the UNDO processing execution program 10 has a recording step that records pre-update information indicating the status of the work shift schedule 30 immediately before the update in an operation list when the work shift schedule 30 is updated by manual operation as described above; an UNDO processing reception step that receives a cancellation request requesting cancellation of the manual operation; and an UNDO processing execution step that executes a restoration operation corresponding to the pre-update information, which is an operation for returning the work shift schedule 30 to the state before the update, based on the pre-update information recorded in the recording step and the cancellation request received in the UNDO processing reception step.

[0045] In the recording step, when first information (e.g., work type) is manually input into the first input area 32 of the input area 31, the pre-update information of the first input area 32 into which the first information is input is recorded in the operation list. Furthermore, in the recording step, if, after the first information is input by manual operation, second information (information such as ancillary work type or supplementary information) corresponding to the first information input by manual operation is automatically input by an auto-completion operation into an input area 31 (either the other first input area 32 or the second input area 33, or both) other than the first input area 32 into which the first information is input, the pre-update information of either or both of the first input area 32 or the second input area 33 into which the second information is input is recorded together with the pre-update information of the first input area 32 into which the first information is input in the operation list. In this way, in the operation list when the first information is input by manual operation, if an auto-completion operation is not performed, the pre-update information of the first input area 32 immediately before it is updated by manual operation is recorded, whereas in the case where an auto-completion operation is performed, the pre-update information of the first input area 32 immediately before it is updated by manual operation and the pre-update information of either or both of the first input area 32 or the second input area 33 immediately before it is updated by auto-completion operation are recorded together.

[0046] Furthermore, in the recording step, the operation lists recorded as described above are further organized into a list and recorded as a history list. A history list is a list in which each operation list is regarded as a single operation and recorded in the order of manual operations performed by the worker, and in which the operation lists in which pre-update information has been recorded are further recorded in chronological order. In the UNDO processing execution step described below, the operation lists recorded in this history list are referenced in the reverse order of the operations, and a restoration operation corresponding to the pre-update information recorded in the referenced operation list is executed. In the recording step, creation of operation lists and recording of the created operation lists in the history list continue until the UNDO processing execution step executes the UNDO execution process, in other words, until a cancellation request is accepted in the UNDO processing acceptance step.

[0047] The UNDO recording process from creating an operation list in the recording step to recording it in the history list will be specifically described below with reference to Fig. 5. Fig. 5 is a flowchart showing the flow of the UNDO recording process. In the following description, the "input area" will also be referred to as a "cell." First, in the UNDO recording process in the recording step, it is determined whether or not a cell (for example, the first input area 32 of the input area 31) has been selected by a manual operation by the worker (S101). If no cell has been selected, the process waits until cell selection is detected. If a cell has been selected, it is determined whether or not a manual operation other than an input operation on the cell, such as a sort operation, a filter operation, a background color change operation, or a comment addition operation, has been performed (S102). If a manual operation other than the above-mentioned input operation has been performed, pre-update information indicating the status of the work shift schedule 30 immediately before the manual operation was performed and updated is recorded to create an operation list (S103).

[0048] At this time, as pre-update information of the work shift schedule 30 updated by manual operations other than input operations, for example, when a sort operation is performed to rearrange items arranged in descending order into ascending order, the operation details for rearranging the items in the original descending order are recorded. Similarly, when a filter operation is performed to narrow down the items according to predetermined conditions, the operation details for canceling the narrowing down according to the predetermined conditions are recorded. Also, for example, when a background color change operation is performed to change the background color of a cell, the operation details for restoring the background color are recorded. Furthermore, when a comment addition operation is performed to add a specific comment 34 to a cell, the operation details for deleting the added comment 34 are recorded. Thereafter, the created operation list is added to the history list (S112).

[0049] On the other hand, if no manual operation other than the input operation is being performed, it is determined whether or not an input to the cell has been detected (S104). An input to the cell means, for example, inputting some value into the cell by an input operation to input first information. If no input to the cell is detected, it is determined whether or not the selection of the cell has been deselected (S105). If the selection of the cell has not been deselected, the process waits until a manual operation other than the input operation or an input to the cell is detected. If the selection of the cell has been deselected, the process waits until the selection of the cell is detected again.

[0050] Next, if an input to a cell is detected, an operation list is created (S106). At this time, it is determined whether the detected input is a value input to the cell (S107). If it is a value input, the pre-update information of the cell immediately before it is updated by the value input is recorded in the operation list (S108). Here, "value input" refers to the input of some value, such as a work type, NULL information, or supplemental information, into a cell, and includes the input of a value by copying and pasting information such as a work type stored in another cell. If the detected input is not a value input, an error is displayed indicating that the detected input does not correspond to either the input of a work type or the deletion or pasting of a work type, etc. (S109). In this way, when a manual operation such as the input, deletion, or pasting of a work type, etc. is performed on a cell, the pre-update information of the cell immediately before it is updated by the manual operation is recorded in the operation list.

[0051] Next, in the UNDO recording process, it is determined whether or not an automatic completion operation for inputting second information corresponding to the first information is performed in the work shift creation system 20 (S110). If an automatic completion operation is performed, it is determined that an automatic completion operation has been performed. At this time, in the work shift creation system 20, a value (information such as an auxiliary work type or supplemental information) for completing the work type as second information is input into another cell (either the first input area 32 or the second input area 33, or both, that are different from the first input area 32 into which the first information is input) by the automatic completion operation (S111). Furthermore, in the UNDO recording process, it is determined whether the input into the cell by the automatic completion operation is an input of a value into the cell (S107). At this time, the automatic completion operation is for inputting second information (for example, information such as a work type as an auxiliary work type or supplemental information) into the cell, so it is determined to be an input of a value, and the pre-update information of the cell immediately before the update by the automatic completion operation is added to the operation list (S108). In this way, when an auto-completion operation is performed, pre-update information of a cell immediately before the update by a manual operation and pre-update information of a cell immediately before the update by the auto-completion operation are recorded in one operation list. Note that the creation of the operation list ends when a new cell is selected and an input to the new cell or a manual operation other than an input operation is detected. The created operation list is then added to the history list (S112). In this way, in the recording step, the creation of the operation list and recording in the history list are repeated.

[0052] Here, the pre-update information for a cell specifically includes, for example, the coordinates of the cell into which the first information or the second information is input, the shift type stored in the cell, supplemental information added to the cell, and information about the format set for the cell (e.g., the format, such as the cell's background color, frame thickness, color, line type, and character thickness). More specifically, for example, as shown in the lower left of FIG. 3(b), if the coordinate in the horizontal direction X is defined as "coordinate X" and the coordinate in the vertical direction Y is defined as "coordinate Y," then if a shift type of "Day Shift A" is stored in the first input area 32 of the "1st" column and a shift type of "Early Morning" is stored in the first input area 32 of the "2nd" column, the cell in which "Day Shift A" is stored will have an X coordinate of "1" and a Y coordinate of "1," and the cell in which "Early Morning" is stored will have an X coordinate of "2" and a Y coordinate of "1." If NULL information is then entered into either or both of the cells storing "Day shift A" or "Dawn" in order to delete "Day shift A" and "Dawn" from this state, the display of the relevant cell will be updated to a blank (lower right side of Figure 3(b)). At this time, in the recording step, an operation list is created in which "Coordinates X: 1, Coordinate Y: 1, Cell information: Day shift A, Format: Bold frame" is recorded as the pre-update information immediately before the update of the cell in which "Day shift A" was stored, and "Coordinates X: 2, Coordinate Y: 1, Cell information: Dawn, Format: Bold frame" is recorded as the pre-update information immediately before the update of the cell in which "Dawn" was stored. This operation list is then recorded in the history list.

[0053] The history list also records the operation names and operation contents of the operation list. The operation names are names that indicate the contents of the operation list, and the operation contents are the contents of the information before the update that is recorded in the operation list. Specifically, for example, if a sort operation is performed to sort the values ​​entered in other cells in ascending order after the operation shown in the lower part of FIG. 3(b) (a manual operation to input "NULL information" to delete "Day shift A" and "Dawn"), the history list records "Operation name [Cell edit], Operation contents [Coordinate X: 1, Coordinate Y: 1, Cell information: Day shift A, Format: Bold frame]" and "Operation name [Cell edit], Operation contents [Coordinate X: 2, Coordinate Y: 1, Cell information: Dawn, Format: Bold frame]" as the first operation list, and records "Operation name [Sort operation], Operation contents [Descending order]" as the second operation list. The history list records the operation lists in the order of manual operations performed by the worker, and when the UNDO processing execution step is executed, the operation lists recorded in the history list are referenced in the reverse order of the operation order, and a restoration operation is performed in accordance with the pre-update information recorded in the referenced operation list.

[0054] The UNDO processing receiving step receives a cancellation request for canceling a manual operation based on an operation by the operator. Specifically, the UNDO processing receiving step receives a cancellation request when an UNDO processing receiving means, such as a "Undo" button 35 (FIG. 2(a)) displayed on the display unit 3 of the computer 1, is pressed via the input unit 4. The UNDO processing receiving step may also have a reception limit that limits the number of consecutive cancellation requests that can be received from the operator to a predetermined number. This predetermined number may be, for example, 10 or less, preferably 4 or less. Since the number of consecutive cancellation requests that can be received by the UNDO processing execution program 10 is limited, the recording step can also limit the number of times that an operation list is created and a history list is recorded. This reduces the storage capacity of the recording device or recording medium for recording the pre-update information, operation list, and history list. The reception of a cancellation request is not limited to the operation of the "Undo" button 35, but may also be based on a specific input (e.g., command input) from an input device such as a keyboard.

[0055] Furthermore, the UNDO processing reception step enters a non-acceptable state in which cancellation requests are not accepted when the UNDO processing cannot be executed, for example, when there is no operation list or history list that the UNDO processing execution step references to execute the restoration operation. For example, the non-acceptable state in which cancellation requests are not accepted is when the work shift schedule 30 is in its initial state before any operations have been performed, or when an operator has performed a single manual operation from the initial state and then executed the UNDO processing. Furthermore, if the UNDO processing reception step has an acceptance limit, the non-acceptable state is also entered when the number of consecutive cancellation requests accepted reaches a predetermined number. Specifically, if the maximum number of times that cancellation requests can be accepted is set to four, after four consecutive cancellation requests have been accepted, the non-acceptable state is entered and no further cancellation requests are accepted.

[0056] The UNDO processing execution step executes a restoration operation, which is an operation for returning the work shift table 30 to the state before the update, based on the pre-update information recorded in the recording step and the cancellation request accepted in the UNDO processing acceptance step. Specifically, the UNDO processing execution step refers to the last operation list created in the recording step and recorded in the history list, and executes a restoration operation corresponding to the pre-update information recorded in the operation list.

[0057] A restoration operation is an operation for returning work shift schedule 30 and input field 31 to the state they were in immediately before the update. For example, as shown in the lower left of Figure 3(b) above, if a work type of "Day shift A" is stored in the cell with coordinate X = "1" and coordinate Y = "1," and a work type of "Day shift A" is stored in the cell with coordinate X = "2" and coordinate Y = "1," and "NULL information" is entered into one or both of these cells to update them, the operation list will record "Operation name [Edit cell], Operation content [Coordinate X: 1, Coordinate Y: 1, Cell information: Day shift A, Format: Bold frame]" and "Operation name [Edit cell], Operation content [Coordinate X: 2, Coordinate Y: 1, Cell information: Day shift A, Format: Bold frame]." When a restoration operation is performed in this state, a restoration operation corresponding to the pre-update information is executed based on the pre-update information recorded in the operation list. In this case, for the cell with coordinate X of "1" and coordinate Y of "1," an input operation to input "Day shift A" recorded in the "cell information" of the pre-update information and a change operation to change the cell frame to a thicker frame are executed as restoration operations. Furthermore, for the cell with coordinate X of "2" and coordinate Y of "1," an input operation to input "Earlier" recorded in the "cell information" of the pre-update information and a change operation to change the cell frame to a thicker frame are executed as restoration operations. In this way, to return work shift schedule 30 to the state it was in immediately before the update, a restoration operation corresponding to the pre-update information is executed based on the pre-update information recorded in the operation list.

[0058] Also, for example, if the operation performed immediately before the update was a manual operation other than an input operation (such as a sort operation or a filter operation), the operation content of the operation recorded as the pre-update information is executed as the restoration operation. For example, if a manual sort operation is performed to rearrange what was arranged in descending order into ascending order, the operation to rearrange again in descending order is executed as the restoration operation. Similarly, if a filter operation to narrow down the results according to predetermined conditions is executed, the operation to cancel the narrowing down is executed as the restoration operation. Also, for example, if a background color change operation is performed to change the background color of a cell, the operation to restore the background color is executed as the restoration operation. Furthermore, if a comment addition operation is performed to add a specific comment 34 to a cell, the operation to delete the added comment 34 is executed as the restoration operation. Then, in the UNDO processing execution step, after executing all the restoration operations corresponding to each piece of pre-update information recorded together in one operation list, the operation list recorded at the end of the history list, in other words, the operation list referenced to execute the restoration operation, is deleted from the history list.

[0059] Next, the UNDO execution process in the UNDO process execution step will be specifically described with reference to Fig. 6. Fig. 6 is a flowchart showing the flow of the UNDO execution process. First, a cancellation request for canceling the immediately preceding manual operation is received in the UNDO processing receiving step based on an operation by the operator (S201). Then, based on the reception of this cancellation request, it is determined in the UNDO processing execution step whether or not an operation list is recorded in the history list (S202). If no operation list is recorded here, the UNDO execution process ends (S210). On the other hand, if an operation list is recorded, the operation list at the end of the history list is acquired (S203). Next, it is determined whether the operation name in the acquired operation list is "cell edit" (S204). Here, if the operation name in the operation list is not "cell edit," the operation recorded in the operation list is a manual operation other than an input operation such as a sort operation, a filter operation, a background color change operation, or a comment addition operation, so a restoration operation is performed based on the operation content of the pre-update information recorded in the operation list and reflected in the work shift table 30 (S205). Thereafter, the UNDO execution process ends (S210). On the other hand, if the operation name in the operation list is "cell edit," pre-update information at the end of the operation list is acquired (S206). Then, a restoration operation is executed based on the operation content of the acquired pre-update information, and is reflected in the cell (S207). After that, the pre-update information at the end of the operation list that was executed as the restoration operation is deleted from the operation list (S208). Next, it is determined whether or not there is still pre-update information in the operation list (S209). Here, if pre-update information remains in the operation list, the procedures from step S206 to step S209 are repeated. On the other hand, if there is no pre-update information remaining, the UNDO execution process is terminated (S210).

[0060] The above has been a description of the UNDO process execution program 10. Below, other functions provided in the UNDO process execution program 10 will be described. 7(a) and 7(b) are explanatory diagrams illustrating the NULL information input confirmation function. In the work shift creation system 20, for example, as shown in FIG. 7(a), when an operator attempts to input NULL information to delete a work type for "Day Shift A" that has already been entered in the work shift schedule 30, a confirmation display 36 is displayed, asking whether or not to enter the NULL information, as shown in FIG. 7(b). If the operator confirms the confirmation display 36 and cancels the deletion of "Day Shift A," the recording step of the UNDO processing execution program 10 is set not to record pre-update information based on the input of the NULL information, even if the input of the NULL information is detected. Therefore, when the input of NULL information to delete a work type is canceled by confirming the confirmation display 36, the input of the NULL information can be excluded from the UNDO processing. On the other hand, if the worker continues deleting "Day Shift A" after checking the confirmation display 36, the UNDO recording process is executed as usual in the recording step of the UNDO processing execution program 10, and the pre-update information before the update due to the input operation of the NULL information is recorded. Therefore, when the UNDO processing is executed using the UNDO processing execution program 10, it is possible to return to the pre-update state in which "Day Shift A" is entered in the work shift schedule 30, as shown in Figure 7(a).

[0061] 8(a) to 8(c) are explanatory diagrams for explaining a case where an input operation is performed by selecting multiple input areas 31. Note that Fig. 8(a) to 8(c) show a case where NULL information is input as the first information in order to delete the work type of "Day Shift A." In the work shift creation system 20, for example, as shown in FIG. 8(a), multiple first input areas 32 (for example, the first input areas 32 in the columns for "11th," "12th," and "13th" in which "Day shift A" has been entered) can be manually selected at once, and NULL information can be entered as first information into these first input areas 32 at once. When attempting to enter the NULL information, a confirmation message 36 is displayed (FIG. 8(b)) asking whether it is OK to enter the NULL information, as in the case of FIG. 7(b) described above. If the worker confirms this confirmation message 36 and proceeds with deleting "Day shift A," NULL information is entered into each first input area 32, and "Day shift A" is deleted from each first input area 32, as shown in FIG. 8(c). Furthermore, as second information corresponding to the NULL information input as first information, NULL information for deleting the "arrangements" information input in each of the second input areas 33 for the "11th," "12th," and "13th" columns is input into each of the second input areas 33 by an automatic completion operation. Then, in conjunction with the input of NULL information into each of the first input areas 32, NULL information is also input into each of the second input areas 33 by an automatic completion operation, and the "arrangements" in each of the second input areas 33 is also deleted.

[0062] In this case, in the recording step of the UNDO processing execution program 10, the pre-update information for each of the first input fields 32 in the columns "11th," "12th," and "13th" is recorded together in the operation list, and the pre-update information for each of the second input fields 33 into which NULL information (second information) corresponding to the NULL information entered as the first information is entered is also recorded together in the same operation list. In this way, in the recording step of the UNDO processing execution program 10, even when first information is entered together into multiple first input fields 32 and second information corresponding to this first information is entered together into multiple second input fields 33, the pre-update information for each of the first input fields 32 and the pre-update information for each of the second input fields 33 are recorded together. Therefore, by executing UNDO processing using the UNDO processing execution program 10, it is possible to restore the work shift schedule 30 to its pre-update state, in which "Day Shift A" and "Dispatch" were entered, as shown in FIG. 8(a), with a single UNDO processing execution. In the above example, multiple first input areas 32 in which the same work type, "Day shift A," is entered are selected, but different work types may also be stored in each of the selected multiple first input areas 32.

[0063] Furthermore, although not shown, for example, if a warning message is displayed when a value that cannot be entered in the first input field 32 is entered, and the worker cancels the input operation to enter the value, the recording step of the UNDO processing execution program 10 is configured not to record pre-update information based on the input operation, even if the input operation is detected. Therefore, when the input operation is canceled due to the warning message, the input operation can be excluded from the UNDO processing. Specifically, for example, if an input operation is performed to change "Shift A" entered in the first input field 32 to "Shift B," and then an attempt is made to enter a value that cannot be entered in the first input field 32, a warning message such as "Entry not permitted" is displayed. In this case, if the input operation to enter the value that cannot be entered is canceled, the shift type stored in the first input field 32 remains "Shift B," and the pre-update information based on the input operation to enter the value that cannot be entered is not recorded in the recording step. Therefore, if UNDO processing is executed using the UNDO processing execution program 10 in this state, the pre-update information based on the input operation attempting to enter a value that cannot be entered is not subject to recording in the recording step, and the state will return to "Work A," which was the state before the update to "Work B."

[0064] Furthermore, in the UNDO processing execution program 10, manual background color change operations are subject to UNDO processing, but background color changes due to operations other than manual background color change operations are excluded from the UNDO processing. Specifically, the work shift creation system 20 is provided with an error check function for checking errors in the work shift schedule 30, such as an error check function that checks whether a work type that violates the work shift creation rules has been assigned. If this error check function finds a problem with the work type entered in the input area 31, it changes the background color of the input area 31, and then, when the error check state is released, the change in background color of the input area 31 is released. In such cases, background color changes based on error checks are excluded from the targets for recording pre-update information in the recording step. By setting it in this way, when an operator performs work by changing the background color of the input area 31 as a flag indicating that some condition has been met, the change in background color made by the operator's manual operation is subject to UNDO processing, but the change in background color made based on an error check is excluded from the UNDO processing, so it becomes clear that the input area 31, which has been restored to its pre-update background color by UNDO processing, was changed by the operator's own manual operation. This allows the operator to work without confusing a change in background color made by manual operation with a change in background color made by the error check function.

[0065] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to the above-described embodiments, and various design modifications can be made to the present invention without departing from the scope of the claims.

[0066] For example, in the UNDO processing execution program 10 according to an embodiment of the present invention, an example has been given in which the data to be subjected to UNDO processing is the work shift schedule 30, but the data to be subjected to UNDO processing can be any data in tabular format, such as a management table for work processes, etc. Furthermore, the first information and second information are not limited to those relating to work types, and may be, for example, work types indicating the types of work processes. [Explanation of symbols]

[0067] 1. Computer 2. Control section 3 Display section 3a Display device 4 Input section 4a Input device 5. Communications Department 10 UNDO processing execution program 20 Work shift creation system 30 Work Shift Schedule 31 Input Area 32 First input area 33 Second input area 34 Comments 35 Back button 36 Confirmation Display X Left / right direction Y vertical direction

Claims

1. 1. An UNDO process execution program for causing a computer to execute an UNDO process for returning table-format data that can be updated by an arbitrary operation to a state before the update, a recording step of recording pre-update information that indicates a state of the data immediately before the update when the data is updated by a manual operation that is the operation performed by an operator; an UNDO processing receiving step of receiving a cancellation request for requesting cancellation of the manual operation; an UNDO processing execution step of executing a restoration operation corresponding to the pre-update information, which is the operation for restoring the data to a state before the update, based on the pre-update information recorded in the recording step and the undo request accepted in the UNDO processing acceptance step; In the recording step, when first information is input into the data input area by the manual operation, the pre-update information of the input area into which the first information is input is recorded, and when, after the first information is input by the manual operation, the second information is input into an input area different from the input area into which the first information is input by an auto-completion operation that automatically inputs second information corresponding to the first information, the pre-update information of the input area into which the second information is input is recorded together with the pre-update information of the input area into which the first information is input.

1. An UNDO processing execution program comprising:

2. The data is a work shift schedule, The first information includes a work type, The second information includes another work type corresponding to the work type input in the input area as the first information.

2. The UNDO process execution program according to claim 1, wherein:

3. The second information includes supplementary information for the work type input in the input area as the first information.

3. The UNDO process execution program according to claim 2, wherein:

4. When the first information is collectively input into a plurality of the input areas by the manual operation, the recording step records the pre-update information of each of the input areas into which the first information is input, and collectively records the pre-update information of each of the input areas into which the second information corresponding to each of the first information is input.

3. The UNDO process execution program according to claim 1, wherein the program executes an UNDO process.

5. The manual operation includes a sorting operation, which is the operation for rearranging the values ​​input into the input area according to a predetermined criterion, and / or a filtering operation, which is the operation for narrowing down the values ​​input into the input area according to a predetermined condition.

3. The UNDO process execution program according to claim 1, wherein the program executes an UNDO process.

6. the manual operation includes a background color change operation, which is the operation for changing the background color of the input area; 3. The UNDO process execution program according to claim 1, wherein the program executes an UNDO process.

7. the number of undo requests that can be consecutively accepted by the UNDO processing accepting step is limited to a predetermined number; 3. The UNDO process execution program according to claim 1, wherein the program executes an UNDO process.

8. A computer-readable medium storing the UNDO processing execution program according to claim 1 or 2, A computer-readable recording medium.

9. 1. An UNDO processing execution method for a computer to execute UNDO processing for returning table-format data that can be updated by any operation to a state before the update, comprising: a recording step of recording pre-update information that indicates a state of the data immediately before the update when the data is updated by a manual operation that is the operation performed by an operator; an UNDO processing receiving step of receiving a cancellation request for requesting cancellation of the manual operation; an UNDO processing execution step of executing a restoration operation corresponding to the pre-update information, which is the operation for restoring the data to a state before the update, based on the pre-update information recorded in the recording step and the undo request accepted in the UNDO processing acceptance step; In the recording step, when first information is input into the data input area by the manual operation, the pre-update information of the input area into which the first information is input is recorded, and when, after the first information is input by the manual operation, the second information is input into an input area different from the input area into which the first information is input by an auto-completion operation that automatically inputs second information corresponding to the first information, the pre-update information of the input area into which the second information is input is recorded together with the pre-update information of the input area into which the first information is input.

10. A method for executing an UNDO process, comprising:

Images