IP Library Granted Patent US 7,565,643
Granted Patent B1
US 7,565,643 · App. 10/636,946 · Granted Jul 21, 2009

Sending notifications to project members in a project management system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,565,643
App. No.
10/636,946
Granted
Jul 21, 2009
Kind
B1
Abstract

An embodiment of the present invention is a technique to send notification to members in a project management system. A notification list and information are created for a project. The notification list and information are stored in a repository. A notification request is received from a component in the project management system. The notification request is processed at run-time using the notification list and information.

Claims (78)

1. A method comprising:

configuring a notification list and information for a notification of status of a component of a project in a project management system, the notification list and information being stored in a repository, the configuring comprising:

retrieving the notification list and information from the repository,

editing the notification list and information, the editing comprising editing a notification item associated with the component on the notification list and editing an enable status for the notification item, the enable status being one of enabled and disabled; and,

saving the edited notification in the repository;

receiving a notification request from the component in the project management system; and

processing the notification request at run-time using the notification list and information.

2. The method of claim 1 wherein editing the notification item comprises:

editing at least one of a destination, a source, a project name, a priority, a subject, and a notification message.

3. The method of claim 1 wherein configuring further comprises:

viewing the notification list and information.

4. The method of claim 1 wherein receiving the notification request comprises:

receiving the notification request from at least one of a checklist component, a document review component, an exit/entry component, a project instantiation component, and a project tracking component.

5. The method of claim 2 wherein processing the notification request comprises:

determining if the notification request corresponds to one of the enable status notification and an unconditional notification;

starting a mail session;

constructing a mail message; and

sending the mail message to the destination using a mail protocol.

6. The method of claim 5 wherein determining comprises:

checking the enable status; and

matching the notification request with a format defined by a notification document type definition.

7. The method of claim 1 wherein starting the mail session comprises:

starting a JavaMail session.

8. The method of claim 6 wherein sending the mail message comprises:

sending the mail message using a JavaMail Simple Mail Transfer Protocol (SMTP) to a configured mail server.

9. An article of manufacture comprising:

a machine-accessible medium tangibly comprising data that, when accessed by a machine, causes the machine to perform operations comprising:

configuring a notification list and information for a notification of status of a component of a project in a project management system, the notification list and information being stored in a repository, the configuring comprising:

retrieving the notification list and information from the repository,

editing the notification list and information, the editing comprising editing a notification item associated with the component on the notification list and editing an enable status for the notification item, the enable status being one of enabled and disabled; and,

saving the edited notification in the repository;

receiving a notification request from the component in the project management system; and

processing the notification request at run-time using the notification list and information.

10. The article of manufacture of claim 9 wherein the data causing the machine to perform editing the notification item comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

editing at least one of a destination, a source, a project name, a priority, a subject, and a notification message.

11. The article of manufacture of claim 9 wherein the data causing the machine to perform configuring further comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

viewing the notification list and information.

12. The article of manufacture of claim 9 wherein the data causing the machine to perform receiving the notification request comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

receiving the notification request from at least one of a checklist component, a document review component, an exit/entry component, a project instantiation component, and a project tracking component.

13. The article of manufacture of claim 10 wherein the data causing the machine to perform processing the notification request comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

determining if the notification request corresponds to one of the enable status notification and an unconditional notification;

starting a mail session;

constructing a mail message; and

sending the mail message to the destination using a mail protocol.

14. The article of manufacture of claim 13 wherein the data causing the machine to perform determining comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

checking the enable status; and

matching the notification request with a format defined by a notification document type definition.

15. The article of manufacture of claim 9 wherein the data causing the machine to perform starting the mail session comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

starting a JavaMail session.

16. The article of manufacture of claim 14 wherein the data causing the machine to perform sending the mail message comprises data that, when accessed by the machine, causes the machine to perform operations comprising:

sending the mail message using a JavaMail Simple Mail Transfer Protocol (SMTP) to a configured mail server.

17. A system comprising:

a processor; and

a memory coupled to the processor, the memory containing instructions that, when executed by the processor, cause the processor to:

configure a notification list and information for a notification of status of a component of a project in a project management system, the notification list and information being stored in a repository, the configuring comprising:

retrieving the notification list and information from the repository,

editing the notification list and information, the editing comprising editing a notification item associated with the component on the notification list and editing an enable status for the notification item, the enable status being one of enabled and disabled; and,

saving the edited notification in the repository;

receive a notification request from the component in the project management system; and

process the notification request at run-time using the notification list and information.

18. The system of claim 17 wherein the instructions causing the processor to edit the notification item comprises instructions that, when executed by the processor, cause the processor to:

edit at least one of a destination, a source, a project name, a priority, a subject, and a notification message.

19. The system of claim 17 wherein the instructions causing the processor to configure further comprises instructions that, when executed by the processor, cause the processor to:

view the notification list and information.

20. The system of claim 17 wherein the instructions causing the processor to receive the notification request comprises instructions that, when executed by the processor, cause the processor to:

receive the notification request from at least one of a checklist component, a document review component, an exit/entry component, a project instantiation component, and a project tracking component.

21. The system of claim 18 wherein the instructions causing the processor to process the notification request comprises instructions that, when executed by the processor, cause the processor to:

determine if the notification request corresponds to one of the enable status notification and an unconditional notification;

start a mail session;

construct a mail message; and

send the mail message to the destination using a mail protocol.

22. The system of claim 21 wherein the instructions causing the processor to determine comprises instructions that, when executed by the processor, cause the processor to:

check the enable status; and

match the notification request with a format defined by a notification document type definition.

23. The system of claim 17 wherein the instructions causing the processor to start the mail session comprises instructions that, when executed by the processor, cause the processor to:

start a JavaMail session.

24. The system of claim 22 wherein the instructions causing the processor to send the mail message comprises instructions that, when executed by the processor, cause the processor to:

send the mail message using a JavaMail Simple Mail Transfer Protocol (SMTP) to a configured mail server.

Assignments (11)
RELEASE OF SECURITY INTEREST Recorded Nov 9, 2017
From: WELLS FARGO BANK, NATIONAL ASSOCIATION (SUCCESSOR TO GENERAL ELECTRIC CAPITAL CORPORATION)
To: UNISYS CORPORATION
Reel/Frame 044416/0358 →
CHANGE OF NAME Recorded Oct 2, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044101/0610 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 17, 2012
From: UNISYS CORPORATION
To: GOOGLE INC.
Reel/Frame 028060/0908 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0530 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0701 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0777 →
SECURITY AGREEMENT Recorded Jun 27, 2011
From: UNISYS CORPORATION
To: GENERAL ELECTRIC CAPITAL CORPORATION, AS AGENT
Reel/Frame 026509/0001 →
SECURITY AGREEMENT Recorded May 7, 2010
From: UNISYS CORPORATION
To: DEUTSCHE BANK
Reel/Frame 024351/0546 →
RELEASE BY SECURED PARTY Recorded Jul 31, 2009
From: CITIBANK, N.A.
To: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
Reel/Frame 023086/0255 →
SECURITY AGREEMENT Recorded Jun 20, 2006
From: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
To: CITIBANK, N.A.
Reel/Frame 018003/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 6, 2003
From: SWEET, NANCY LEE; SADHU, AVINASH
To: UNISYS CORPORATION
Reel/Frame 014379/0956 →