JPH11120247A - Electronic mail transmitting method for overlap operation of file object to reserved schedule object - Google Patents

Abstract

PROBLEM TO BE SOLVED: To additionally send materials through an electronic mail system to all reservation object members by reporting information for transmitting electronic mail, to which a drag &drop operation performed file object is added, to an acquired electronic mail address when a schedule object shows a reserved schedule. SOLUTION: When the drag & drop operation of the file object is performed on the schedule object on a schedule managing system picture and it is the schedule reserved by the object member, a processing part 112 acquires the addresses of electronic mail of all the object members of the reserved schedule, on which the drag &drop operation is performed, from an electronic mail address storage device 105. The information required for transmitting the electronic mail, to which the drag & drop operation performed file object is added, to the acquired electronic mail address is reported to an electronic mail system 106.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an e-mail transmission method in a schedule management system that operates on an operating system having a GUI screen, and in particular, transmits e-mail to all scheduled members who have already processed reservations. About the method.

[0002]

2. Description of the Related Art In a conventional schedule management system, a method of making a schedule reservation to a target person and transmitting a notification about the schedule reservation to the target member by e-mail is disclosed in Japanese Patent Application Laid-Open No. 08-214023, System ".

[0003]

When using a schedule management system, it is often the case that the schedule of a meeting or the like is adjusted first, and the meeting material is sent later, before the meeting is held.

According to this procedure, in a schedule management system in which the schedule reservation and the transmission of the material related to the schedule can be performed only at the same timing as in the above-described prior art, the schedule for which the reservation processing is already performed is performed. If no consideration is given to sending additional information, and if you want to send additional materials to the reservation target members, start the e-mail system and specify the e-mail addresses of all the reservation target members individually, There was a problem that email had to be sent.

[0005] An object of the present invention is to improve such a problem, and all members of the reservation target member can perform an operation of superimposing a file object on a reserved schedule object on a schedule management system screen represented by a GUI screen. To provide a method for sending additional materials by e-mail system.

[0006]

The operation of moving an object represented on a GUI screen by an input device and superimposing objects represented by other GUIs is hereinafter defined as a drag-and-drop operation.

In order to provide the above method, when a file object is dragged and dropped on a schedule object on a screen of a schedule management system, it is determined whether or not the schedule object is reserved by another person. The step of determining and the step of determining whether the member to be scheduled has performed a drag-and-drop operation on a file object with respect to the schedule object, and the case where the schedule object on which the drag-and-drop operation has been performed is a reserved schedule Obtaining the e-mail addresses of all the members to be scheduled, and the information necessary to send an e-mail with the file object that was dragged and dropped to the obtained e-mail address The four steps of the step of notifying the e-mail system is required.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will now be described with reference to an example of dragging and dropping a file object onto a reserved schedule data object.

FIG. 1 is a diagram showing the configuration of the present invention. The configuration of the invention includes an input device (101), a terminal (102), a schedule management system (103), a schedule data storage device (10
4) An e-mail address storage device (105), an e-mail system (106), and an e-mail data storage device (107).

The schedule management system processing unit (108) in the schedule management system (103) includes an input control processing unit (10).
9), a data management processing unit (110), a screen control processing unit (111), and a processing unit of the present invention (112).

[0011] The input control processing section (109) is a section for performing processing for transmitting information given from the input device (101) to the data management processing section (110). The data management processing unit (110) is a part that performs a process of associating data in the schedule data storage device (104) with data to be displayed on the terminal (102). The screen control processing unit (111) transmits the schedule data to the terminal (10
This is the part that performs control processing for displaying in 2). The processing unit (112) of the present invention is configured to attach an operation target file object to a reserved schedule data object displayed on the terminal (102) when the file object is dragged and dropped. This part performs processing for notifying the electronic mail system (106) of a mail transmission request. The schedule data storage device (104) is a storage device for storing data of the schedule management system (103), and it does not matter whether it is stored on a memory or a hard disk. Email address storage (10
5) is a storage device that associates an ID for identifying a user of the schedule management system (103) and an e-mail system (106) with an e-mail address and stores the data as data, which is stored in a memory or a hard disk. It does not matter. The e-mail system (106) is a system that manages transmission / reception of e-mail and associated data, and the e-mail data storage device (107) is a storage device for storing e-mail data, and is stored on a memory. Or stored on the hard disk.

FIG. 2 is a diagram of a display screen of the schedule management system (103). Schedule management system screen (2
01) is an area (202) for displaying the time of the day, an area (203) for displaying the schedule for each date, and an area (204) for displaying the date.
Area, which displays the schedule for each date (2
03), the data stored in the schedule data storage device (104) is stored in the schedule data object (205).
Display as This schedule data storage device (10
4) The data stored in (4) and the schedule data object (205) on the schedule management system screen (201)
Is a one-to-one correspondence mechanism by the data management processing unit (110). Schedule data object (205)
Is the schedule area (2
The user can move freely within the device 03) using the input device (101). The data update of the schedule data storage device (104) is performed when the schedule data object (205) is moved by the input device (101), the schedule is reserved for the user from another user, or the user newly registers a schedule. .

Next, a schedule data storage device (104)
The schedule data stored in the schedule management system will be described with reference to FIG. Schedule data (302) is managed for each user ID (301),
Date (303), Start time (304), End time (305), Message (30
6), destination (307), reservation person ID (308), and reservation person ID (309). The user ID (301) is an ID required to identify each user when using the schedule management system (103). Each data will be described using the data in the shaded portion in FIG. 3 as an example. The date (303) stores the data of the registered date of the schedule, June 4, 1997, "19970604", and the start time (304) and the end time (305) indicate the start time of the schedule. Data “1400” representing 14:00 and data “2000” representing 20:00 at the end of the schedule are stored. In addition, business requirements (306)
Contains data “meeting” that represents the contents of the schedule
Is stored, and “in-house”, which is the location data of the schedule, is stored in the destination (307). In the reservation ID (308),
User ID of the user who made the schedule reservation for the target person
Is stored, and the reserved person ID (309) stores "A, D, E, F" which is the user ID of the user who is the target of the reservation schedule.

FIG. 4 shows a data structure stored in the electronic mail address storage device (105). Reference numeral 401 denotes a schedule management system, a user ID (402) of the electronic mail system, and an electronic mail address (403), which correspond one-to-one. In FIG. 4, the e-mail address (403) whose user ID (402) is “A” is associated with “a@abc.co.jp”.

FIG. 5 shows the structure of electronic mail data stored in the electronic mail data storage device (107). 501 is the date (502), transmission time (503), sender ID (504), receiver ID (50
5), subject (506), contents (507), and attached file (508). Each data will be described using the data of the shaded portion in FIG. 5 as an example. The shaded data is 1997
User with user ID "C" at 9:26 on June 2, 2013
Indicates that the user with ID "A, D, E, F" described the contents in an e-mail titled "6/4 Meeting" and attached the file "ABC.TXT". ing.

FIG. 6 is a diagram showing each processing of the processing section (112) of the present invention. When the drag and drop operation of the file object is performed on the schedule object (205) on the schedule management system screen (201),
The next four steps are performed in order. In the reservation schedule determining step (601), it is determined whether or not the drag and drop operation of the file object has been performed on the schedule data object reserved by another person. In the target member determination step (602), it is determined whether the schedule target member has performed a drag-and-drop operation on the schedule object with the file object.

In the e-mail address acquisition step (603), the e-mail addresses of all the members of the reservation schedule subjected to the drag and drop operation are acquired from the e-mail address storage device (105). In the step (604) of notifying the e-mail system of the information to be transmitted,
The e-mail system notifies the e-mail system of information necessary for transmitting the e-mail attached with the file object subjected to the drag-and-drop operation to the e-mail address obtained in the e-mail address obtaining step (603).

Next, a reservation schedule determination step (60
Details of the process 1) will be described with reference to a flowchart.

FIG. 7 shows a reservation schedule determination step (60
It is a process flowchart of 1). In step 701, the user ID of the user currently using the schedule management system at the terminal (102) is obtained from the data management processing unit (110) and stored in the variable UserID. In step 702, when a drag and drop operation of a file object is performed in the schedule management system screen (201), an object to be subjected to the drag and drop operation is acquired from the screen control processing unit (111). In step 703, it is determined whether a drag and drop operation has been performed on the schedule data object. If the drag & drop operation is performed on the schedule data object (in the case of * YES * in step 703), in step 704, from the target schedule data, "message" (306), "reserver I
D '' (308), and the data set in each item of `` reserved person ID '' (309) are stored in the variables Youken, YoyakuID, and Member, respectively, and `` reserved person ID '' (308), `` reserved person The number of members for the reservation schedule obtained from “ID” (309) is stored in the variable Count. Then, the presence or absence of YoyakuID data is determined (705).
If there is data in the YoyakuID (when the determination is “YES” in step 705), it is determined that the schedule data is reserved, and the process proceeds to the target member determination process (706). YoyakuI
When there is no data of D (when the judgment is 'NO' in step 705)
Is not the reserved schedule data. If the determination is “NO” in step 703 or step 705, the drag and drop operation is cancelled.

FIG. 8 is a processing flowchart of the target member determination step (602). In step 801, 0 is set as an initial value to a flag (Flag) for determining whether the user who performed the drag and drop operation is a member of the target schedule, as a value that is not a member of the target schedule. Step 70 in the loop of Step 802
Judgment process of whether UserID acquired in 1 is equal to YoyakuID acquired in step 704 or included in Member (803)
Contains, UserID is equal to YoyakuID, or UserID is Member
If the user who performed the drag and drop operation is a member of the target schedule
(If 'YES' in step 803) is 1 in Flag in step 805
And exit from the loop of step 802. UserID is Y
If it is not equal to oyakuID and UserID is not included in Member, that is, if the user who performed the drag & drop operation is not a member of the target schedule (in the case of 'NO' in step 803), the Count in step 804 From the value of
While the count is positive by subtracting 1, the loop of step 802 is continued. After the loop of step 802, the flag is determined in step 806. When Flag is 1 (when "YES" in step 806)
Moves the process to the email address acquisition process (807) of the schedule target member, and if the Flag is not 1 (in the case of "NO" in step 806), an error message display process indicating that the operation is not the operation of the schedule target member After performing (808), the drag-drop operation is canceled.
Regarding the display of the error message in step 808, there is no limitation on the method.

FIG. 9 shows an e-mail address acquisition process (603).
26 is a process flowchart of a process (604) of notifying the e-mail system of information for transmitting an e-mail with a file object subjected to a drag and drop operation. In step 901, the e-mail address storage device (105)
Out of the reservation person ID (308) and the reservation person ID (309) of the target schedule data, excluding the ID of the user who performed the drag & drop operation of the file object,
Step 902 is an e-mail address corresponding to the user ID (402) of all target schedule members obtained in step 901
An e-mail address acquisition process (603) for acquiring (403) from the e-mail address storage device (105). In step 902, it is determined that the process has succeeded only when the e-mail addresses of all the target schedule members have been successfully acquired. In step 903, it is determined whether or not the e-mail address has been successfully obtained in step 902. When it is determined that the acquisition of the e-mail address is successful (step 903)
In step 902, the e-mail address as the destination of the obtained e-mail, the file subjected to the drag and drop operation as an e-mail attachment, and the subject (506) of the e-mail As the data to be set, a process (904) of notifying the data (306) of the schedule data subject to the drag and drop operation to the electronic mail system (106) together with the electronic mail transmission instruction is performed.

Then, in step 905, the electronic mail system (106) transmits an electronic mail based on the data notified from step 904, and the process ends. Step 90
If it is determined that the acquisition of the e-mail address has failed in step 3 (* NO * in step 903), an error message display process (906) indicating that the acquisition of the e-mail address of the schedule target member failed has been performed. After performing, the drag-drop operation is canceled. The method of displaying the error message in step 906 does not matter.

Here, the processing of step 603 and step 604 will be described using a specific example, taking the shaded portion of FIG. 3 as an example. The user with user ID 'C' is the user ID 'A', '
A schedule management system is used to reserve a schedule for four users D, E, and F. At this time, the user of the user ID 'E' drags a file object to the reserved schedule data object.
If a drop operation is performed, user IDs' A ',' C ',' D ','
The e-mail address of the user of F 'is obtained. If “YES” in the step 903, the e-mail addresses of the users with the user IDs “A”, “C”, “D”, and “F”, the “meeting” that is the “message” data, and The file on which the drop operation was performed is sent to the e-mail system (1
06) is notified.

[0024]

According to the present invention, when additional information is generated for a reserved schedule, the means for notifying the additional information to all schedule target members can be performed only by dragging and dropping a file. Become.

[0025] This makes it possible to easily transmit additional information to the schedule without individually specifying the e-mail addresses of the schedule subjects, thereby contributing to simplification of the procedure.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram

FIG. 2 is a schedule management system screen

FIG. 3 is a data configuration stored in a schedule data storage device.

FIG. 4 is a data configuration stored in an electronic mail address storage device.

FIG. 5 is a data configuration stored in an electronic mail data storage device.

FIG. 6 is a processing sequence of the present invention.

FIG. 7 is a flowchart of a reservation schedule determination process.

FIG. 8 is a flowchart of a reservation schedule target member determination process.

FIG. 9 is a flowchart of a process of acquiring an e-mail address of a reservation schedule target member and notifying the e-mail system of information necessary for e-mail transmission.

[Explanation of symbols]

101: input device, 102: terminal, 103: schedule management system, 104: schedule data storage device, 105: electronic mail address storage device, 106: electronic mail system, 107:
E-mail data storage device, 108: schedule management system processing unit, 201: schedule management system screen, 30
2: Schedule data, 401: E-mail address data, 501: E-mail data

Claims (1)

[Claims] 1. A file in which target members (reserved persons and reserved persons) of a reserved schedule are represented by a GUI with respect to a reserved schedule object on a schedule management system screen operated on an operating system having a GUI screen. A step of determining whether the member to be scheduled has performed a file object overlay operation on the schedule object when the object overlay operation has been performed; and determining whether the schedule object has been reserved by another person. And obtaining the e-mail addresses of all the members to be scheduled, and e-mailing information necessary for sending as an e-mail with a file object attached to the obtained e-mail address. How comprising the step of notifying the Temu.