US20130311223A1 - System and method for electronic message notification - Google Patents
System and method for electronic message notification Download PDFInfo
- Publication number
- US20130311223A1 US20130311223A1 US13/621,825 US201213621825A US2013311223A1 US 20130311223 A1 US20130311223 A1 US 20130311223A1 US 201213621825 A US201213621825 A US 201213621825A US 2013311223 A1 US2013311223 A1 US 2013311223A1
- Authority
- US
- United States
- Prior art keywords
- action
- recited
- recipient
- report
- reminders
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99948—Application of database or data structure, e.g. distributed, multimedia, or image
Definitions
- the present invention relates generally electronic communication and, more particularly, to systems and methods tor automatically delivering electronic messages to designated recipients.
- E-mail Electronic mail
- other types of electronic messages are becoming extremely popular.
- E-mail networks permit networks of communicating users to transmit information from one user to another. This has led to the widespread use of electronic messages to share ideas, transmit documents, schedule meetings, and perform a multitude of other everyday tasks.
- e-mail programs facilitate the transmission of messages between users.
- Messaging-enabled scheduling programs allow users to request and schedule meetings and appointments via electronic messages.
- computer programs such as desktop information managers coordinate the growing stream of electronic communications by incorporating e-mail, calendaring, task management, contact management, notes, and journal features into a single application program.
- data management personnel typically check the data management system everyday and build lists of data items needed by the system users. Then, the data management personnel compile the data items into reports and send the reports to designated recipients, such as employees, or clients.
- the system should be highly automated to decrease human error. Furthermore, the system should intelligently evaluate the data in a database and only forward desired data to authorized recipients. Moreover, the system preferably utilizes a last delivery system, such as email.
- the present invention addresses the above issues by providing an e-mail notification system for automatically delivering electronic messages.
- the e-mail notification system in a preferred embodiment of the present invention, comprises a docketing program and a data manager system (database).
- the docketing program checks action items in the database, and then creates notifications, in the form of messages, according the action items.
- the messages are then automatically sent to authorized, designated recipients.
- the designated recipients are preferably searched from the action items by the docketing program.
- a method for electronic mail notification in accordance with the present invention includes determining that it is a time for at least one of a reminder notification action and a report notification action.
- the method further includes obtaining all action items within a given range and processing the action items into at least one action item report and e-mailing the at least one action item report to at least one designated recipient.
- the method further includes obtaining a list of completed action items in a given range and processing the list of completed action items into at least one completed action report and e-mailing the at least one completed action report to at least one designated recipient.
- the method for obtaining of all action items and the obtaining a list preferably includes opening a docketing program, running a report, and saving the report for further processing.
- the docketing program may be a commercially available docketing program with built-in reporting capabilities.
- processing the action items includes reading the saved report into memory, parsing the report into items, and filtering out unwanted items.
- obtaining a list of completed action items includes reading the report into memory, parsing the report into items, and creating a list from the items.
- the present invention provides the ability to generate and distribute several types of the messages including reports and reminders.
- Completed action items are processed to create reports and sent to clients as the designated recipients. All action items within a given region are processed by fillers to create reminders, and are sent to authorized, designated recipients.
- Each of the reports comprises information about what has been done, while each reminder comprises information about what still needs to be done.
- FIG. 1 is a schematic diagram of a network system in which the present invention may find application, in accordance with one embodiment of the present invention
- FIG. 2 is a pictorial view showing the elements of an exemplary computer system of the network system of FIG. 1 ;
- FIG. 3 is a flow diagram illustrating a method of automatically generating messages in accordance with the present invention
- FIG. 4 is a flow diagram illustrating operation 304 and 308 of FIG. 3 , in accordance with yet another embodiment of the present invention.
- FIG. 5 is a How diagram illustrating operation 306 of FIG. 3 , in accordance with an embodiment of the present invention.
- FIGS. 6A-6D illustrate types of action items stored in the database, in accordance with another aspect of the present invention.
- FIG. 7A is an illustration used to explain operations 502 - 508 of FIG. 5 , in accordance with another aspect of the present invention.
- FIG. 7B is a flow diagram of me process illustrated in FIG. 7A ;
- FIG. 8 is a flow diagram illustrating operation 512 of FIG. 5 , in accordance with yet another aspect of the present invention.
- FIG. 9 is a flow diagram illustrating operation 514 of FIG. 5 , in accordance
- FIG. 10A is an illustration used to explain operation 905 of FIG. 9 , in accordance with another embodiment of the present invention.
- FIG. 10B is a flow diagram of the process illustrated in FIG. 10A ;
- FIG. 11 is a flow diagram illustrating operation 310 of FIG. 3 , in accordance with an embodiment of the present invention.
- FIG. 12 is a flow diagram illustrating operation 126 of FIG. 11 , in accordance with yet another aspect of the present invention.
- FIG. 1 is a schematic diagram of a network system 5 which may be utilized to implement an e-mail notification system, in accordance with one embodiment of the present invention.
- the network system 5 may connect to an internal Local Area Network (LAN) 10 , or include two networks 10 and 10 ′ that are connected together, such as with a T1 line 11 .
- the network system 5 may also include a wide area network (WAN) 12 , such as the Internet, typically through the services of an Internet Service Provider (ISP) 14 .
- the LAN 10 preferably includes a plurality of individual computers or computer stations 16 and 18 respectively, as discussed in detail subsequently.
- FIG. 2 is an illustration showing an exemplary computer system 20 for use with the e-mail notification system, in accordance with another embodiment of the present invention.
- the computer system 20 comprises a central processing unit (CPU) 21 , a system memory 22 , and a system memory bus 23 A which couples the system memory 22 to the processing unit 21 .
- the system memory 22 typically includes read only memory (ROM) 24 and random access memory (RAM) 25 .
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system
- BIOS basic routines that help transfer information between elements within the personal computer 20 , such as during start-up.
- the computer system 20 typically further includes peripherals, such as mass storage devices including a hard disk drive 27 , a floppy drive 28 , and a CD-ROM drive 29 , as well as a pointing device such as a mouse 34 , keyboard 35 , monitor 36 , and network card 37 .
- peripherals such as mass storage devices including a hard disk drive 27 , a floppy drive 28 , and a CD-ROM drive 29 , as well as a pointing device such as a mouse 34 , keyboard 35 , monitor 36 , and network card 37 .
- peripheral devices are typically coupled to an I/O bus 23 B which is, in turn, coupled to the CPU 21 .
- a number of program modules may be stored in the drives and, temporarily, RAM 25 of the computer system 20 , including at least portions of an operating system 30 , one or more application programs 31 , other program modules 32 , and program data 33 .
- Users typically enter commands and information into the computer system 20 utilizing the keyboard 35 and/or a pointing device, such as the mouse 34 .
- These input devices are often connected to the processing unit 21 through the I/O bus 23 B.
- a monitor 36 is typically connected to the processing unit 21 through the I/O bus 23 B.
- the computer system 20 may operate in a networked environment using logical connections to one or more remote computers, such as through a network card 37 .
- the e-mail notification system of the present invention comprises two parts—a reminder system, and a report system.
- the reminder system is used to send reminders to system users. These reminders typically comprise information such as due dates of action items, and are typically restricted to a given range of time.
- the report system is used to send reports to specified recipients, such as clients. Each report comprises Information such as action type, due dates of the action items, and what has been done, or will be done, within a given range of time.
- the data used to generate the reminders and reports is preferably located in a docket database, containing various records of data.
- FIG. 3 is a flowchart 299 illustrating a method of automatically generating messages, in accordance with an embodiment of the present invention.
- pre-process operations occur, such as initializing the docket database and other initial operations that will be apparent to those skilled in the art.
- a timing operation 302 the present invention determines when a report or reminder is to be generated. This determination is preferably based on a system clock of computer 20 . However, other methods may be utilized for timing, such as counters, and other techniques that will be apparent to those skilled in the art. Also included in operation 302 , is a determination of what type of item to generate. For example, a decision can be made as to whether a reminder is to be generated or a report is to be generated. When generating a reminder, the method continues with operation 304 . When generating a report, the method continues with operation 308 . If both a reminder and a report need to be generated, one can be generated after the other, or both can be generated concurrently, as will be appreciated by those skilled in the art.
- this range is a range of time, preferably 2-4 weeks, but the range can be extended to include all the action, items (i.e., the range equals infinity, or a period of time representing the same).
- the obtained actions items are processed into at least one reminder, which is then sent to designated recipients.
- designated it is meant that an authorized recipient who has a pertinent message is added to a list of designated recipients.
- the processing of the action items includes filtering out unwanted action items, and determining to which recipients generated reminders should be sent.
- the recipients of reminders are employees (one example of an authorized recipient) who utilize the system, however reminders can be sent to recipients, such as vendors, clients, or customers, outside an organization (another example of an authorized recipient).
- the present invention preferably creates an individual reminder for each designated recipient, thus allowing the reminders to be highly customizable for the individual needs of a particular recipient.
- an item gathering operation 308 if the system determines a report is to be generated, all completed action items within a given range are obtained.
- this range is a range of time, preferably 2-4 weeks, but the range can be extended to include all the action items (i.e., the range equals infinity, or a period of time representing the same).
- a report generating operation 310 the obtained actions items are processed into at least one report, which is then sent to designated recipients.
- the processing of the action items includes filtering out unwanted action items, and determining to which recipients generated reports should be sent.
- the recipients of reports are, for example, clients, however, reports may be generated for internal personnel as well.
- the present invention creates an individual report for each designated recipient, thus allowing the reports to be highly customizable for the individual needs of a particular recipient.
- a method 304 / 308 illustrates operations 304 and 308 of FIG. 3 in greater detail.
- operations 304 and 308 utilize equivalent or analogous methods for obtaining action items within a given range.
- an “action item” is a docket hem having associated with it an action to be performed and a date for such performance.
- Such dates may be “hard” such as a “drop dead” or “bar” date, or “soft” such as a reminder, target, or tickler date.
- the action items obtained in operation 304 will generally be non-completed action items, while the action items obtained in operation 308 will generally be completed action items.
- the method 304 / 308 begins after the timing operation 302 , where the systems determines when to send the reminders and reports.
- a docketing program is opened.
- the docketing program can be any docketing program capable of generating reports within a given range.
- One suitable docketing program is PCMASTER by MASTER DATA CENTER located in Southfield, Mich.
- opening a docketing program includes inputting a user name and password, and navigating to an area within the docketing program containing a report generator.
- the docketing program can be integrated with the process 299 of the present invention, i.e., the e-mail notification feature is integrated with a docketing system and its database.
- the report generator is updated with a new date range based on the current date.
- the report generator is capable of generating reports including action items falling within a range of time defined by a start date and an end date.
- the range is determined by calculating a start date and an end-date based on the current date.
- a report generating operation 406
- the report generator is executed using the start and end dates determined in operation 404 .
- the report generator creates a report using action items which fall within the date range determined in operation 404 .
- the result is a report including action items to be completed within a given range of time.
- the generated report is preferably saved to a mass storage device, such as a hard disk.
- a mass storage device such as a hard disk.
- FIG. 5 is a flowchart illustrating operation 306 of FIG. 3 , according to one embodiment of the present invention.
- a report, generated in operation 304 is read from a mass storage device, such as a hard disk, into memory.
- the report includes action items falling within a given range of time based on the current date, such as within two weeks of the current date.
- a report generated by a commercial report generator contains header and footer data. This data is generally not needed in the final reminder which is generated and sent out to a recipient.
- the header and footer data can be eliminated or saved for other uses.
- other page formatting information such as page breaks, may be eliminated by this technique.
- each docket item typically includes a record of data related to that particular docket item, including action item type, and often includes personnel assigned to that action item.
- a field parsing operation 508 the parsed docket hems are parsed into fields.
- individual fields of the docket item records arc parsed out. These fields typically include the type of action item, the personnel assigned to the action item, and the related clients.
- the method continues with a filtering, operation 510 .
- unwanted docket items are filtered out based on the field types included within the docket item.
- docket items having a specific type of field information are eliminated from further processing, as described in more detail below.
- filters are selected from the field types and set in the docketing program.
- a list of recipients is created. Using the fields of the filtered docket items, a list of recipients to which to send the final generated reminders is created.
- the list may be based on a personnel field, a client field, or any other appropriate field as will be apparent to those skilled in the art.
- a reminder is generated for each recipient on the recipient list.
- a generated reminder includes filtered action items related to the particular recipient for which the reminder is generated. After generating reminders, the method returns to the timing operation 302 of FIG. 3 .
- FIGS. 6A-6D are illustrations showing the results of the parsing operations of FIG. 5 .
- FIG. 6A is an illustration showing a typically report 600 generated by a commercial report generator. The report includes header data 602 and looter data 604 . Also shown are page breaks 606 . Typically, the header 602 and footer 604 data contain information identifying the program, page number, and date the report was created. As discussed above, this information may not be needed in the final generated reminder or report, thus the report is preferably parsed out into pages as shown in FIG. 6B .
- FIG. 6B is an illustration showing parsed pages 608 of information, based on the report shown, in FIG. 6A .
- Each parsed page generally includes all the information included on a page in the generated report of FIG. 6A , without the header 602 , footer 604 , and page break 606 information.
- FIG. 6C is an illustration showing parsed docket items 610 , based on the parsed pages of FIG. 6B .
- the docket items of each parsed page are parsed out into individual docket items 610 .
- each docket item 610 includes a record of data related to that particular docket item.
- FIG. 6D is an illustration showing parsed fields 612 , based on the parsed docket items 610 .
- the parsed fields typically include action item type, personnel assigned to the action item, one or more dates, and related clients. Once the individual fields are parsed out of the generated report, the system can easily use them to generate a final, reminder or report.
- FIG. 7A is a pictorial illustration used to explain, operation 510 of FIG. 5 .
- each record 702 of action items comprises many fields 704 , such as date, action type, country of an application, and client information.
- the present, invention provides several filters 706 selected from these fields.
- Each filter 706 typically includes a particular data related to a specified field.
- a filter 706 may include the particular data “return receipt postcard” related to the specific field 704 of “action, type.” In this manner, filters can filter out unwanted records. If a field of a record matches a filter, the record includes unwanted data.
- a field 704 of a record 702 can be “action type.”
- a filter 706 includes the particular data “return receipt postcard” related to the specific field 704 “action type.” If the field 704 “action type”, of a record 702 includes the specific data “return receipt postcard”, the record 702 matches the filter 706 . Thus, the system will determine that the record includes unwanted information. Finally, since the record 702 includes unwanted information, it is eliminated from further processing, as indicated by the garbage can 703 .
- FIG. 7B is a flowchart illustrating operation 510 of FIG. 5 for filtering docket items, in accordance with an embodiment of the present invention.
- the method 510 begins after the report, generated by the report generator, is parsed. Then, in a record obtaining operation 711 , the next record in the database is obtained.
- This record preferably includes fields related to a single action item.
- EEF End of File
- a comparing operation 714 the obtained record is compared to the next filter included in a filter list. A decision is then made as to whether a field in the record matches the filter, in operation 715 . If a field in the record matches the filter, the record is eliminated, in an elimination operation 717 . If a field in the record does not match the filter, the method 510 continues with operation 716 .
- FIG. 8 is a flow diagram illustrating operation 512 of FIG. 5 for creating a list of report and reminder recipients, in accordance with an embodiment of the present invention.
- the method 512 begins after the unwanted docket items are filtered out, in operation 510 of FIG. 5 .
- a record obtaining operation 801 the next record in the database is obtained.
- This record preferably includes fields related to a single action item.
- a decision is then made as to whether an End of File (EOF) has been reached, in operation 802 . If the EOF has been reached, the method 512 is complete, and operation 514 of FIG. 5 begins. However, if the EOF is not reached, the method 512 continues with an all recipients operation 803 .
- EEF End of File
- the recipient is added to the current recipient list. In this manner, a list of recipients is generated, which includes only approved recipients, without including duplicate recipients. Finally, after the recipient is added to the current recipient list, the next record is obtained in operation 801 . The method 512 continues until the EOF is reached.
- FIG. 9 is a flowchart illustrating the method 514 of FIG. 5 for generating a report for each recipient on the recipient list, in accordance with one aspect of the present invention.
- the method 514 begins after the recipient list is generated, in operation 512 of FIG. 5 .
- a recipient obtaining operation 901 the next recipient on the current recipient list is obtained. A decision is then made as to whether an End of File (EOF) has been reached for the recipient list, in operation 902 . If the EOF has been reached, the method 514 is complete, and operation 302 of FIG. 3 begins. However, if the EOF is not reached, the method 514 continues with a record obtaining operation 903 .
- EEF End of File
- a record obtaining operation 903 the next record in the database is obtained.
- This record preferably includes fields related to a single action item.
- EEF End of File
- a filtering operation 905 the record is filtered based on the particular recipients profile information.
- each recipient has a related profile which includes filters selected to filter out unwanted Information based on that particular recipient.
- the next record is obtained in operation 903 .
- the method 514 continues until the EOF is reached for the recipient list.
- FIG. 10A is an illustration used to explain operation 905 of FIG. 9 . More particularly.
- FIG. 10A is an illustration of a method tor adding a record to a special list, in accordance with another embodiment of the present invention.
- a record 1002 of action items comprises many fields 1004 , such as date, action type, country of an application, and client information.
- the present invention provides several filters 1006 selected from these fields.
- Each filter 1006 typically includes particular data related to a specified field.
- a filter 1006 may include the particular data “return receipt postcard” related to the specific field 704 of “action type.” In this manner, filters can filter out unwanted records. If a field of a record matches a filter, the record includes unwanted data.
- each filter 1006 includes additional information in the form of some type of indicia, such as a plus (+) or a minus ( ⁇ ). If a filter includes a minus, the filter is utilized to eliminate unwanted information. If a filter includes a plus, the filter is utilized to add or “promote” records to the special list.
- the special list is typically used to differentiate the records that are on the special list, such as by placing them first in a report.
- FIG. 10B is a flow diagram further illustrating a method 905 of FIG. 9 for filtering records based on a recipient's profile.
- the method 905 begins after an EOF is cheeked for the record database, as in operation 904 of FIG. 9 .
- a record obtaining operation 1101 the next record in the database is obtained.
- This record preferably includes fields related to a single action item.
- EEF End of File
- a report is generated for tire current recipient. Any items on the special list, discussed in detail subsequently, are preferably listed first.
- a preferred embodiment of the present invention sends the report by email to the current recipient. After sending the email, the method 905 is completed for the current recipient and the next recipient on the current recipient list is obtained, in operation 901 of FIG. 9 .
- a comparing operation 106 the obtained record is compared to the next filter Included in a filter list. A decision is then made as to whether a field in the record matches the filter, in operation 1107 . If a field in the record matches the filter, the method 905 continues with operation 1110 . If a field in the record does not match the filter, the method 905 continues with operation 1108 .
- an additional filters operation 1108 a determination is made as to whether more filters remain to be compared with the record. If more fibers remain to be compared, the method 905 continues with the comparison operation 1106 . If no more filters remain to be compared, the record is placed in the final report to the current recipient, in operation 1109 . The method 905 then continues with the next record obtaining operation 1101 .
- the type of filter is determined in operation 1110 . If the filter is a plus (+) filter, the filter is an add or“promote” filter, and the record is placed on the special list, in operation 1111 . If the filter is a minus ( ⁇ ) filter, the filter is an elimination filter, and the record is ignored by setting an “ignore record” flag for the current recipient, in operation 1112 . The method 905 then continues with the nest record obtaining operation 1101 . The method 905 continues until an EOF is reached.
- FIG. 11 is a flowchart further illustrating operation 310 of FIG. 3 for generating a report of completed action items, in accordance with yet another aspect of the present invention.
- a report generated in operation 308 is read into memory from a mass storage device, such as a hard disk.
- the report includes action items falling within a given range of time based on the current date, such as within two weeks of the current date.
- a page parsing operation 1122 the report is parsed into pages of data.
- a report generated by a commercial report generator contains header and footer data which is not needed in the final report generated and sent out to a recipient.
- the header and footer data can be eliminated or saved for other uses.
- other page formatting information such as page breaks, may be eliminated by this technique.
- each docket item typically includes a record of data related to that particular docket item, including action, item type, and often further includes personnel assigned to that action item.
- a field parsing operation 1124 the parsed docket items are parsed into fields.
- individual fields of the docket item records are parsed out. These fields typically include action item type, personnel assigned to the action item, and related clients.
- a list of recipients is created. Using the fields of the filtered docket items, a list of recipients of the final generated report is created. The list may be based on a personnel field, a client field, or any other appropriate field as will be apparent to those skilled in the art.
- a report is generated for each recipient on the recipient list, created in operation 1125 .
- a generated report includes filtered action items related to the particular recipient for which the report is generated. After generating reports, the method returns to the timing operation 302 of FIG. 3 .
- FIG. 12 is a flowchart illustrating a method 1226 of FIG. 11 for generating a report for each recipient, in accordance with an embodiment of the present invention.
- the method 1226 begins after the current recipient list is created, as in operation 1125 of FIG. 11 .
- a record obtaining operation 1202 the next record in the database is obtained.
- This record preferably includes fields related to a single action item.
- EEF End of File
- a report is generated for the current recipient. Any items on the special list are preferably listed first.
- a preferred embodiment of the present invention sends the report by email to the current recipient. After sending the email, the method 1226 is completed for the current recipient, in operation 1210 .
- a comparing operation 1212 the obtained record is compared to the next filter included in a filter list. A decision is then made as to whether a field in the record matches the filter, in operation 1214 . If a field in the record matches the filter, the method 1226 continues with operation 1216 . If a field in the record does not match the filter, the method 1226 continues with operation 1218 .
- an additional filters operation 1218 a determination is made as to whether more filters remain to be compared with the record. If more filters remain to be compared, the method 1226 continues with the comparison operation 1212 . If no more filters remain to be compared, the record is placed in the final report to the current recipient in operation 1220 . The method 1226 then continues with the next record obtaining operation 1202 .
- the type of filter is determined in operation 1216 . If the filter is a plus (+) filter, the filter is an add or “promote” filter, and the record is placed on the special list, in operation 1222 . If the filter is a minus ( ⁇ ) filter, the filter is an elimination filter, and the record is ignored by setting an “ignore record” flag for the current recipient, in operation 1224 . The method 1226 then continues with the next record obtaining operation 1202 . The method 1226 repeats until an EOF is reached.
Abstract
Description
- This application is a continuation of U.S. Ser. No. 11/440,702, filed May 24,2006, now U.S. Pat. No. 8,271,505, which is a continuation of U.S. Ser. No. 09/648,715, filed Aug. 25, 2000, now U.S. Pat. No. 7,082,439, which claims benefit of 60/150,921, filed Aug. 26, 1999, all of which are herein incorporated fey reference.
- The present invention relates generally electronic communication and, more particularly, to systems and methods tor automatically delivering electronic messages to designated recipients.
- The proliferation of electronic office systems has created a need for exchanging and storing information. Electronic mail (e-mail) and other types of electronic messages are becoming extremely popular. E-mail networks permit networks of communicating users to transmit information from one user to another. This has led to the widespread use of electronic messages to share ideas, transmit documents, schedule meetings, and perform a multitude of other everyday tasks.
- These tasks may be accomplished by a variety of software programs. For example, e-mail programs facilitate the transmission of messages between users. Messaging-enabled scheduling programs allow users to request and schedule meetings and appointments via electronic messages. In addition, computer programs such as desktop information managers coordinate the growing stream of electronic communications by incorporating e-mail, calendaring, task management, contact management, notes, and journal features into a single application program.
- However, as data management systems grow more complex, more users interact with them, and issues such as performance, data integrity, workload management, batch processing, efficiency and continuous availability arise. Many systems on the market today can only handle small numbers of users simultaneously, offer little or no expansion capabilities, and frequently require manual intervention to process data through the system.
- Users of data management systems often need to be reminded and apprised of approaching deadlines and other events. To keep these users informed, data management personnel typically check the data management system everyday and build lists of data items needed by the system users. Then, the data management personnel compile the data items into reports and send the reports to designated recipients, such as employees, or clients.
- In view of the foregoing, what Is needed are improved systems for getting the proper information (such as deadline information, competed action information, etc.) to the proper recipients. The system should be highly automated to decrease human error. Furthermore, the system should intelligently evaluate the data in a database and only forward desired data to authorized recipients. Moreover, the system preferably utilizes a last delivery system, such as email.
- The present invention addresses the above issues by providing an e-mail notification system for automatically delivering electronic messages. The e-mail notification system, in a preferred embodiment of the present invention, comprises a docketing program and a data manager system (database). The docketing program checks action items in the database, and then creates notifications, in the form of messages, according the action items. The messages are then automatically sent to authorized, designated recipients. The designated recipients are preferably searched from the action items by the docketing program.
- It will therefore be appreciated that a method for electronic mail notification in accordance with the present invention includes determining that it is a time for at least one of a reminder notification action and a report notification action. For a reminder notification action, the method further includes obtaining all action items within a given range and processing the action items into at least one action item report and e-mailing the at least one action item report to at least one designated recipient. For a report notification action, the method further includes obtaining a list of completed action items in a given range and processing the list of completed action items into at least one completed action report and e-mailing the at least one completed action report to at least one designated recipient.
- The method for obtaining of all action items and the obtaining a list preferably includes opening a docketing program, running a report, and saving the report for further processing. The docketing program may be a commercially available docketing program with built-in reporting capabilities. Preferably, processing the action items includes reading the saved report into memory, parsing the report into items, and filtering out unwanted items. Preferably, obtaining a list of completed action items includes reading the report into memory, parsing the report into items, and creating a list from the items.
- Advantageously, the present invention provides the ability to generate and distribute several types of the messages including reports and reminders. Completed action items are processed to create reports and sent to clients as the designated recipients. All action items within a given region are processed by fillers to create reminders, and are sent to authorized, designated recipients. Each of the reports comprises information about what has been done, while each reminder comprises information about what still needs to be done.
- These and other advantages of the present invention will become apparent upon a reading of the following descriptions and a study of the various figures of the drawing.
- The subject matter which is regarded as the invention's particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of practice, together with further objects and advantages thereof, may best be understood by reference to the following description taken in connection with the accompanying drawings in which:
-
FIG. 1 is a schematic diagram of a network system in which the present invention may find application, in accordance with one embodiment of the present invention; -
FIG. 2 is a pictorial view showing the elements of an exemplary computer system of the network system ofFIG. 1 ; -
FIG. 3 is a flow diagram illustrating a method of automatically generating messages in accordance with the present invention; -
FIG. 4 is a flowdiagram illustrating operation FIG. 3 , in accordance with yet another embodiment of the present invention; -
FIG. 5 is a How diagram illustrating operation 306 ofFIG. 3 , in accordance with an embodiment of the present invention; -
FIGS. 6A-6D illustrate types of action items stored in the database, in accordance with another aspect of the present invention; -
FIG. 7A is an illustration used to explain operations 502-508 ofFIG. 5 , in accordance with another aspect of the present invention; -
FIG. 7B is a flow diagram of me process illustrated inFIG. 7A ; -
FIG. 8 is a flowdiagram illustrating operation 512 ofFIG. 5 , in accordance with yet another aspect of the present invention; -
FIG. 9 is a flowdiagram illustrating operation 514 ofFIG. 5 , in accordance - with another embodiment of the present invention;
-
FIG. 10A is an illustration used to explainoperation 905 ofFIG. 9 , in accordance with another embodiment of the present invention; -
FIG. 10B is a flow diagram of the process illustrated inFIG. 10A ; -
FIG. 11 is a flowdiagram illustrating operation 310 ofFIG. 3 , in accordance with an embodiment of the present invention; and -
FIG. 12 is a flow diagram illustrating operation 126 ofFIG. 11 , in accordance with yet another aspect of the present invention. - A preferred embodiment of the present invention will now be described with reference to the various figures of the drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to unnecessarily obscure the present invention.
-
FIG. 1 is a schematic diagram of anetwork system 5 which may be utilized to implement an e-mail notification system, in accordance with one embodiment of the present invention. Thenetwork system 5 may connect to an internal Local Area Network (LAN) 10, or include twonetworks network system 5 may also include a wide area network (WAN) 12, such as the Internet, typically through the services of an Internet Service Provider (ISP) 14. TheLAN 10 preferably includes a plurality of individual computers orcomputer stations -
FIG. 2 is an illustration showing anexemplary computer system 20 for use with the e-mail notification system, in accordance with another embodiment of the present invention. These computer systems can be used for thecomputer stations computer system 20 comprises a central processing unit (CPU) 21, a system memory 22, and a system memory bus 23A which couples the system memory 22 to theprocessing unit 21. The system memory 22 typically includes read only memory (ROM) 24 and random access memory (RAM) 25. Typically included in theROM 24 is a basic input/output system (BIOS) 26, which contains basic routines that help transfer information between elements within thepersonal computer 20, such as during start-up. Thecomputer system 20 typically further includes peripherals, such as mass storage devices including ahard disk drive 27, afloppy drive 28, and a CD-ROM drive 29, as well as a pointing device such as amouse 34,keyboard 35, monitor 36, and network card 37. These peripheral devices are typically coupled to an I/O bus 23B which is, in turn, coupled to theCPU 21. - A number of program modules may be stored in the drives and, temporarily,
RAM 25 of thecomputer system 20, including at least portions of an operating system 30, one ormore application programs 31,other program modules 32, andprogram data 33. Users typically enter commands and information into thecomputer system 20 utilizing thekeyboard 35 and/or a pointing device, such as themouse 34. These input devices are often connected to theprocessing unit 21 through the I/O bus 23B. Additionally, amonitor 36 is typically connected to theprocessing unit 21 through the I/O bus 23B. Finally, thecomputer system 20 may operate in a networked environment using logical connections to one or more remote computers, such as through a network card 37. - The e-mail notification system of the present invention comprises two parts—a reminder system, and a report system. However, it should be noted that the reminder system and report system can also be used independently of each other, and that each individually forms an embodiment of the present invention. The reminder system is used to send reminders to system users. These reminders typically comprise information such as due dates of action items, and are typically restricted to a given range of time. The report system is used to send reports to specified recipients, such as clients. Each report comprises Information such as action type, due dates of the action items, and what has been done, or will be done, within a given range of time. The data used to generate the reminders and reports is preferably located in a docket database, containing various records of data.
-
FIG. 3 is aflowchart 299 illustrating a method of automatically generating messages, in accordance with an embodiment of the present invention. In aninitial operation 300, pre-process operations occur, such as initializing the docket database and other initial operations that will be apparent to those skilled in the art. - In a
timing operation 302, the present invention determines when a report or reminder is to be generated. This determination is preferably based on a system clock ofcomputer 20. However, other methods may be utilized for timing, such as counters, and other techniques that will be apparent to those skilled in the art. Also included inoperation 302, is a determination of what type of item to generate. For example, a decision can be made as to whether a reminder is to be generated or a report is to be generated. When generating a reminder, the method continues withoperation 304. When generating a report, the method continues withoperation 308. If both a reminder and a report need to be generated, one can be generated after the other, or both can be generated concurrently, as will be appreciated by those skilled in the art. - In an
item gathering operation 304, all non-completed action items within a given range are obtained. In a preferred embodiment, this range is a range of time, preferably 2-4 weeks, but the range can be extended to include all the action, items (i.e., the range equals infinity, or a period of time representing the same). - Next, in a reminder generating operation 306, the obtained actions items are processed into at least one reminder, which is then sent to designated recipients. By “designated” it is meant that an authorized recipient who has a pertinent message is added to a list of designated recipients. Typically, the processing of the action items includes filtering out unwanted action items, and determining to which recipients generated reminders should be sent. Generally, the recipients of reminders are employees (one example of an authorized recipient) who utilize the system, however reminders can be sent to recipients, such as vendors, clients, or customers, outside an organization (another example of an authorized recipient). Moreover, the present invention preferably creates an individual reminder for each designated recipient, thus allowing the reminders to be highly customizable for the individual needs of a particular recipient.
- In an
item gathering operation 308, if the system determines a report is to be generated, all completed action items within a given range are obtained. In a preferred embodiment, this range is a range of time, preferably 2-4 weeks, but the range can be extended to include all the action items (i.e., the range equals infinity, or a period of time representing the same). - Next, in a
report generating operation 310, the obtained actions items are processed into at least one report, which is then sent to designated recipients. Typically, the processing of the action items includes filtering out unwanted action items, and determining to which recipients generated reports should be sent. Typically, the recipients of reports are, for example, clients, however, reports may be generated for internal personnel as well. Generally, the present invention creates an individual report for each designated recipient, thus allowing the reports to be highly customizable for the individual needs of a particular recipient. - Referring next to
FIG. 4 , amethod 304/308 illustratesoperations FIG. 3 in greater detail. In this example,operations - As noted above, the action items obtained in
operation 304 will generally be non-completed action items, while the action items obtained inoperation 308 will generally be completed action items. Themethod 304/308 begins after thetiming operation 302, where the systems determines when to send the reminders and reports. - In an open docketing program operation 402, a docketing program is opened. The docketing program can be any docketing program capable of generating reports within a given range. One suitable docketing program is PCMASTER by MASTER DATA CENTER located in Southfield, Mich. Typically, opening a docketing program includes inputting a user name and password, and navigating to an area within the docketing program containing a report generator. Alternatively, the docketing program can be integrated with the
process 299 of the present invention, i.e., the e-mail notification feature is integrated with a docketing system and its database. - Next, in a
range setting operation 404, the report generator is updated with a new date range based on the current date. Preferably, the report generator is capable of generating reports including action items falling within a range of time defined by a start date and an end date. During therange setting operation 404, the range is determined by calculating a start date and an end-date based on the current date. - In a report generating,
operation 406, the report generator is executed using the start and end dates determined inoperation 404. The report generator creates a report using action items which fall within the date range determined inoperation 404. Thus, the result is a report including action items to be completed within a given range of time. - In a saving
operation 408, the generated report is preferably saved to a mass storage device, such as a hard disk. The method then continues to operation 306 ofFIG. 3 if a reminder is being generated, or tooperation 310 ofFIG. 3 if report is being generated. -
FIG. 5 is a flowchart illustrating operation 306 ofFIG. 3 , according to one embodiment of the present invention. In aninitial operation 502, a report, generated inoperation 304 is read from a mass storage device, such as a hard disk, into memory. Preferably, the report includes action items falling within a given range of time based on the current date, such as within two weeks of the current date. - In a page parsing operation 504, the report is parsed into pages of data. Typically, a report generated by a commercial report generator contains header and footer data. This data is generally not needed in the final reminder which is generated and sent out to a recipient. By parsing the generated report into pages, the header and footer data can be eliminated or saved for other uses. Moreover, other page formatting information, such as page breaks, may be eliminated by this technique.
- In an item parsing operation 506, the parsed pages of data are further parsed into docket items. Each docket item typically includes a record of data related to that particular docket item, including action item type, and often includes personnel assigned to that action item.
- Next, in a field parsing operation 508, the parsed docket hems are parsed into fields. In this operation, individual fields of the docket item records arc parsed out. These fields typically include the type of action item, the personnel assigned to the action item, and the related clients.
- The method continues with a filtering, operation 510. In operation 510, unwanted docket items are filtered out based on the field types included within the docket item. Typically, docket items having a specific type of field information are eliminated from further processing, as described in more detail below. Generally, filters are selected from the field types and set in the docketing program.
- In a
recipient list operation 512, a list of recipients is created. Using the fields of the filtered docket items, a list of recipients to which to send the final generated reminders is created. The list may be based on a personnel field, a client field, or any other appropriate field as will be apparent to those skilled in the art. - Finally, in a
reminder generating operation 514, a reminder is generated for each recipient on the recipient list. A generated reminder includes filtered action items related to the particular recipient for which the reminder is generated. After generating reminders, the method returns to thetiming operation 302 ofFIG. 3 . -
FIGS. 6A-6D are illustrations showing the results of the parsing operations ofFIG. 5 .FIG. 6A is an illustration showing a typically report 600 generated by a commercial report generator. The report includes header data 602 andlooter data 604. Also shown arepage breaks 606. Typically, the header 602 andfooter 604 data contain information identifying the program, page number, and date the report was created. As discussed above, this information may not be needed in the final generated reminder or report, thus the report is preferably parsed out into pages as shown inFIG. 6B . -
FIG. 6B is an illustration showing parsedpages 608 of information, based on the report shown, inFIG. 6A . Each parsed page generally includes all the information included on a page in the generated report ofFIG. 6A , without the header 602,footer 604, andpage break 606 information. -
FIG. 6C is an illustration showing parseddocket items 610, based on the parsed pages ofFIG. 6B . The docket items of each parsed page are parsed out intoindividual docket items 610. Generally, eachdocket item 610 includes a record of data related to that particular docket item. - Finally,
FIG. 6D is an illustration showing parsedfields 612, based on the parseddocket items 610. As discussed above, the parsed fields typically include action item type, personnel assigned to the action item, one or more dates, and related clients. Once the individual fields are parsed out of the generated report, the system can easily use them to generate a final, reminder or report. -
FIG. 7A is a pictorial illustration used to explain, operation 510 ofFIG. 5 . As shown inFIG. 7A , eachrecord 702 of action items comprisesmany fields 704, such as date, action type, country of an application, and client information. The present, invention, providesseveral filters 706 selected from these fields. Eachfilter 706 typically includes a particular data related to a specified field. For example, afilter 706 may include the particular data “return receipt postcard” related to thespecific field 704 of “action, type.” In this manner, filters can filter out unwanted records. If a field of a record matches a filter, the record includes unwanted data. - For example, a
field 704 of arecord 702 can be “action type.” In addition, afilter 706 includes the particular data “return receipt postcard” related to thespecific field 704 “action type.” If thefield 704 “action type”, of arecord 702 includes the specific data “return receipt postcard”, the record 702 matches thefilter 706. Thus, the system will determine that the record includes unwanted information. Finally, since therecord 702 includes unwanted information, it is eliminated from further processing, as indicated by thegarbage can 703. -
FIG. 7B is a flowchart illustrating operation 510 ofFIG. 5 for filtering docket items, in accordance with an embodiment of the present invention. The method 510 begins after the report, generated by the report generator, is parsed. Then, in arecord obtaining operation 711, the next record in the database is obtained. This record preferably includes fields related to a single action item. - A decision is then made to determine if an End of File (EOF) is reached in
operation 712. If the EOF has been reached, the method 510 is complete. However, if the EOF is not reached, the method continues with arecord application operation 713. - In the
record application operation 713, a decision is made as to whether the record applies to the particular report that is being generated. If the record does not apply to the particular report being generated, the record is ignored and the next record is obtained inoperation 711. If the record does apply to the report, then the method 510 continues with operation 714. - In a comparing operation 714, the obtained record is compared to the next filter included in a filter list. A decision is then made as to whether a field in the record matches the filter, in
operation 715. If a field in the record matches the filter, the record is eliminated, in anelimination operation 717. If a field in the record does not match the filter, the method 510 continues with operation 716. - In an additional fillers operation 716, a determination is made as to whether more filters remain to be compared with the record. If more filters remain to be compared, the method 510 continues with the comparison operation 714. If no more filters remain to be compared, the method 510 continues with the
record obtaining operation 711. The method then begins again until the EOF is reached. -
FIG. 8 is a flowdiagram illustrating operation 512 ofFIG. 5 for creating a list of report and reminder recipients, in accordance with an embodiment of the present invention. Themethod 512, begins after the unwanted docket items are filtered out, in operation 510 ofFIG. 5 . - In a
record obtaining operation 801, the next record in the database is obtained. This record preferably includes fields related to a single action item. A decision is then made as to whether an End of File (EOF) has been reached, inoperation 802. If the EOF has been reached, themethod 512 is complete, andoperation 514 ofFIG. 5 begins. However, if the EOF is not reached, themethod 512 continues with an allrecipients operation 803. - A decision is then made as to whether the record applies to all recipients, in
operation 803. If the record applies to all recipients, the record is ignored and themethod 512 obtains the next record, inoperation 801. If the record does not apply to all recipients, themethod 512 continues with a recipientcheck list operation 804. - Another decision is then made as to whether the recipient is on an approved list, in
operation 804. If the recipient is not on the approved list, the record is ignored and the next record is obtained, inoperation 801. If the recipient is on the approved list, themethod 512 continues withoperation 805. - Yet another decision is then made as to whether the recipient is on the current recipient list, in
operation 805. If the recipient is already on the current recipient list the record is ignored and the next record is obtained, inoperation 801. If the recipient is not already on the current recipient list, themethod 512 continues withoperation 806. - In
operation 806, the recipient is added to the current recipient list. In this manner, a list of recipients is generated, which includes only approved recipients, without including duplicate recipients. Finally, after the recipient is added to the current recipient list, the next record is obtained inoperation 801. Themethod 512 continues until the EOF is reached. -
FIG. 9 is a flowchart illustrating themethod 514 ofFIG. 5 for generating a report for each recipient on the recipient list, in accordance with one aspect of the present invention. Themethod 514 begins after the recipient list is generated, inoperation 512 ofFIG. 5 . - In a recipient obtaining operation 901, the next recipient on the current recipient list is obtained. A decision is then made as to whether an End of File (EOF) has been reached for the recipient list, in operation 902. If the EOF has been reached, the
method 514 is complete, andoperation 302 ofFIG. 3 begins. However, if the EOF is not reached, themethod 514 continues with arecord obtaining operation 903. - In a
record obtaining operation 903, the next record in the database is obtained. This record preferably includes fields related to a single action item. - A decision is then made as to whether an End of File (EOF) has been reached for the record database, in an operation 904. If the-EOF has been reached, the next recipient is obtained from the current recipient list, in operation 901. However, if the EOF is not reached, the
method 514 continues withfiltering operation 905. - In a
filtering operation 905, the record is filtered based on the particular recipients profile information. Preferably, each recipient has a related profile which includes filters selected to filter out unwanted Information based on that particular recipient. After filtering the record, the next record is obtained inoperation 903. Themethod 514 continues until the EOF is reached for the recipient list. -
FIG. 10A is an illustration used to explainoperation 905 ofFIG. 9 . More particularly.FIG. 10A is an illustration of a method tor adding a record to a special list, in accordance with another embodiment of the present invention. As shown inFIG. 10A , arecord 1002 of action items comprises many fields 1004, such as date, action type, country of an application, and client information. The present invention provides several filters 1006 selected from these fields. Each filter 1006 typically includes particular data related to a specified field. For example, a filter 1006 may include the particular data “return receipt postcard” related to thespecific field 704 of “action type.” In this manner, filters can filter out unwanted records. If a field of a record matches a filter, the record includes unwanted data. - In addition, each filter 1006 includes additional information in the form of some type of indicia, such as a plus (+) or a minus (−). If a filter includes a minus, the filter is utilized to eliminate unwanted information. If a filter includes a plus, the filter is utilized to add or “promote” records to the special list. The special list is typically used to differentiate the records that are on the special list, such as by placing them first in a report.
-
FIG. 10B is a flow diagram further illustrating amethod 905 ofFIG. 9 for filtering records based on a recipient's profile. In accordance with another aspect of the present invention. Themethod 905 begins after an EOF is cheeked for the record database, as in operation 904 ofFIG. 9 . Then, in arecord obtaining operation 1101, the next record in the database is obtained. This record preferably includes fields related to a single action item. - A decision is then made as to whether an End of File (EOF) has been reached in
operation 1102. If the EOF has not been reached, themethod 905 continues with arecord application operation 1105. If the EOF has been reached themethod 905 continues with areport preparation operation 1103. - In the
report preparation operation 1103, a report is generated for tire current recipient. Any items on the special list, discussed in detail subsequently, are preferably listed first. A preferred embodiment of the present invention sends the report by email to the current recipient. After sending the email, themethod 905 is completed for the current recipient and the next recipient on the current recipient list is obtained, in operation 901 ofFIG. 9 . - If the EOF is not reached, a decision is made as to whether the record applies to the particular report that is being generated, in a
record application operation 1105. If the record does not apply to the particular report being generated, the record is ignored and the next record is obtained inoperation 1101. If the record does apply to the report, themethod 905 then continues withoperation 1106. - In a comparing
operation 106, the obtained record is compared to the next filter Included in a filter list. A decision is then made as to whether a field in the record matches the filter, inoperation 1107. If a field in the record matches the filter, themethod 905 continues withoperation 1110. If a field in the record does not match the filter, themethod 905 continues with operation 1108. - In an additional filters operation 1108, a determination is made as to whether more filters remain to be compared with the record. If more fibers remain to be compared, the
method 905 continues with thecomparison operation 1106. If no more filters remain to be compared, the record is placed in the final report to the current recipient, inoperation 1109. Themethod 905 then continues with the nextrecord obtaining operation 1101. - Referring back to
operation 1107, if a field in the record matches the filter, the type of filter is determined inoperation 1110. If the filter is a plus (+) filter, the filter is an add or“promote” filter, and the record is placed on the special list, inoperation 1111. If the filter is a minus (−) filter, the filter is an elimination filter, and the record is ignored by setting an “ignore record” flag for the current recipient, inoperation 1112. Themethod 905 then continues with the nestrecord obtaining operation 1101. Themethod 905 continues until an EOF is reached. -
FIG. 11 is a flowchart further illustratingoperation 310 ofFIG. 3 for generating a report of completed action items, in accordance with yet another aspect of the present invention. In aninitial operation 1121, a report generated inoperation 308 is read into memory from a mass storage device, such as a hard disk. Preferably, the report includes action items falling within a given range of time based on the current date, such as within two weeks of the current date. - In a
page parsing operation 1122, the report is parsed into pages of data. Typically; a report generated by a commercial report generator contains header and footer data which is not needed in the final report generated and sent out to a recipient. By parsing the generated report into pages, the header and footer data can be eliminated or saved for other uses. Moreover, other page formatting information, such as page breaks, may be eliminated by this technique. - In an
item parsing operation 1123, the parsed pages of data are further parsed into docket items. Each docket item typically includes a record of data related to that particular docket item, including action, item type, and often further includes personnel assigned to that action item. - Next, in a
field parsing operation 1124, the parsed docket items are parsed into fields. In this operation, individual fields of the docket item records are parsed out. These fields typically include action item type, personnel assigned to the action item, and related clients. - In a
recipient list operation 1125, a list of recipients is created. Using the fields of the filtered docket items, a list of recipients of the final generated report is created. The list may be based on a personnel field, a client field, or any other appropriate field as will be apparent to those skilled in the art. - Finally, in a
report generating operation 1126, a report is generated for each recipient on the recipient list, created inoperation 1125. A generated report includes filtered action items related to the particular recipient for which the report is generated. After generating reports, the method returns to thetiming operation 302 ofFIG. 3 . -
FIG. 12 is a flowchart illustrating a method 1226 ofFIG. 11 for generating a report for each recipient, in accordance with an embodiment of the present invention. The method 1226 begins after the current recipient list is created, as inoperation 1125 ofFIG. 11 . Then, in arecord obtaining operation 1202, the next record in the database is obtained. This record preferably includes fields related to a single action item. - A decision is then made as to whether an End of File (EOF) has been reached, in
operation 1204. If the EOF has not been reached, the method continues 1226 with arecord application operation 1206. If the EOF has been reached the method 1226 continues with areport preparation operation 1208. - In the
report preparation operation 1208, a report is generated for the current recipient. Any items on the special list are preferably listed first. A preferred embodiment of the present invention sends the report by email to the current recipient. After sending the email, the method 1226 is completed for the current recipient, inoperation 1210. - If the EOF is not reached, decision is made as to whether the record applies to the particular report that is being generated, in
operation 1206. If the record does not apply to the particular report being generated, the record is ignored and the next record is obtained, inoperation 1202. If the record does apply to the report, the method 1226 continues withoperation 1212. - In a comparing
operation 1212, the obtained record is compared to the next filter included in a filter list. A decision is then made as to whether a field in the record matches the filter, inoperation 1214. If a field in the record matches the filter, the method 1226 continues withoperation 1216. If a field in the record does not match the filter, the method 1226 continues withoperation 1218. - In an
additional filters operation 1218, a determination is made as to whether more filters remain to be compared with the record. If more filters remain to be compared, the method 1226 continues with thecomparison operation 1212. If no more filters remain to be compared, the record is placed in the final report to the current recipient inoperation 1220. The method 1226 then continues with the nextrecord obtaining operation 1202. - Referring back to
operation 1214, if a field in the record matches the filter, the type of filter is determined inoperation 1216. If the filter is a plus (+) filter, the filter is an add or “promote” filter, and the record is placed on the special list, inoperation 1222. If the filter is a minus (−) filter, the filter is an elimination filter, and the record is ignored by setting an “ignore record” flag for the current recipient, inoperation 1224. The method 1226 then continues with the nextrecord obtaining operation 1202. The method 1226 repeats until an EOF is reached. - While the present invention has been described in terms of several preferred embodiments, there are many alterations, permutations, and equivalents which fall within the scope of this invention. It should also be noted that there are many alternative ways of implementing the methods and apparatuses of the present invention. It is therefore intended that the appended claims be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.
Claims (23)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/621,825 US20130311223A1 (en) | 1999-08-26 | 2012-09-17 | System and method for electronic message notification |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15092199P | 1999-08-26 | 1999-08-26 | |
US09/648,715 US7082439B1 (en) | 1999-08-26 | 2000-08-25 | System and method for electronic message notification |
US11/440,702 US8271505B2 (en) | 1999-08-26 | 2006-05-24 | System and method for electronic message notification |
US13/621,825 US20130311223A1 (en) | 1999-08-26 | 2012-09-17 | System and method for electronic message notification |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/440,702 Continuation US8271505B2 (en) | 1999-08-26 | 2006-05-24 | System and method for electronic message notification |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130311223A1 true US20130311223A1 (en) | 2013-11-21 |
Family
ID=36687150
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/648,715 Expired - Fee Related US7082439B1 (en) | 1999-08-26 | 2000-08-25 | System and method for electronic message notification |
US11/440,702 Expired - Lifetime US8271505B2 (en) | 1999-08-26 | 2006-05-24 | System and method for electronic message notification |
US13/621,825 Abandoned US20130311223A1 (en) | 1999-08-26 | 2012-09-17 | System and method for electronic message notification |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/648,715 Expired - Fee Related US7082439B1 (en) | 1999-08-26 | 2000-08-25 | System and method for electronic message notification |
US11/440,702 Expired - Lifetime US8271505B2 (en) | 1999-08-26 | 2006-05-24 | System and method for electronic message notification |
Country Status (1)
Country | Link |
---|---|
US (3) | US7082439B1 (en) |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002082880A (en) * | 2000-06-28 | 2002-03-22 | Oregadare Inc | Method and system for managing message transmission and reception |
US7343407B2 (en) | 2001-10-15 | 2008-03-11 | Ricoh Company, Ltd. | Method and system of remote monitoring and support of devices, including handling Email messages having message types specified within the Email message |
US7151824B1 (en) | 2003-05-19 | 2006-12-19 | Soundpath Conferencing Services | Billing data interface for conferencing customers |
US7624147B2 (en) * | 2003-09-04 | 2009-11-24 | Sierra Wireless, Inc. | Efficient notification of new electronic mail arrival |
US8219621B2 (en) * | 2003-09-04 | 2012-07-10 | Nokia Corporation | Method and device for handling push type e-mails for a mobile terminal device according to a user profile |
US20050223287A1 (en) * | 2004-03-25 | 2005-10-06 | International Business Machines Corporation | Presence-based system management information routing system |
US20060168050A1 (en) * | 2005-01-21 | 2006-07-27 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Interface for creation of limited-use electronic mail accounts |
US20060195527A1 (en) * | 2005-02-25 | 2006-08-31 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Limited-operation electronic mail accounts with set functions |
US8738707B2 (en) * | 2005-01-21 | 2014-05-27 | The Invention Science Fund I, Llc | Limited-life electronic mail accounts |
US20060168051A1 (en) * | 2005-01-21 | 2006-07-27 | Searete Llc, A Limited Liability Corporation Of The State Delaware | Limited-use instant messaging accounts |
US8831991B2 (en) * | 2005-01-21 | 2014-09-09 | The Invention Science Fund I, Llc | Limited-life electronic mail account as intermediary |
US8589452B2 (en) * | 2005-02-23 | 2013-11-19 | Microsoft Corporation | End user defined event rules for ERP applications |
US8340266B2 (en) * | 2005-09-13 | 2012-12-25 | American Teleconferences Services, Ltd. | Online reporting tool for conferencing customers |
US20070150520A1 (en) * | 2005-12-08 | 2007-06-28 | Microsoft Corporation | User defined event rules for aggregate fields |
US20080059123A1 (en) * | 2006-08-29 | 2008-03-06 | Microsoft Corporation | Management of host compliance evaluation |
US8122041B2 (en) * | 2009-05-08 | 2012-02-21 | Microsoft Corporation | Sharing and collaboration of search findings |
US8341023B2 (en) * | 2009-06-17 | 2012-12-25 | Trustifi Corporation | Certified email system and method |
Family Cites Families (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US601663A (en) * | 1898-04-05 | Shore-protector | ||
US5276869A (en) | 1990-09-10 | 1994-01-04 | International Business Machines Corporation | System for selecting document recipients as determined by technical content of document and for electronically corroborating receipt of document |
JP3210102B2 (en) | 1992-11-17 | 2001-09-17 | 松下電器産業株式会社 | Electronic document filing apparatus and filing document search method |
US5446740A (en) | 1993-12-17 | 1995-08-29 | Empire Blue Cross/Blue Shield | Method of and apparatus for processing data at a remote workstation |
US5875432A (en) * | 1994-08-05 | 1999-02-23 | Sehr; Richard Peter | Computerized voting information system having predefined content and voting templates |
US5608874A (en) | 1994-12-02 | 1997-03-04 | Autoentry Online, Inc. | System and method for automatic data file format translation and transmission having advanced features |
US5694616A (en) * | 1994-12-30 | 1997-12-02 | International Business Machines Corporation | Method and system for prioritization of email items by selectively associating priority attribute with at least one and fewer than all of the recipients |
US6237096B1 (en) | 1995-01-17 | 2001-05-22 | Eoriginal Inc. | System and method for electronic transmission storage and retrieval of authenticated documents |
US5748738A (en) | 1995-01-17 | 1998-05-05 | Document Authentication Systems, Inc. | System and method for electronic transmission, storage and retrieval of authenticated documents |
CA2683230C (en) | 1995-02-13 | 2013-08-27 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
US6298327B1 (en) | 1995-03-08 | 2001-10-02 | Yes Technologies | Expert support system for authoring invention disclosures |
US5732219A (en) | 1995-03-17 | 1998-03-24 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for remote editing of computer files |
US5956489A (en) | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
US5826269A (en) * | 1995-06-21 | 1998-10-20 | Microsoft Corporation | Electronic mail interface for a network server |
US5768505A (en) * | 1995-12-19 | 1998-06-16 | International Business Machines Corporation | Object oriented mail server framework mechanism |
US5754840A (en) | 1996-01-23 | 1998-05-19 | Smartpatents, Inc. | System, method, and computer program product for developing and maintaining documents which includes analyzing a patent application with regards to the specification and claims |
US5850442A (en) * | 1996-03-26 | 1998-12-15 | Entegrity Solutions Corporation | Secure world wide electronic commerce over an open network |
US5923848A (en) * | 1996-05-31 | 1999-07-13 | Microsoft Corporation | System and method for resolving names in an electronic messaging environment |
US5862346A (en) | 1996-06-28 | 1999-01-19 | Metadigm | Distributed group activity data network system and corresponding method |
US5982506A (en) | 1996-09-10 | 1999-11-09 | E-Stamp Corporation | Method and system for electronic document certification |
US5895468A (en) * | 1996-10-07 | 1999-04-20 | Whitmyer, Jr.; Wesley W. | System automating delivery of professional services |
US6708202B1 (en) * | 1996-10-16 | 2004-03-16 | Microsoft Corporation | Method for highlighting information contained in an electronic message |
US6192407B1 (en) | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
US5790790A (en) | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
US5930471A (en) * | 1996-12-26 | 1999-07-27 | At&T Corp | Communications system and method of operation for electronic messaging using structured response objects and virtual mailboxes |
US6138162A (en) | 1997-02-11 | 2000-10-24 | Pointcast, Inc. | Method and apparatus for configuring a client to redirect requests to a caching proxy server based on a category ID with the request |
US5982898A (en) | 1997-03-07 | 1999-11-09 | At&T Corp. | Certification process |
US6073105A (en) | 1997-06-13 | 2000-06-06 | Tele-Publishing, Inc. | Interactive personals online network method and apparatus |
US6363361B1 (en) | 1997-07-22 | 2002-03-26 | Patent & Trademark Fee Management, Llc | Computerized patent and trademark fee payment method and system for law firms |
US6195686B1 (en) * | 1997-09-29 | 2001-02-27 | Ericsson Inc. | Messaging application having a plurality of interfacing capabilities |
US6092102A (en) * | 1997-10-24 | 2000-07-18 | University Of Pittsburgh Of The Commonwealth System Of Higher Education | System and method for notifying users about information or events of an enterprise |
JPH11143936A (en) * | 1997-11-13 | 1999-05-28 | Nippon Telegr & Teleph Corp <Ntt> | Schedule reminding notification processing method, schedule management device and recording medium storing reminding notification program |
US6477578B1 (en) | 1997-12-16 | 2002-11-05 | Hankey Mhoon | System and method for conducting secure internet transactions |
US5987429A (en) | 1997-12-16 | 1999-11-16 | Sun Microsystems, Inc. | Computer-based fee processing for electronic commerce |
US6192165B1 (en) | 1997-12-30 | 2001-02-20 | Imagetag, Inc. | Apparatus and method for digital filing |
CA2228331C (en) | 1998-01-30 | 2002-01-15 | Ibm Canada Limited-Ibm Canada Limitee | A token-based deadline enforcement system for electronic document submission |
US6016479A (en) * | 1998-02-10 | 2000-01-18 | Interstate Solutions, Llc | Computer-based system, computer program product and method for recovering tax revenue |
US6154840A (en) | 1998-05-01 | 2000-11-28 | Northern Telecom Limited | System and method for transferring encrypted sections of documents across a computer network |
US6345278B1 (en) | 1998-06-04 | 2002-02-05 | Collegenet, Inc. | Universal forms engine |
US6314454B1 (en) * | 1998-07-01 | 2001-11-06 | Sony Corporation | Method and apparatus for certified electronic mail messages |
US6584466B1 (en) | 1999-04-07 | 2003-06-24 | Critical Path, Inc. | Internet document management system and methods |
US6289460B1 (en) | 1999-09-13 | 2001-09-11 | Astus Corporation | Document management system |
US6324648B1 (en) | 1999-12-14 | 2001-11-27 | Gte Service Corporation | Secure gateway having user identification and password authentication |
-
2000
- 2000-08-25 US US09/648,715 patent/US7082439B1/en not_active Expired - Fee Related
-
2006
- 2006-05-24 US US11/440,702 patent/US8271505B2/en not_active Expired - Lifetime
-
2012
- 2012-09-17 US US13/621,825 patent/US20130311223A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US7082439B1 (en) | 2006-07-25 |
US8271505B2 (en) | 2012-09-18 |
US20070011202A1 (en) | 2007-01-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8271505B2 (en) | System and method for electronic message notification | |
US6617969B2 (en) | Event notification system | |
US7530021B2 (en) | Instant meeting preparation architecture | |
US6816885B1 (en) | Method and system to handle large volume of E-mail received from a plurality of senders intelligently | |
US6604079B1 (en) | System and method for feeding e-mail with calendar data | |
US9407707B2 (en) | Method and apparatus for demographic-based reminders | |
US6816863B2 (en) | Method, system, and computer product for providing a distribution list | |
US7299193B2 (en) | Method and meeting scheduler for automated meeting scheduling using delegates, representatives, quorums and teams | |
US20030004773A1 (en) | Scheduling system with methods for polling to determine best date and time | |
US20030018643A1 (en) | VIGIP006 - collaborative resolution and tracking of detected events | |
US8738709B2 (en) | Automated email activity management | |
US20030154254A1 (en) | Assisted messaging for corporate email systems | |
US20090077026A1 (en) | Electronic Communication Messaging | |
US20020188620A1 (en) | Calendar-enhanced directory searches including dynamic contact information | |
CN101000667A (en) | System and method of dynamic examining procedure | |
US20040215499A1 (en) | Method and system for automated meeting scheduling | |
US20090217176A1 (en) | Method and system for managing events in an electronic calendar application | |
US20020156601A1 (en) | Event monitoring and detection system | |
US20020184234A1 (en) | Internet-based patent and trademark applicaton management system | |
Whittaker et al. | 10. Everything through Email | |
US20050050146A1 (en) | Mail management system and method | |
US20060277258A1 (en) | Managing and organizing electronic mail messages via a cross tabulation summary or a histogram | |
US20030018722A1 (en) | Method of managing an update of a changed electronic mail address | |
US20040215497A1 (en) | Method and system for automated meeting scheduling | |
US20080183834A1 (en) | Method and system for dynamic reader-instigated categorization and distribution restriction on mailing list threads |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: G&H NEVADA-TEK, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NEOSTAR, INC.;REEL/FRAME:029162/0364 Effective date: 20050118 Owner name: NEOSTAR, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HSC VENTURE FUND 1999;REEL/FRAME:029162/0357 Effective date: 20010403 Owner name: HSC VENTURE FUND 1999, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HICKMAN, PAUL L.;GOUGH, JAMES J.;REEL/FRAME:029162/0353 Effective date: 20001204 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |