US20110022662A1 - Event triggered notifications for collaborative processes - Google Patents

Event triggered notifications for collaborative processes Download PDF

Info

Publication number
US20110022662A1
US20110022662A1 US12/507,939 US50793909A US2011022662A1 US 20110022662 A1 US20110022662 A1 US 20110022662A1 US 50793909 A US50793909 A US 50793909A US 2011022662 A1 US2011022662 A1 US 2011022662A1
Authority
US
United States
Prior art keywords
collaborative
originator
computer
collaborative process
program code
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
Application number
US12/507,939
Inventor
Cynthia E. Barber-Mingo
Arno Denne
Liam S. Harpur
John Kennedy
Paula Prendergast
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US12/507,939 priority Critical patent/US20110022662A1/en
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BARBER-MINGO, CYNTHIA E., DENNE, ARNO, HARPUR, LIAM S., KENNEDY, JOHN, PRENDERGAST, PAULA
Priority to TW099118947A priority patent/TW201112691A/en
Priority to CN2010800317666A priority patent/CN102473251A/en
Priority to PCT/EP2010/060584 priority patent/WO2011009896A1/en
Publication of US20110022662A1 publication Critical patent/US20110022662A1/en
Priority to US14/826,273 priority patent/US9813460B2/en
Priority to US15/602,649 priority patent/US10015211B2/en
Priority to US15/967,715 priority patent/US10320858B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications
    • H04L65/401Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H04L65/4015Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/107Computer-aided management of electronic mailing [e-mailing]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/04Processing captured monitoring data, e.g. for logfile generation
    • H04L43/045Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data

Definitions

  • the present invention relates to enhancements of electronic collaborative processes, and in particular, to the propagation of notifications that serve as “hints” related to activity associated with a corresponding collaborative process.
  • Electronic mail (email) systems, electronic calendars and electronic to-do lists are quite popular among computer users, both in business settings and for personal use.
  • a message originator has relatively little visibility as to how a message recipient handles a received message, including when a particular message is opened or viewed, how messages are prioritized, whether messages that require some type of follow-up action are addressed, and so forth.
  • it is typically expected that some sort of activity may be required by the recipient of a shared electronic calendar event and/or shared to-do task.
  • an event or task originator has relatively little visibility as to when the shared event or task is opened or viewed by the recipient.
  • the originator has little visibility as to whether the recipient has implemented some type of follow-up action, etc.
  • the originator and/or recipient For messages, events and/or tasks that request that the recipient perform some type of action, the originator and/or recipient must manually take action to track the message, event or task status. For example, the originator may be required to send a follow-up message to the recipient to check on the status of the specific request.
  • a collaborative process is tracked and a notification of an occurrence of an event is propagated to an originator.
  • a collaborative process server computer having a processor and at least one memory device, and coupled to a network environment receives an indication that a user has initiated a computer implemented collaborative process that generates collaborative content, wherein the user defines an originator of the generated collaborative content.
  • the collaborative process server computer obtains a designation that events associated with the initiated collaborative process are to be tracked.
  • the collaborative content associated with the collaborative process is shared with at least one recipient.
  • the collaborative process server computer obtains information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content, other than a communication from any recipient back to the originator.
  • the information associated with the collaborative process is automatically transformed in response to at least one detected event associated with the shared collaborative content.
  • a notification is propagated to the originator that informs the originator of the detected event.
  • the notification is generated in response to the detected event and is based upon the transformed information.
  • a user of a collaborative process is notified that an event of interest has occurred.
  • a graphical user interface is implemented that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked.
  • the user defines an originator of the generated collaborative content.
  • the graphical user interface graphically interacts with the originator of the collaborative content to designate at least one event that triggers a notification to the originator of the collaborative content.
  • the graphical user interface communicates with a collaborative process server computer coupled to a network environment to identify the collaborative process to be tracked and at least one event associated with the collaborative process to monitor.
  • the collaborative content is shared with at least one recipient.
  • the graphical user interface receives an indication from the collaborative process server computer that at least one designated event has occurred, other than a communication from any recipient back to the originator.
  • the graphical user interface is transformed to modify a visual display of the shared collaborative content if a designated event associated with the shared collaborative content is detected so as to visually depict the notification of the occurrence of the event to the originator.
  • FIG. 1 is a schematic illustration of an exemplary system in which computer-implemented event triggered notifications can be electronically generated and/or delivered, where the notifications correspond to hints of activity associated with a corresponding collaborative process;
  • FIG. 2 is block diagram of a system to facilitate computer-implemented event triggered propagation of notifications associated with corresponding tracked collaborative processes, according to various aspects of the present invention
  • FIG. 3 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with corresponding tracked collaborative processes, according to various aspects of the present invention
  • FIG. 3A is an illustration of a graphical user interface including exemplary sets of rules to be applied to a collaborative process according to various aspects of the present invention
  • FIG. 3B is an illustration of a graphical user interface including an exemplary transformation according to various aspects of the present invention.
  • FIG. 4 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked email message according to various aspects of the present invention
  • FIG. 5 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked electronic calendar event according to various aspects of the present invention
  • FIG. 6 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked electronic to-do task according to various aspects of the present invention.
  • FIG. 7 is a block diagram of an exemplary computer system including a computer usable storage medium having computer usable program code embodied therewith, where the exemplary computer system is capable of executing a computer program product to provide event triggered hints or notifications for communications related to one or more tasks according to various aspects of the present invention.
  • hints are triggered by detecting the occurrence of one or more events associated with a shared collaborative process.
  • the propagated hints alert an originator of the shared collaborative process as to the occurrence of the associated triggering event(s) in a manner that may not reveal the specific details of the associated triggering event(s).
  • the hints are propagated to inform the originator that a triggering event has occurred, e.g., an assigned task is being worked on, a follow-up meeting has been scheduled, etc., without requiring the originator of the shared collaborative process to micro-manage the details of those events or to otherwise proactively monitor the status of the corresponding shared collaborative process.
  • the generation of hints may be automated or semi-automated in a manner that eliminates, substantially eliminates, simplifies or otherwise reduces the interaction required by the shared collaborative process recipient in order for the originator to receive the hint.
  • the ability to automatically track triggering events thus allows automated “overview level” management in a manner that does not require the originator to expend significant resources on follow-ups for situations where a recipient is taking steps to implement an action associated with the shared collaborative process.
  • Each hint received by the originator identifies the occurrence of one or more events of interest that are associated with a corresponding collaborative process.
  • events may be positive actions, e.g., activity carried out by a recipient, such as forwarding a communication associated with the corresponding collaborative process.
  • An event may also comprise a negative action or omission of an anticipated action, such as a failure of a recipient to take an action within a prescribed period of time.
  • each hint contains sufficient information to allow the corresponding originator to at least identify that the associated event has occurred.
  • the originator of a collaborative process may interact with a graphical user interface to configure the manner in which the hints are, or are not, conveyed.
  • the collaborative process originator may select an option within the graphical user interface to receive notifications that are propagated upon certain triggering events, e.g., actions performed by one or more of the recipients.
  • the graphical user interface may be implemented as a notification utility within corresponding collaborative process application or as an application that can be executed independent of, or in conjunction with the associated collaborative process application.
  • the interface may be configured to allow the originator to select which types of triggering events will result in the propagation of a notification, and/or what type of display transformation the originator would like to see to serve as visual indicia of the notification, examples of which shall be described in greater detail herein.
  • the computer system 100 comprises a plurality of hardware processing devices, designated generally by the reference 102 that are linked together by a network 104 .
  • Typical processing devices 102 may include servers, personal computers, notebook computers, transactional systems, purpose-driven appliances, pervasive computing devices such as a personal data assistant (PDA), cellular access processing devices, special purpose computing devices, printing and imaging devices, facsimile devices, storage devices and/or other devices capable of communicating over the network 104 .
  • PDA personal data assistant
  • the processing devices 102 may execute software, including, for example, applications and/or other code that process information stored in various databases, spreadsheets, structured documents, unstructured documents and/or other files containing information.
  • the network 104 provides communications links between the various processing devices 102 , and may be supported by networking components 106 that interconnect the processing devices 102 , including for example, routers, hubs, firewalls, network interfaces wired or wireless communications links and corresponding interconnections. Moreover, the network 104 may comprise connections using one or more intranets, extranets, local area networks (LAN), wide area networks (WAN), wireless networks (WIFI), the Internet, including the world wide web, and/or other arrangements for enabling communication between the processing devices 102 , in either real time or otherwise, e.g., via time shifting, batch processing, etc.
  • the system 100 is shown by way of illustration, and not by way of limitation, as a computing environment in which various aspects of the present invention may be practiced.
  • various processing devices 102 may participate in a collaborative environment, which may include one or more shared collaborative process applications, e.g., electronic mail (email) systems capable of creating, sending, receiving, storing or otherwise manipulating messages, electronic calendar systems capable of creating, storing and otherwise manipulating events by order of time and/or date, and to-do systems capable of creating, storing and otherwise manipulating events associated with tasks that are to be completed at some time in the future, i.e., “to-do” tasks.
  • various processing devices 102 may each execute a communications client 108 that facilitates one or more collaborative processes, e.g., email, calendaring, to-do tasks, etc., such as via communication across the network 104 with a corresponding collaborative process server 110 .
  • various collaborative processes may be integrated into the same client 108 , or multiple clients 108 may be required for different collaborative processes.
  • the client 108 may comprise, or interact with a software application that integrates email, calendaring and/or to-do lists.
  • a processing device 102 may include a first client 108 for email, and a second client 108 for a non-email collaborative application, e.g., calendaring, to-do list, etc.
  • the client 108 may comprise a generic software application, e.g., a Web browser.
  • the user may utilize the Web browser to log into an Internet based email/calendaring/to-do application hosted by the collaborative process server 110 , etc.
  • a client 108 may be utilized to implement a graphical user interface to setup, manage and/or monitor notifications, e.g., where such capabilities are not provided within the corresponding shared collaborative process application.
  • a shared collaborative process originator initiates a shared collaborative process by sending an email message to a recipient to request that the recipient perform a task.
  • the originator may have no idea whether the recipient received and read the message or understood its content.
  • the message originator may have no idea whether the recipient performed a task requested within the message, unless the recipient replies to the sender with a status update or message confirmation.
  • the originator may also become impatient and send a follow up message to the recipient. This impatience, although perhaps understandable, is an inefficient utilization of resources.
  • the originator may wish to know that the requested action has been completed.
  • the originator may be content just knowing that that the recipient is working on the requested action. For example, assume that the originator sends an email message to a recipient that requests the recipient to perform an action that will involve others to complete. In this case, a notification may be sent to the originator when a recipient forwards the email message to a third party. The originator is likely to be unconcerned with the details of the forwarded message. Rather, the originator may be content to simply know that the email message has been forwarded on.
  • a user e.g., a shared collaborative process originator, on a first processing device, designated 102 A may communicate, e.g., using a collaborative process, e.g., email message, calendar event, to-do task, via its collaborative process client 108 A with a correspondent, i.e., a recipient, on a second processing device, designated 102 B via the corresponding collaborative process client 108 B across a network 104 .
  • the collaborative process clients 108 A, 108 B may comprise dedicated collaborative process applications or they may execute within a web browser or other application on the corresponding processing clients 108 A, 108 B respectively.
  • collaborative process software 112 may be executed on the collaborative process server 110 , which interacts with a user database 114 and a preferences database 116 .
  • the user database 114 identifies users that may participate in the collaborative process applications supported by the collaborative process server 110 .
  • the user database 114 may also store each user's subscribing peers as well as other user information pertinent to the particular implementation of the collaborative process system. For example, the user database 114 may provide information needed to share collaborative content associated with a collaborative process with other users.
  • the preferences database 116 may be used to enhance user interaction with the collaborative process as will be described in greater detail herein.
  • the preferences stored in the preference database 116 may be characterized in any practical manner.
  • the preferences may be expressed as rules that define how the collaborative process system responds to predetermined events.
  • evaluation of rules in the affirmative and/or in the negative may be used to indicate the occurrence of a triggering event.
  • rules may comprise simple or complex structures.
  • a decision with regard whether or not a triggering event occurred may be determined based upon either complete or incomplete information. For example, a rule may require that each of a number of predicates must be satisfied before determining that a triggering event occurred. Failure of one of the predicates may thus yield a determination that a triggering event has not occurred.
  • the preferences may be organized to include event rules 118 that define one or more triggering events, which, upon the occurrence thereof, may initiate the propagation of a notification, as will be described in detail herein.
  • the preferences may also be organized to include propagation rules 120 , which define conditions for propagating notifications.
  • the propagation rules 120 may first require the occurrence of a predetermined triggering event, e.g., defined by a corresponding event rule 118 before being evaluated, as will be described in greater detail herein.
  • the preferences may also be organized to include transformation rules 122 , which define rules associated with how a propagated notification, i.e., generated if one or more conditions of the propagation rules are met, is displayed to the originator, as will be described in greater detail herein.
  • the collaborative process software 112 may be implemented in any appropriate manner to implement the features and functions set out more fully herein.
  • the collaborative process software 112 is illustrated as having a collaborative process manager 124 for managing aspects of the collaborative process system in a conventional manner, such as by maintaining user lists, e.g., in the user database 114 , facilitating, logging or otherwise enabling collaborative process communications, etc.
  • the method 150 may be implemented, for example, as a computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising computer readable program code configured to implement the steps set out herein with regard to FIG. 3 .
  • An indication is received at 152 , that a collaborative process has been initiated.
  • the method at 152 may comprise receiving, at a collaborative process server computer coupled to a network environment, e.g., collaborative process server 110 , an indication that a user has initiated a computer implemented collaborative process that generates shared collaborative content, wherein the user defines an originator of the generated collaborative content.
  • the collaborative process may comprise, scheduling a shared calendar event, creating an electronic message (email message), initializing a shared to-do task, or other such collaborative process.
  • the initialization may also require some other action, e.g., by designating that the collaborative content is to be tracked so that hints are generated.
  • the originator may also be required to set up preferences, e.g., as described with reference to FIG. 2 . In this regard, the originator may initiate the collaborative process on a processing device, such as the first processing device 102 A.
  • the method 150 detects a designation that events associated with collaborative process are to be tracked at 154 .
  • the step at 154 may comprise obtaining, by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked, where information associated with the collaborative process is stored in a computer storage device accessible by the collaborative process server computer, and the collaborative process server computer is utilized to share the collaborative content associated with the collaborative process with at least one recipient.
  • the collaborative process server 110 executes collaborative process software 112 that interacts with the user database 114 and preferences database 116 , which may be used to distinguish whether the initiated collaborative process is to be tracked, and if so, distinguish events that will trigger propagation of a hint.
  • the originator may optionally designate one or more events associated with the collaborative process to be tracked. This may be done, for example, by selecting an appropriate option associated with the collaborative process in a corresponding graphical user interface.
  • the originator may thus interact with the client 108 , which communicates with the collaborative process software 112 to implement one or more event rules 118 , one or more propagation rules 120 , and/or one or more transformation rules 122 , which event rules 118 , propagation rules 120 , and/or transformation rules 122 are described in greater detail herein.
  • the collaborative content associated with collaborative process is shared with one or more recipients at 156 .
  • the collaborative process server computer may be utilized to share the collaborative content associated with the collaborative process with at least one recipient, e.g., as chosen by the originator.
  • the collaborative process server 110 may use the network 104 to share the collaborative content with one or more clients 108 .
  • Events associated with shared collaborative content are automatically detected at 158 .
  • the method at step 158 may comprise obtaining, by the collaborative process server computer, information identifying the occurrence of computer implemented events associated with the shared collaborative content, where the events are triggered, for example, by activity associated with at least one recipient.
  • the collaborative process server computer itself may detect the occurrence of computer implemented events, e.g., by polling, monitoring or otherwise accessing event information.
  • the collaborative process server may obtain information identifying the occurrence of computer implemented events, e.g., by receiving an indication that an event has occurred, e.g., from an event notification system.
  • events may comprise activity, other than a communication from any of the recipients back to the originator, performed by at least one of the recipients associated with the shared collaborative content, failure to act by one or more recipients within a prescribed time, etc.
  • the types of events that are detected may be specified by the originator using the event rules 118 .
  • the types of detected events may also be specified on a case by case basis. For example, the types of events may be different or the same for the various recipients of the shared collaborative content. Accordingly, the originator may select a first set of event rules 118 for a first recipient, and a second set of event rules 118 for a second recipient, which are the same as, or different from the first set of event rules.
  • the originator may also set different rules across different collaborative process domains. For example, the originator may want to receive hints under a first set of conditions if the triggering activity is email-related, and the originator may want to receive hints under different circumstances if the triggering event is a scheduling of a calendaring event, completion of a to-do task item, etc.
  • a notification of the occurrence of the event is propagated to the originator at 160 .
  • the notification to the originator of the occurrence may not reveal the content or details associated with the event.
  • the step at 160 may comprise propagating a notification of the occurrence of the events to the originator, where the notification of the occurrence may not reveal the content associated with the event(s).
  • a screen display of a corresponding computer processing device which is associated with the originator, is transformed to provide a visual indication of the notification that represents specific information, e.g., makes the originator aware of the happening of the triggering event.
  • conditions associated with the notification including for example, notification delivery format, notification delivery address, etc., may be specified by the originator using the propagation rules 120 .
  • the collaborative process server may utilize operational efficiencies associated with the issuance of notification(s). For example, the process server may annotate, abbreviate, aggregate, or otherwise consolidate one or more events and/or one or more notifications into a single notification message. Moreover, the collaborative process server may delay, batch process or otherwise control the delivery of the notification, e.g., depending upon the mechanisms utilized to detect corresponding events.
  • processing such as may be executed by the collaborative process server, may automatically transform the computer stored information associated with the collaborative process if events associated with the shared collaborative content are detected, e.g., to update a database or other information to designate the occurrence of a triggering event.
  • a display and/or data on a computer processing device associated with the originator are transformed at 162 .
  • the method at 162 may comprise automatically transforming the computer stored information associated with the collaborative process if one or more events associated with the shared collaborative content are detected by propagating a notification of the occurrence of the event(s) to the originator, where the notification of the occurrence may not reveal the content and/or detail associated with the detected event(s).
  • a screen display of a computer processing device associated with the originator is transformed to provide a visual indication of the notification.
  • the transformation of the screen display represents a transformation of the data that represents tangible object(s), i.e., an action or actions carried out in response to a collaborative process, wherein the notification is generated in response to the detected event and is based upon the transformed computer stored information associated with the collaborative process.
  • the type of information automatically transformed may vary depending upon the particular implementation of the collaborative process.
  • the transformation may comprise updating data that is representative of the collaborative process to designate that an event has occurred.
  • the originator may select one or more event rules 118 A, one or more propagation rules 120 A, and one or more transformation rules 122 A for implementation with a tracked collaborative process, e.g., by checking select boxes or making some other designation in a graphical user interface 166 .
  • the graphical user interface 166 may be a component of a corresponding collaborative process application, or the graphical user interface 166 may interact with or otherwise operate in conjunction with corresponding collaborative process application, e.g., by interacting with the collaborative process application on the user's processing device and/or by interacting with the collaborative process server 110 .
  • a computer program product is provided to notify a user of a collaborative process that an event of interest has occurred.
  • the computer program product comprises a computer readable storage medium having computer readable program code embodied therewith.
  • the computer readable program code comprises computer readable program code configured to implement a graphical user interface that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked.
  • the graphical user interface 166 schematically illustrated in FIG. 3A represents that a collaborative process 168 is selected to be tracked.
  • the user of the graphical user interface 166 defines an originator of the generated collaborative content associated with the collaborative process 168 .
  • the graphical user interface 167 graphically interacts with the originator of the collaborative content to designate at least one event that triggers a notification to the originator of the collaborative content, e.g., by setting, selecting, accepting, or otherwise defining or allowing the event or events that will trigger a notification, e.g., via 118 A.
  • the graphical user interface 166 communicates with a collaborative process server computer coupled to a network environment to identify the collaborative process to be tracked and at least one event associated with the collaborative process to monitor.
  • a processing device 102 may execute a client 108 which may comprise the graphical user interface 166 , which can communicate over network 104 to the collaborative process server 110 .
  • the collaborative content is shared with at least one recipient.
  • the computer program product further comprises computer readable program code configured to receive by the graphical user interface, an indication from the collaborative process server computer that at least one designated event has occurred, and computer readable program code configured to cause the graphical user interface to transform a visual display of the shared collaborative content if a designated event associated with the shared collaborative content is detected so as to visually depict the notification of the occurrence of the event to the originator, where the notification of the occurrence may not reveal the details associated with the event.
  • the transformation provides a visual indication of the propagated notification to the originator, to alert the originator of the occurrence of the detected event.
  • Conditions associated with the transformation may be specified by the originator using the transformation rules 122 , as discussed in greater detail herein.
  • a notification box 164 that is visually observable on a graphical user interface 166 associated with collaborative process 168 may be used to designate a notification that one or more events associated with the shared collaborative content have been detected.
  • FIGS. 3A and 3B are presented in simplified schematic fashion by way of illustration and not by way of limitation and are not intended to limit the claimed invention to any particular layout or arrangement of indicia within the graphical user interface.
  • the notification may be visually represented by any visual metaphor, including for example, modification to text, graphics, color, font properties, etc.
  • a project leader within a company may send an email to team members to initiate a collaborative process with regard to a project that must be completed.
  • the project leader may thus define the originator of the collaborative process.
  • the project leader does not need to micromanage the specific details of the work performed by the project team members.
  • the project manager may like to know if team members are working towards the project.
  • triggering events may be defined that trigger a notification to the originator when corresponding triggering events have taken place.
  • the project manager may receive a notification, i.e., hint, that a project team member forwarded a request to a vendor related to the project, etc.
  • the notification to the originator need not carry the details of the vendor request because knowledge that the communication took place may be all that is necessary to the project manager. That is, the project manager may be less interested in the details of the communication, and more interesting in knowing of the occurrence of the email. As yet another example, the project manager may be interested to know that a predetermined period of time has lapsed and the project team member has failed to take a timely action.
  • the project manager may only desire that notifications are propagated upon the instance of certain triggering events taken by one or more of the recipients, but not other events and/or recipients.
  • a notification may be propagated to the originator if the shared collaborative content associated with the collaborative process that is being tracked is forwarded by at least one of the recipients to a new participant.
  • the project manager may not be interested in receiving notifications if the team members are emailing back and forth only to themselves.
  • the project leader may wish to receive a notification, i.e., hint, that a project team member has set up a meeting with a vender, e.g., via the use of a shared electronic calendar, or created a to-do task for the vender that is related to the collaborative process, e.g., via the use of an electronic to-do task system, etc.
  • a notification i.e., hint
  • the notification to the originator need not carry the details of the vendor request, because knowledge that the event, e.g., the creation of the meeting on the electronic calendar or the creation of a to-do task on the electronic to-do task system, took place is all that is necessary to the project manager. Accordingly, hints may be propagated across multiple collaborative process systems.
  • the originator may have initiated the collaborative process via an email message.
  • the process-initiating email my trigger a recipient to schedule an activity on a calendaring system, thus generating the propagation of a hint back to the originator.
  • receipt of the process-initiating email may trigger a recipient to set up a collaborative to-do task, thus triggering the propagation of a hint back to the originator.
  • notification of the triggering events can take any number of forms.
  • the type of display transformation selected by the originator may be, for example, a modification of a representation of the shared collaborative content, such as an “icon” in an associated software application.
  • an originator of collaborative content may be notified of activity associated with the collaborative process by modifying a selected color applied against the sent email in the originator's corresponding folder, e.g., “sent items” folder of the originator's email application.
  • the notification may take other forms such as the delivery of an email message, text message, instant message, etc.
  • one or more recipients may be notified of the tracking of the collaborative content. Further, one or more recipients may have the option to override the propagation of notifications, in which case notifications are not propagated for the originator upon the performance of subsequent triggering events by that recipient. A notice that one or more of the recipients has overridden the propagation of notifications may be propagated to the originator to alert the originator of the override.
  • a collaborative process is initiated by generating an email message authored by an originator at 172 .
  • the email message is initiated to generate collaborative content associated with the email message.
  • the collaborative content may include, for example, a request for one or more recipients to perform one or more tasks.
  • the originator designates that specified triggering events associated with the email message are to be tracked, and those designations are received, e.g., by a collaborative process server at 174 .
  • the triggering events may be specified by the originator by selecting one or more event rules 118 to be implemented using a graphical user interface to the collaborative process software 112 , e.g., as described more fully herein.
  • the triggering events may comprise one or more of deleting the email message that includes the shared collaborative content, overriding the tracking of events associated with the shared collaborative content, or sharing, forwarding, etc. the email message that includes the shared collaborative content.
  • the triggering event may also include other manipulations of the email message, such as copying the content into another software application, such as a word processor, spreadsheet, etc.
  • Sharing an email message containing the shared collaborative content may comprise, for example, forwarding the email message that includes the shared collaborative content to one or more new recipients, forwarding the email message to one or more members identified in the distribution list, e.g., carbon copy (cc), blind carbon copy (bcc), etc.
  • the originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof. For example, the originator may wish to receive notifications that one or more of the recipients forwarded the email message that includes the shared collaborative content to a sub-recipient, but may not wish to receive notification if one or more of the recipients' forwards the email message to a group of other recipients.
  • the originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 176 , e.g., as described in greater detail herein.
  • the originator may use the propagation rules 120 to specify a constraint to the number of hints received over a given period of time when events associated with the tracked collaborative process are detected.
  • the originator may specify, using the propagation rules 120 , that the originator will receive notifications only within a certain time period, e.g., only receive notifications for up to one month after sending the email message, or only receive notifications within certain windows of time, e.g., once one week has elapsed after sending the email message, only during business hours, etc.
  • the propagation rules may also be utilized to set up routing of hints.
  • the rules may specify that hints are to be delivered to the originator's computer during business hours, but after business hours, a text message should be sent to the originator's cellular telephone.
  • the various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • the originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 178 , e.g., at the collaborative process server, e.g., as described more fully herein.
  • the originator may specify, using the transformation rules 122 , that a visual display of a computer processing device is transformed upon the propagation of each notification.
  • the originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the email software application, e.g., a sent email message icon in the originator's sent items folder or a color change of the sent email message in the originator's sent items folder, or a new message that appears on the originator's computer processing device's display, etc.
  • the hint may take different forms depending upon the detected triggering action. For example, if a recipient forwards the email, the hint, e.g., a displayed as an icon, may take a first color, visual appearance, location on the display, etc.
  • an action such as deleting the email may take a different form, color, location, visual representation, etc.
  • forwarding the email only to recipients within the original distribution list(s) may take on a first set of display parameters, whereas forwarding the email to a recipient on an exclude list or otherwise outside the originally listed recipients may trigger the display of the hint using a different set of display parameters.
  • a server computer is used to share the collaborative content associated with the created email message with the one or more recipients specified by the originator at 180 .
  • the same server computer or a different server computer may be used for subsequent sharing of the email message that includes the shared collaborative content, e.g., by one or more of the recipients.
  • the recipients may be given notice that events associated with the email message are to be tracked at 182 .
  • the notice may be, for example, in the form of text in a pop-up message when the email message is opened, an icon associated with the email message, or a specific color of the email message, e.g., in an inbox associated with the one or more recipients.
  • the recipients may be given the option to override or accept the tracking of events associated with the shared collaborative content at 184 .
  • Overriding the tracking of the events may comprise, for example, selecting an appropriate box contained in a pop-up message window on the display device of the recipient's computer processing device.
  • Accepting the tracking may comprise, for example, doing nothing, clearing a notification box, positively acquiescing, etc.
  • triggering events other than a communication back to the originator, e.g., a reply to the originator or a confirmation of a “read-receipt”, performed by the accepting recipients associated with the shared collaborative content are automatically detected at 186 .
  • the triggering events are detected according to the event rules 118 that have been specified by the originator for that particular accepting recipient. That is, a triggering event is automatically detected if the conditions associated with a corresponding event rule 118 , which has been specified by the originator for that particular recipient, are met.
  • a notification of the occurrence of the event is propagated to the originator at 188 . Details in connection with the propagation of the occurrence of the event are specified by the originator at 176 , as discussed above. However, each recipient may be provided with an option to enable sending notifications or disable sending notifications. If one or more recipients indicates the option to disable sending notifications, propagating notifications in connections with events in connection with those recipients are refrained from.
  • the notification to the originator of the occurrence may not reveal the content associated with the event.
  • a notification that any of the recipients has overridden the tracking of events, i.e., at 184 may also be a triggering event by the overriding recipients that propagates a notification at 188 .
  • a display on a computer processing device associated with the originator is transformed at 190 .
  • the transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are specified by the originator at 178 , as discussed above.
  • a collaborative process is initiated by scheduling an event on a shared electronic calendar by an originator at 202 .
  • the scheduled event is initiated to generate collaborative content associated with the scheduled event.
  • the collaborative content may include, for example, a request for one or more recipients to attend one or more scheduled events.
  • the originator designates that specified triggering events associated with the scheduled event are to be tracked, and those designations are received, e.g., by a collaborative process server at 204 , e.g., as described in greater detail herein.
  • the triggering events may comprise one or more of deleting the scheduled event from the recipient's electronic calendar system, overriding the tracking of events associated with the shared collaborative content, flagging or otherwise assigning the scheduled event for a subsequent action or follow-up, accepting the scheduled event, declining the scheduled event, accepting a conflicting scheduled event, or sharing, forwarding, etc. the scheduled event that includes the shared collaborative content.
  • the triggering event may also include other manipulations of the scheduled event, such as copying the content into another software application, such as a word processor, spreadsheet, etc.
  • Sharing the scheduled event that includes the shared collaborative content may comprise, for example, generating the scheduled event that includes the shared collaborative content on the shared electronic calendar of one or more new recipients.
  • the originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof.
  • the originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 206 as described more fully herein.
  • the originator may use the propagation rules 120 to specify a constraint to the number of hints received over a given period of time when events associated with the tracked collaborative process are detected.
  • the originator may specify, using the propagation rules 120 , that the originator will receive notifications only within a certain time period, e.g., only receive notifications for up to one month after scheduling the event, or only receive notifications within certain windows of time, e.g., once one week has elapsed after scheduling the event, only during business hours, etc.
  • the propagation rules may also be utilized to set up routing of hints as described more fully herein.
  • the various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • the originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 208 , e.g., at the collaborative process server, e.g., as described more fully herein.
  • the originator may specify, using the transformation rules 122 , that a visual display of a computer processing device is transformed upon the propagation of each notification.
  • the originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the calendar software application, e.g., a scheduled event icon in the originator's electronic calendar or a color change of the scheduled event icon in the originator's electronic calendar, or a new message that appears on the originator's computer processing device's display, etc.
  • the hint may take different forms depending upon the detected triggering action. For example, if a recipient reassigns the scheduled event to another recipient, the hint, e.g., a displayed as an icon, may take a first color, visual appearance, location on the display, etc. Correspondingly, an action, such as deleting the scheduled event may take a different form, color, location, visual representation, etc.
  • a server computer is used to share the collaborative content associated with the created scheduled event with the one or more recipients specified by the originator at 210 in a manner analogous to that already described herein.
  • the recipients Upon receipt of the scheduled event that includes the shared collaborative content, the recipients are given notice that events associated with the scheduled event are to be tracked at 212 .
  • the recipients may optionally be given the option to override or accept the tracking of events associated with the shared collaborative content at 214 .
  • triggering events performed by the accepting recipients associated with the shared collaborative content are automatically detected at 216 .
  • the triggering events may be detected, for example, according to the event rules 118 that have been specified by the originator for that particular accepting recipient as noted in greater detail herein. That is, a triggering event is automatically detected if the conditions associated with a corresponding event rule 118 , which has been specified by the originator for that particular recipient, are met.
  • a notification of the occurrence of the event is propagated to the originator at 218 . Details in connection with the propagation of the occurrence of the event are specified by the originator at 206 , as discussed above.
  • a display on a computer processing device associated with the originator is transformed at 220 .
  • the transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are discussed in greater detail herein.
  • a collaborative process is initiated by initializing a to-do task by an originator at 252 .
  • the initialized to-do task is initiated to generate collaborative content associated with the to-do task.
  • the collaborative content may include, for example, a request for one or more recipients to perform one or more tasks.
  • the originator designates that specified triggering events associated with the initialized to-do task are to be tracked at 254 , e.g., as described more fully herein.
  • the triggering events may comprise one or more of deleting the initialized to-do task that includes the shared collaborative content, overriding the tracking of events associated with the shared collaborative content, flagging or otherwise assigning the initialized to-do task for a subsequent action or follow-up, accepting the initialized to-do task, declining the initialized to-do task, or sharing, forwarding, etc. the to-do task that includes the shared collaborative content.
  • the triggering event may also include other manipulations of the initialized to-do task, such as copying the content into another software application, such as a word processor, spreadsheet, etc.
  • Sharing the initialized to-do task that includes the shared collaborative content may comprise, for example, re-assigning the initialized to-do task that includes the shared collaborative content to one or more sub-recipients, etc.
  • the sub-recipients may be original recipients of the initialized to-do task that includes the shared collaborative content from the originator, or may not be original recipients of the initialized to-do task that includes the shared collaborative content from the originator.
  • the originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof.
  • the originator may wish to receive notifications that one or more of the recipients re-assigned the initialized to-do task that includes the shared collaborative content to a sub-recipient, but may not wish to receive notification if one or more of the recipients' forwards the initialized to-do task to a group.
  • the originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 256 , e.g., as described more fully herein.
  • the propagation rules may also be utilized to set up routing of hints as described more fully herein.
  • the various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • the originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 258 , e.g., at the collaborative process server.
  • the conditions associated with the transformation may be specified by the originator by selecting one or more transformation rules 122 to be implemented using the collaborative process software 112 , e.g., as described more fully herein.
  • the originator may specify, using the transformation rules 122 , that a visual display of a computer processing device is transformed upon the propagation of each notification.
  • the originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the to-do task software application, e.g., a to-do task icon in the originator's to-do task software application or a color change of the to-do task icon in the originator's to-do task software application, or a new message that appears on the originator's computer processing device's display, etc. Still further, the hint may take different forms depending upon the detected triggering action.
  • a modification of data on the display of the originator's computer processing device e.g., an icon associated with the to-do task software application, e.g., a to-do task icon in the originator's to-do task software application or a color change of the to-do task icon in the originator's to-do task software application, or a new message that appears on the originator's
  • the hint e.g., a displayed as an icon
  • the hint may take a first color, visual appearance, location on the display, etc.
  • an action such as deleting the to-do task may take a different form, color, location, visual representation, etc.
  • a server computer is used to share the collaborative content associated with the initialized to-do task with the one or more recipients specified by the originator at 260 in a manner analogous to that already described herein.
  • the recipients may be given notice that events associated with the to-do task are to be tracked at 262 , and the recipients may optionally be given the option to override or accept the tracking of events associated with the shared collaborative content at 264 , e.g., as described more fully herein.
  • triggering events performed by the accepting recipients associated with the shared collaborative content are automatically detected at 266 .
  • the triggering events may be detected according to the event rules 118 that have been specified by the originator for that particular accepting recipient as noted in greater detail herein. That is, a triggering event may be automatically detected if the conditions associated with a corresponding event rule 118 , which has been specified by the originator for that particular recipient, are met.
  • a notification of the occurrence of the event is propagated to the originator at 268 . Details in connection with the propagation of the occurrence of the event are specified by the originator at 256 , as discussed above.
  • a display on a computer processing device associated with the originator is transformed at 270 .
  • the transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are discussed in greater detail herein.
  • Data processing system 300 such as one of the processing devices 102 or the collaborative process server 110 described with reference to FIG. 1 , may comprise a symmetric multiprocessor (SMP) system or other configuration including a plurality of processors 302 connected to system bus 304 . Alternatively, a single processor 302 may be employed. Also connected to system bus 304 is memory controller/cache 306 , which provides an interface to local memory 308 . An I/O bus bridge 310 is connected to the system bus 204 and provides an interface to an I/O bus 312 .
  • SMP symmetric multiprocessor
  • the I/O bus may be utilized to support one or more busses and corresponding devices 314 , such as bus bridges, input output devices (I/O devices), storage, network adapters, etc.
  • Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks.
  • Also connected to the I/O bus may be devices such as a graphics adapter 316 , storage 318 and a computer usable storage medium 320 having computer usable program code embodied thereon.
  • the computer usable program code may be executed to execute any aspect of the present invention, for example, to implement any aspect of any of the methods and/or system components illustrated in FIGS. 1-6 .
  • the computer usable program code may be utilized to implement the tracking of events, implement the graphical user interface or any other processes that are used to perform the tracking of events as set out further herein.
  • the data processing system depicted in FIG. 7 may be, for example, an IBM RS/6000 system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system.
  • An object oriented programming system such as Java may run in conjunction with the operating system and provides calls to the operating system from Java programs or applications executing on data processing system.
  • aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing
  • the computer readable storage medium comprise for example, a semiconductor or solid state memory, magnetic tape, an electrical connection having one or more wires, a swappable intermediate storage medium such as floppy drive or other removable computer diskette, tape drive, external hard drive, a portable computer diskette, a hard disk, a rigid magnetic disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a read/write (CD-R/W) or digital video disk (DVD), an optical fiber, disk or storage device, or a transmission media such as those supporting the Internet or an intranet.
  • a semiconductor or solid state memory magnetic tape
  • an electrical connection having one or more wires a swappable intermediate storage medium
  • floppy drive or other removable computer diskette such as floppy drive or other removable computer diskette, tape drive, external hard drive, a portable computer diskette, a hard disk, a rigid magnetic disk, a
  • the computer-usable or computer-readable medium may also comprise paper or another suitable medium upon which the program is printed or otherwise encoded, as the program can be captured, for example, via optical scanning of the program on the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
  • the computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave or a carrier signal.
  • the computer usable program code may also be transmitted using any appropriate medium, including but not limited to the Internet, wire line, wireless, optical fiber cable, RF, etc.
  • Computer program code for carrying out operations of the present invention may be written in any suitable language, including for example, an object oriented programming language such as Java, Smalltalk, C++ or the like.
  • the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language, or in higher or lower level programming languages.
  • the program code may execute entirely on a single processing device, partly on one or more different processing devices, as a stand-alone software package or as part of a larger system, partly on a local processing device and partly on a remote processing device or entirely on the remote processing device.
  • the remote processing device may be connected to the local processing device through a network such as a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external processing device, for example, through the Internet using an Internet Service Provider.
  • a network such as a local area network (LAN) or a wide area network (WAN)
  • WAN wide area network
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • the present invention may be practiced on any form of computer system, including a standalone computer or one or more processors participating on a distributed network of computers.
  • computer systems programmed with instructions embodying the methods and/or systems disclosed herein, or computer systems programmed to perform various aspects of the present invention and storage or storing media that store computer readable instructions for converting a general purpose computer into a system based upon the various aspects of the present invention disclosed herein are also considered to be within the scope of the present invention.
  • a computer is programmed to implement the various aspects of the present invention, including the methods of use as set out herein, such computer in effect, becomes a special purpose computer particular to the methods and program structures of this invention. The techniques necessary for this are well known to those skilled in the art of computer systems.
  • one or more blocks in the flowchart or block diagrams may represent a component, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or in the reverse order.

Abstract

Notifications that serve as “hints” related to activity associated with a collaborative process are propagated to an originator to alert the originator of activity on the collaborative process. A collaborative process server computer receives an indication that the originator has initiated a computer implemented collaborative process that generates collaborative content to be tracked. The collaborative process server computer is utilized to share the collaborative content associated with the collaborative process with at least one recipient. Computer implemented event(s) associated with the shared collaborative content by recipients are detected. Information associated with the collaborative process is automatically transformed in response to detected event(s) associated with the shared collaborative content, wherein a notification of the occurrence of the event(s) is propagated to the originator. The notification is generated in response to detected event(s) and is based upon the transformed information.

Description

    BACKGROUND
  • The present invention relates to enhancements of electronic collaborative processes, and in particular, to the propagation of notifications that serve as “hints” related to activity associated with a corresponding collaborative process.
  • Electronic mail (email) systems, electronic calendars and electronic to-do lists are quite popular among computer users, both in business settings and for personal use. However, in email systems, a message originator has relatively little visibility as to how a message recipient handles a received message, including when a particular message is opened or viewed, how messages are prioritized, whether messages that require some type of follow-up action are addressed, and so forth. Similarly, it is typically expected that some sort of activity may be required by the recipient of a shared electronic calendar event and/or shared to-do task. Again however, an event or task originator has relatively little visibility as to when the shared event or task is opened or viewed by the recipient. Still further, the originator has little visibility as to whether the recipient has implemented some type of follow-up action, etc.
  • For messages, events and/or tasks that request that the recipient perform some type of action, the originator and/or recipient must manually take action to track the message, event or task status. For example, the originator may be required to send a follow-up message to the recipient to check on the status of the specific request.
  • BRIEF SUMMARY
  • According to aspects of the present invention, a collaborative process is tracked and a notification of an occurrence of an event is propagated to an originator. A collaborative process server computer having a processor and at least one memory device, and coupled to a network environment receives an indication that a user has initiated a computer implemented collaborative process that generates collaborative content, wherein the user defines an originator of the generated collaborative content. The collaborative process server computer obtains a designation that events associated with the initiated collaborative process are to be tracked. The collaborative content associated with the collaborative process is shared with at least one recipient. The collaborative process server computer obtains information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content, other than a communication from any recipient back to the originator. The information associated with the collaborative process is automatically transformed in response to at least one detected event associated with the shared collaborative content. A notification is propagated to the originator that informs the originator of the detected event. The notification is generated in response to the detected event and is based upon the transformed information.
  • According to further aspects of the present invention, a user of a collaborative process is notified that an event of interest has occurred. A graphical user interface is implemented that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked. The user defines an originator of the generated collaborative content. The graphical user interface graphically interacts with the originator of the collaborative content to designate at least one event that triggers a notification to the originator of the collaborative content. The graphical user interface communicates with a collaborative process server computer coupled to a network environment to identify the collaborative process to be tracked and at least one event associated with the collaborative process to monitor. The collaborative content is shared with at least one recipient. The graphical user interface receives an indication from the collaborative process server computer that at least one designated event has occurred, other than a communication from any recipient back to the originator. The graphical user interface is transformed to modify a visual display of the shared collaborative content if a designated event associated with the shared collaborative content is detected so as to visually depict the notification of the occurrence of the event to the originator.
  • BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
  • FIG. 1 is a schematic illustration of an exemplary system in which computer-implemented event triggered notifications can be electronically generated and/or delivered, where the notifications correspond to hints of activity associated with a corresponding collaborative process;
  • FIG. 2 is block diagram of a system to facilitate computer-implemented event triggered propagation of notifications associated with corresponding tracked collaborative processes, according to various aspects of the present invention;
  • FIG. 3 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with corresponding tracked collaborative processes, according to various aspects of the present invention;
  • FIG. 3A is an illustration of a graphical user interface including exemplary sets of rules to be applied to a collaborative process according to various aspects of the present invention;
  • FIG. 3B is an illustration of a graphical user interface including an exemplary transformation according to various aspects of the present invention;
  • FIG. 4 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked email message according to various aspects of the present invention;
  • FIG. 5 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked electronic calendar event according to various aspects of the present invention;
  • FIG. 6 is a flow chart of a computer-implemented method for electronically propagating notifications that are triggered by events associated with a tracked electronic to-do task according to various aspects of the present invention; and
  • FIG. 7 is a block diagram of an exemplary computer system including a computer usable storage medium having computer usable program code embodied therewith, where the exemplary computer system is capable of executing a computer program product to provide event triggered hints or notifications for communications related to one or more tasks according to various aspects of the present invention.
  • DETAILED DESCRIPTION
  • According to various aspects of the present invention, methods, computer program products and systems are provided for the propagation of notifications, also referred to herein as “hints”, which are triggered by detecting the occurrence of one or more events associated with a shared collaborative process. The propagated hints alert an originator of the shared collaborative process as to the occurrence of the associated triggering event(s) in a manner that may not reveal the specific details of the associated triggering event(s). That is, the hints are propagated to inform the originator that a triggering event has occurred, e.g., an assigned task is being worked on, a follow-up meeting has been scheduled, etc., without requiring the originator of the shared collaborative process to micro-manage the details of those events or to otherwise proactively monitor the status of the corresponding shared collaborative process.
  • Moreover, the generation of hints may be automated or semi-automated in a manner that eliminates, substantially eliminates, simplifies or otherwise reduces the interaction required by the shared collaborative process recipient in order for the originator to receive the hint. The ability to automatically track triggering events thus allows automated “overview level” management in a manner that does not require the originator to expend significant resources on follow-ups for situations where a recipient is taking steps to implement an action associated with the shared collaborative process.
  • Each hint received by the originator identifies the occurrence of one or more events of interest that are associated with a corresponding collaborative process. In this regard, events may be positive actions, e.g., activity carried out by a recipient, such as forwarding a communication associated with the corresponding collaborative process. An event may also comprise a negative action or omission of an anticipated action, such as a failure of a recipient to take an action within a prescribed period of time. Regardless, each hint contains sufficient information to allow the corresponding originator to at least identify that the associated event has occurred.
  • According to aspects of the invention, the originator of a collaborative process may interact with a graphical user interface to configure the manner in which the hints are, or are not, conveyed. As a few illustrative examples, the collaborative process originator may select an option within the graphical user interface to receive notifications that are propagated upon certain triggering events, e.g., actions performed by one or more of the recipients. In this regard, the graphical user interface may be implemented as a notification utility within corresponding collaborative process application or as an application that can be executed independent of, or in conjunction with the associated collaborative process application. Regardless, the interface may be configured to allow the originator to select which types of triggering events will result in the propagation of a notification, and/or what type of display transformation the originator would like to see to serve as visual indicia of the notification, examples of which shall be described in greater detail herein.
  • Referring now to the drawings and particularly to FIG. 1, a general diagram of a computer system 100 is illustrated. The computer system 100 comprises a plurality of hardware processing devices, designated generally by the reference 102 that are linked together by a network 104. Typical processing devices 102 may include servers, personal computers, notebook computers, transactional systems, purpose-driven appliances, pervasive computing devices such as a personal data assistant (PDA), cellular access processing devices, special purpose computing devices, printing and imaging devices, facsimile devices, storage devices and/or other devices capable of communicating over the network 104. The processing devices 102 may execute software, including, for example, applications and/or other code that process information stored in various databases, spreadsheets, structured documents, unstructured documents and/or other files containing information.
  • The network 104 provides communications links between the various processing devices 102, and may be supported by networking components 106 that interconnect the processing devices 102, including for example, routers, hubs, firewalls, network interfaces wired or wireless communications links and corresponding interconnections. Moreover, the network 104 may comprise connections using one or more intranets, extranets, local area networks (LAN), wide area networks (WAN), wireless networks (WIFI), the Internet, including the world wide web, and/or other arrangements for enabling communication between the processing devices 102, in either real time or otherwise, e.g., via time shifting, batch processing, etc. The system 100 is shown by way of illustration, and not by way of limitation, as a computing environment in which various aspects of the present invention may be practiced.
  • As illustrated, various processing devices 102 may participate in a collaborative environment, which may include one or more shared collaborative process applications, e.g., electronic mail (email) systems capable of creating, sending, receiving, storing or otherwise manipulating messages, electronic calendar systems capable of creating, storing and otherwise manipulating events by order of time and/or date, and to-do systems capable of creating, storing and otherwise manipulating events associated with tasks that are to be completed at some time in the future, i.e., “to-do” tasks. For example, various processing devices 102 may each execute a communications client 108 that facilitates one or more collaborative processes, e.g., email, calendaring, to-do tasks, etc., such as via communication across the network 104 with a corresponding collaborative process server 110.
  • In practice, various collaborative processes may be integrated into the same client 108, or multiple clients 108 may be required for different collaborative processes. For example, the client 108 may comprise, or interact with a software application that integrates email, calendaring and/or to-do lists. Alternatively, a processing device 102 may include a first client 108 for email, and a second client 108 for a non-email collaborative application, e.g., calendaring, to-do list, etc.
  • Still further, the client 108 may comprise a generic software application, e.g., a Web browser. In this regard, the user may utilize the Web browser to log into an Internet based email/calendaring/to-do application hosted by the collaborative process server 110, etc. Still further, a client 108 may be utilized to implement a graphical user interface to setup, manage and/or monitor notifications, e.g., where such capabilities are not provided within the corresponding shared collaborative process application.
  • Although collaborative process systems provide a number of conveniences, the courtesies typically used in collaborative process systems does not always align with the demands of busy individuals. To illustrate, assume that a shared collaborative process originator initiates a shared collaborative process by sending an email message to a recipient to request that the recipient perform a task. The originator may have no idea whether the recipient received and read the message or understood its content. Moreover, the message originator may have no idea whether the recipient performed a task requested within the message, unless the recipient replies to the sender with a status update or message confirmation. In the event that the originator is anxious to know the status of the requested task, the originator may also become impatient and send a follow up message to the recipient. This impatience, although perhaps understandable, is an inefficient utilization of resources.
  • Keeping with the above-example, under certain circumstances, the originator may wish to know that the requested action has been completed. Under different circumstances, the originator may be content just knowing that that the recipient is working on the requested action. For example, assume that the originator sends an email message to a recipient that requests the recipient to perform an action that will involve others to complete. In this case, a notification may be sent to the originator when a recipient forwards the email message to a third party. The originator is likely to be unconcerned with the details of the forwarded message. Rather, the originator may be content to simply know that the email message has been forwarded on.
  • Referring to FIG. 2, according to aspects of the present invention, a user, e.g., a shared collaborative process originator, on a first processing device, designated 102A may communicate, e.g., using a collaborative process, e.g., email message, calendar event, to-do task, via its collaborative process client 108A with a correspondent, i.e., a recipient, on a second processing device, designated 102B via the corresponding collaborative process client 108B across a network 104. For example, the collaborative process clients 108A, 108B may comprise dedicated collaborative process applications or they may execute within a web browser or other application on the corresponding processing clients 108A, 108B respectively.
  • In this regard, collaborative process software 112 may be executed on the collaborative process server 110, which interacts with a user database 114 and a preferences database 116. The user database 114 identifies users that may participate in the collaborative process applications supported by the collaborative process server 110. The user database 114 may also store each user's subscribing peers as well as other user information pertinent to the particular implementation of the collaborative process system. For example, the user database 114 may provide information needed to share collaborative content associated with a collaborative process with other users.
  • The preferences database 116 may be used to enhance user interaction with the collaborative process as will be described in greater detail herein. The preferences stored in the preference database 116 may be characterized in any practical manner. For example, the preferences may be expressed as rules that define how the collaborative process system responds to predetermined events. Moreover, evaluation of rules in the affirmative and/or in the negative may be used to indicate the occurrence of a triggering event. Additionally, rules may comprise simple or complex structures. Still further, a decision with regard whether or not a triggering event occurred may be determined based upon either complete or incomplete information. For example, a rule may require that each of a number of predicates must be satisfied before determining that a triggering event occurred. Failure of one of the predicates may thus yield a determination that a triggering event has not occurred.
  • The preferences may be organized to include event rules 118 that define one or more triggering events, which, upon the occurrence thereof, may initiate the propagation of a notification, as will be described in detail herein. The preferences may also be organized to include propagation rules 120, which define conditions for propagating notifications. The propagation rules 120 may first require the occurrence of a predetermined triggering event, e.g., defined by a corresponding event rule 118 before being evaluated, as will be described in greater detail herein. The preferences may also be organized to include transformation rules 122, which define rules associated with how a propagated notification, i.e., generated if one or more conditions of the propagation rules are met, is displayed to the originator, as will be described in greater detail herein.
  • The collaborative process software 112 may be implemented in any appropriate manner to implement the features and functions set out more fully herein. For purposes of illustration, and not by way of limitation, the collaborative process software 112 is illustrated as having a collaborative process manager 124 for managing aspects of the collaborative process system in a conventional manner, such as by maintaining user lists, e.g., in the user database 114, facilitating, logging or otherwise enabling collaborative process communications, etc.
  • Referring now to FIG. 3, a method 150 of tracking a collaborative process is illustrated according to various aspects of the present invention. The method 150 may be implemented, for example, as a computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising computer readable program code configured to implement the steps set out herein with regard to FIG. 3.
  • An indication is received at 152, that a collaborative process has been initiated. For example, the method at 152 may comprise receiving, at a collaborative process server computer coupled to a network environment, e.g., collaborative process server 110, an indication that a user has initiated a computer implemented collaborative process that generates shared collaborative content, wherein the user defines an originator of the generated collaborative content.
  • As a few exemplary illustrations, the collaborative process may comprise, scheduling a shared calendar event, creating an electronic message (email message), initializing a shared to-do task, or other such collaborative process. The initialization may also require some other action, e.g., by designating that the collaborative content is to be tracked so that hints are generated. The originator may also be required to set up preferences, e.g., as described with reference to FIG. 2. In this regard, the originator may initiate the collaborative process on a processing device, such as the first processing device 102A.
  • Further, the method 150 detects a designation that events associated with collaborative process are to be tracked at 154. For example, the step at 154 may comprise obtaining, by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked, where information associated with the collaborative process is stored in a computer storage device accessible by the collaborative process server computer, and the collaborative process server computer is utilized to share the collaborative content associated with the collaborative process with at least one recipient.
  • By way of illustration, as shown in FIG. 2, the collaborative process server 110 executes collaborative process software 112 that interacts with the user database 114 and preferences database 116, which may be used to distinguish whether the initiated collaborative process is to be tracked, and if so, distinguish events that will trigger propagation of a hint. For example, the originator may optionally designate one or more events associated with the collaborative process to be tracked. This may be done, for example, by selecting an appropriate option associated with the collaborative process in a corresponding graphical user interface. The originator may thus interact with the client 108, which communicates with the collaborative process software 112 to implement one or more event rules 118, one or more propagation rules 120, and/or one or more transformation rules 122, which event rules 118, propagation rules 120, and/or transformation rules 122 are described in greater detail herein.
  • The collaborative content associated with collaborative process is shared with one or more recipients at 156. For example, the collaborative process server computer may be utilized to share the collaborative content associated with the collaborative process with at least one recipient, e.g., as chosen by the originator. Thus, for instance, the collaborative process server 110 may use the network 104 to share the collaborative content with one or more clients 108.
  • Events associated with shared collaborative content are automatically detected at 158. For example, the method at step 158 may comprise obtaining, by the collaborative process server computer, information identifying the occurrence of computer implemented events associated with the shared collaborative content, where the events are triggered, for example, by activity associated with at least one recipient. By way of illustration and not by way of limitation, the collaborative process server computer itself may detect the occurrence of computer implemented events, e.g., by polling, monitoring or otherwise accessing event information. As another illustrative example, the collaborative process server may obtain information identifying the occurrence of computer implemented events, e.g., by receiving an indication that an event has occurred, e.g., from an event notification system.
  • As noted in greater detail herein, events may comprise activity, other than a communication from any of the recipients back to the originator, performed by at least one of the recipients associated with the shared collaborative content, failure to act by one or more recipients within a prescribed time, etc. Also, as noted in greater detail herein, the types of events that are detected may be specified by the originator using the event rules 118. The types of detected events may also be specified on a case by case basis. For example, the types of events may be different or the same for the various recipients of the shared collaborative content. Accordingly, the originator may select a first set of event rules 118 for a first recipient, and a second set of event rules 118 for a second recipient, which are the same as, or different from the first set of event rules. The originator may also set different rules across different collaborative process domains. For example, the originator may want to receive hints under a first set of conditions if the triggering activity is email-related, and the originator may want to receive hints under different circumstances if the triggering event is a scheduling of a calendaring event, completion of a to-do task item, etc.
  • Upon the detection of a specified triggering event, e.g., initiated by at least one of the recipients associated with the shared collaborative content, a notification of the occurrence of the event is propagated to the originator at 160. The notification to the originator of the occurrence may not reveal the content or details associated with the event. For example, the step at 160 may comprise propagating a notification of the occurrence of the events to the originator, where the notification of the occurrence may not reveal the content associated with the event(s). As such, a screen display of a corresponding computer processing device, which is associated with the originator, is transformed to provide a visual indication of the notification that represents specific information, e.g., makes the originator aware of the happening of the triggering event. In this regard, as noted in greater detail herein, conditions associated with the notification, including for example, notification delivery format, notification delivery address, etc., may be specified by the originator using the propagation rules 120.
  • Still further, in certain applications, the collaborative process server may utilize operational efficiencies associated with the issuance of notification(s). For example, the process server may annotate, abbreviate, aggregate, or otherwise consolidate one or more events and/or one or more notifications into a single notification message. Moreover, the collaborative process server may delay, batch process or otherwise control the delivery of the notification, e.g., depending upon the mechanisms utilized to detect corresponding events.
  • Moreover, processing, such as may be executed by the collaborative process server, may automatically transform the computer stored information associated with the collaborative process if events associated with the shared collaborative content are detected, e.g., to update a database or other information to designate the occurrence of a triggering event.
  • A display and/or data on a computer processing device associated with the originator are transformed at 162. For example, the method at 162 may comprise automatically transforming the computer stored information associated with the collaborative process if one or more events associated with the shared collaborative content are detected by propagating a notification of the occurrence of the event(s) to the originator, where the notification of the occurrence may not reveal the content and/or detail associated with the detected event(s). Thus, a screen display of a computer processing device associated with the originator is transformed to provide a visual indication of the notification. In this regard, the transformation of the screen display represents a transformation of the data that represents tangible object(s), i.e., an action or actions carried out in response to a collaborative process, wherein the notification is generated in response to the detected event and is based upon the transformed computer stored information associated with the collaborative process. The type of information automatically transformed may vary depending upon the particular implementation of the collaborative process. For example, the transformation may comprise updating data that is representative of the collaborative process to designate that an event has occurred.
  • Referring to FIG. 3A, by way of illustration and not limitation, the originator may select one or more event rules 118A, one or more propagation rules 120A, and one or more transformation rules 122A for implementation with a tracked collaborative process, e.g., by checking select boxes or making some other designation in a graphical user interface 166. The graphical user interface 166 may be a component of a corresponding collaborative process application, or the graphical user interface 166 may interact with or otherwise operate in conjunction with corresponding collaborative process application, e.g., by interacting with the collaborative process application on the user's processing device and/or by interacting with the collaborative process server 110.
  • According to various aspects of the present invention, a computer program product is provided to notify a user of a collaborative process that an event of interest has occurred. The computer program product comprises a computer readable storage medium having computer readable program code embodied therewith.
  • In this regard, the computer readable program code comprises computer readable program code configured to implement a graphical user interface that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked. For example, the graphical user interface 166 schematically illustrated in FIG. 3A represents that a collaborative process 168 is selected to be tracked. Under this configuration, the user of the graphical user interface 166 defines an originator of the generated collaborative content associated with the collaborative process 168. The graphical user interface 167 graphically interacts with the originator of the collaborative content to designate at least one event that triggers a notification to the originator of the collaborative content, e.g., by setting, selecting, accepting, or otherwise defining or allowing the event or events that will trigger a notification, e.g., via 118A.
  • The graphical user interface 166 communicates with a collaborative process server computer coupled to a network environment to identify the collaborative process to be tracked and at least one event associated with the collaborative process to monitor. For example, as illustrated in FIGS. 1 and 2, a processing device 102 may execute a client 108 which may comprise the graphical user interface 166, which can communicate over network 104 to the collaborative process server 110. In response thereto, the collaborative content is shared with at least one recipient.
  • The computer program product further comprises computer readable program code configured to receive by the graphical user interface, an indication from the collaborative process server computer that at least one designated event has occurred, and computer readable program code configured to cause the graphical user interface to transform a visual display of the shared collaborative content if a designated event associated with the shared collaborative content is detected so as to visually depict the notification of the occurrence of the event to the originator, where the notification of the occurrence may not reveal the details associated with the event.
  • The transformation provides a visual indication of the propagated notification to the originator, to alert the originator of the occurrence of the detected event. Conditions associated with the transformation may be specified by the originator using the transformation rules 122, as discussed in greater detail herein. By way of illustration and not limitation, referring to FIG. 3B, a notification box 164 that is visually observable on a graphical user interface 166 associated with collaborative process 168 may be used to designate a notification that one or more events associated with the shared collaborative content have been detected.
  • In this regard, FIGS. 3A and 3B are presented in simplified schematic fashion by way of illustration and not by way of limitation and are not intended to limit the claimed invention to any particular layout or arrangement of indicia within the graphical user interface. Moreover, the notification may be visually represented by any visual metaphor, including for example, modification to text, graphics, color, font properties, etc.
  • By way of illustration, and not by way of limitation, a project leader within a company may send an email to team members to initiate a collaborative process with regard to a project that must be completed. The project leader may thus define the originator of the collaborative process. The project leader does not need to micromanage the specific details of the work performed by the project team members. However, the project manager may like to know if team members are working towards the project. According to various aspects of the invention, triggering events may be defined that trigger a notification to the originator when corresponding triggering events have taken place. For example, the project manager may receive a notification, i.e., hint, that a project team member forwarded a request to a vendor related to the project, etc.
  • In this regard, the notification to the originator need not carry the details of the vendor request because knowledge that the communication took place may be all that is necessary to the project manager. That is, the project manager may be less interested in the details of the communication, and more interesting in knowing of the occurrence of the email. As yet another example, the project manager may be interested to know that a predetermined period of time has lapsed and the project team member has failed to take a timely action.
  • In this regard, as yet another illustrative example, the project manager may only desire that notifications are propagated upon the instance of certain triggering events taken by one or more of the recipients, but not other events and/or recipients. By way of illustration, a notification may be propagated to the originator if the shared collaborative content associated with the collaborative process that is being tracked is forwarded by at least one of the recipients to a new participant. However, the project manager may not be interested in receiving notifications if the team members are emailing back and forth only to themselves.
  • Additionally, the project leader may wish to receive a notification, i.e., hint, that a project team member has set up a meeting with a vender, e.g., via the use of a shared electronic calendar, or created a to-do task for the vender that is related to the collaborative process, e.g., via the use of an electronic to-do task system, etc. Once again, the notification to the originator need not carry the details of the vendor request, because knowledge that the event, e.g., the creation of the meeting on the electronic calendar or the creation of a to-do task on the electronic to-do task system, took place is all that is necessary to the project manager. Accordingly, hints may be propagated across multiple collaborative process systems. That is, the originator may have initiated the collaborative process via an email message. The process-initiating email my trigger a recipient to schedule an activity on a calendaring system, thus generating the propagation of a hint back to the originator. As yet a further example, receipt of the process-initiating email may trigger a recipient to set up a collaborative to-do task, thus triggering the propagation of a hint back to the originator.
  • According to further aspects of the present invention, notification of the triggering events can take any number of forms. The type of display transformation selected by the originator may be, for example, a modification of a representation of the shared collaborative content, such as an “icon” in an associated software application. Thus, for example, an originator of collaborative content may be notified of activity associated with the collaborative process by modifying a selected color applied against the sent email in the originator's corresponding folder, e.g., “sent items” folder of the originator's email application. Still further, the notification may take other forms such as the delivery of an email message, text message, instant message, etc.
  • According to still further aspects of the invention, upon receipt of the shared collaborative content associated with the collaborative process that is to be tracked, one or more recipients may be notified of the tracking of the collaborative content. Further, one or more recipients may have the option to override the propagation of notifications, in which case notifications are not propagated for the originator upon the performance of subsequent triggering events by that recipient. A notice that one or more of the recipients has overridden the propagation of notifications may be propagated to the originator to alert the originator of the override.
  • Referring now to FIG. 4, a flow chart 170 illustrating exemplary steps for carrying out an aspect of the invention is shown. In this example, a collaborative process is initiated by generating an email message authored by an originator at 172. The email message is initiated to generate collaborative content associated with the email message. The collaborative content may include, for example, a request for one or more recipients to perform one or more tasks.
  • The originator designates that specified triggering events associated with the email message are to be tracked, and those designations are received, e.g., by a collaborative process server at 174. The triggering events may be specified by the originator by selecting one or more event rules 118 to be implemented using a graphical user interface to the collaborative process software 112, e.g., as described more fully herein.
  • By way of illustration and not limitation, the triggering events may comprise one or more of deleting the email message that includes the shared collaborative content, overriding the tracking of events associated with the shared collaborative content, or sharing, forwarding, etc. the email message that includes the shared collaborative content. The triggering event may also include other manipulations of the email message, such as copying the content into another software application, such as a word processor, spreadsheet, etc. Sharing an email message containing the shared collaborative content may comprise, for example, forwarding the email message that includes the shared collaborative content to one or more new recipients, forwarding the email message to one or more members identified in the distribution list, e.g., carbon copy (cc), blind carbon copy (bcc), etc.
  • The originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof. For example, the originator may wish to receive notifications that one or more of the recipients forwarded the email message that includes the shared collaborative content to a sub-recipient, but may not wish to receive notification if one or more of the recipients' forwards the email message to a group of other recipients.
  • The originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 176, e.g., as described in greater detail herein. By way of illustration and not limitation, the originator may use the propagation rules 120 to specify a constraint to the number of hints received over a given period of time when events associated with the tracked collaborative process are detected. Further, the originator may specify, using the propagation rules 120, that the originator will receive notifications only within a certain time period, e.g., only receive notifications for up to one month after sending the email message, or only receive notifications within certain windows of time, e.g., once one week has elapsed after sending the email message, only during business hours, etc.
  • The propagation rules may also be utilized to set up routing of hints. For example, the rules may specify that hints are to be delivered to the originator's computer during business hours, but after business hours, a text message should be sent to the originator's cellular telephone. The various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • The originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 178, e.g., at the collaborative process server, e.g., as described more fully herein. By way of illustration and not limitation, the originator may specify, using the transformation rules 122, that a visual display of a computer processing device is transformed upon the propagation of each notification. The originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the email software application, e.g., a sent email message icon in the originator's sent items folder or a color change of the sent email message in the originator's sent items folder, or a new message that appears on the originator's computer processing device's display, etc. Still further, the hint may take different forms depending upon the detected triggering action. For example, if a recipient forwards the email, the hint, e.g., a displayed as an icon, may take a first color, visual appearance, location on the display, etc. Correspondingly, an action, such as deleting the email may take a different form, color, location, visual representation, etc. As another example, forwarding the email only to recipients within the original distribution list(s) may take on a first set of display parameters, whereas forwarding the email to a recipient on an exclude list or otherwise outside the originally listed recipients may trigger the display of the hint using a different set of display parameters.
  • A server computer is used to share the collaborative content associated with the created email message with the one or more recipients specified by the originator at 180. The same server computer or a different server computer may be used for subsequent sharing of the email message that includes the shared collaborative content, e.g., by one or more of the recipients.
  • Upon receipt of the email message that includes the shared collaborative content, the recipients may be given notice that events associated with the email message are to be tracked at 182. The notice may be, for example, in the form of text in a pop-up message when the email message is opened, an icon associated with the email message, or a specific color of the email message, e.g., in an inbox associated with the one or more recipients.
  • If a notification is given, then the recipients may be given the option to override or accept the tracking of events associated with the shared collaborative content at 184. Overriding the tracking of the events may comprise, for example, selecting an appropriate box contained in a pop-up message window on the display device of the recipient's computer processing device. Accepting the tracking may comprise, for example, doing nothing, clearing a notification box, positively acquiescing, etc.
  • If one or more of the recipients accept the tracking of events at 184, triggering events, other than a communication back to the originator, e.g., a reply to the originator or a confirmation of a “read-receipt”, performed by the accepting recipients associated with the shared collaborative content are automatically detected at 186. The triggering events are detected according to the event rules 118 that have been specified by the originator for that particular accepting recipient. That is, a triggering event is automatically detected if the conditions associated with a corresponding event rule 118, which has been specified by the originator for that particular recipient, are met.
  • Upon the detection of a triggering event corresponding to an event rule 118 by one of the accepting recipients, a notification of the occurrence of the event is propagated to the originator at 188. Details in connection with the propagation of the occurrence of the event are specified by the originator at 176, as discussed above. However, each recipient may be provided with an option to enable sending notifications or disable sending notifications. If one or more recipients indicates the option to disable sending notifications, propagating notifications in connections with events in connection with those recipients are refrained from.
  • As noted above, the notification to the originator of the occurrence may not reveal the content associated with the event. Also, a notification that any of the recipients has overridden the tracking of events, i.e., at 184, may also be a triggering event by the overriding recipients that propagates a notification at 188.
  • A display on a computer processing device associated with the originator is transformed at 190. The transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are specified by the originator at 178, as discussed above.
  • Referring now to FIG. 5, a flow chart 200 illustrating exemplary steps for carrying out another aspect of the invention is shown. In this example, a collaborative process is initiated by scheduling an event on a shared electronic calendar by an originator at 202. The scheduled event is initiated to generate collaborative content associated with the scheduled event. The collaborative content may include, for example, a request for one or more recipients to attend one or more scheduled events.
  • The originator designates that specified triggering events associated with the scheduled event are to be tracked, and those designations are received, e.g., by a collaborative process server at 204, e.g., as described in greater detail herein. By way of illustration and not limitation, the triggering events may comprise one or more of deleting the scheduled event from the recipient's electronic calendar system, overriding the tracking of events associated with the shared collaborative content, flagging or otherwise assigning the scheduled event for a subsequent action or follow-up, accepting the scheduled event, declining the scheduled event, accepting a conflicting scheduled event, or sharing, forwarding, etc. the scheduled event that includes the shared collaborative content. The triggering event may also include other manipulations of the scheduled event, such as copying the content into another software application, such as a word processor, spreadsheet, etc.
  • Sharing the scheduled event that includes the shared collaborative content may comprise, for example, generating the scheduled event that includes the shared collaborative content on the shared electronic calendar of one or more new recipients. The originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof.
  • The originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 206 as described more fully herein. By way of illustration and not limitation, the originator may use the propagation rules 120 to specify a constraint to the number of hints received over a given period of time when events associated with the tracked collaborative process are detected. Further, the originator may specify, using the propagation rules 120, that the originator will receive notifications only within a certain time period, e.g., only receive notifications for up to one month after scheduling the event, or only receive notifications within certain windows of time, e.g., once one week has elapsed after scheduling the event, only during business hours, etc.
  • The propagation rules may also be utilized to set up routing of hints as described more fully herein. The various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • The originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 208, e.g., at the collaborative process server, e.g., as described more fully herein. By way of illustration and not limitation, the originator may specify, using the transformation rules 122, that a visual display of a computer processing device is transformed upon the propagation of each notification. The originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the calendar software application, e.g., a scheduled event icon in the originator's electronic calendar or a color change of the scheduled event icon in the originator's electronic calendar, or a new message that appears on the originator's computer processing device's display, etc. Still further, the hint may take different forms depending upon the detected triggering action. For example, if a recipient reassigns the scheduled event to another recipient, the hint, e.g., a displayed as an icon, may take a first color, visual appearance, location on the display, etc. Correspondingly, an action, such as deleting the scheduled event may take a different form, color, location, visual representation, etc.
  • A server computer is used to share the collaborative content associated with the created scheduled event with the one or more recipients specified by the originator at 210 in a manner analogous to that already described herein.
  • Upon receipt of the scheduled event that includes the shared collaborative content, the recipients are given notice that events associated with the scheduled event are to be tracked at 212. The recipients may optionally be given the option to override or accept the tracking of events associated with the shared collaborative content at 214.
  • If one or more of the recipients accept the tracking of events at 214, triggering events performed by the accepting recipients associated with the shared collaborative content are automatically detected at 216. The triggering events may be detected, for example, according to the event rules 118 that have been specified by the originator for that particular accepting recipient as noted in greater detail herein. That is, a triggering event is automatically detected if the conditions associated with a corresponding event rule 118, which has been specified by the originator for that particular recipient, are met.
  • Upon the detection of a triggering event corresponding to an event rule 118 by one of the accepting recipients, a notification of the occurrence of the event is propagated to the originator at 218. Details in connection with the propagation of the occurrence of the event are specified by the originator at 206, as discussed above.
  • A display on a computer processing device associated with the originator is transformed at 220. The transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are discussed in greater detail herein.
  • Referring now to FIG. 6, a flow chart 250 illustrating exemplary steps for carrying out yet another aspect of the invention is shown. In this example, a collaborative process is initiated by initializing a to-do task by an originator at 252. The initialized to-do task is initiated to generate collaborative content associated with the to-do task. The collaborative content may include, for example, a request for one or more recipients to perform one or more tasks.
  • The originator designates that specified triggering events associated with the initialized to-do task are to be tracked at 254, e.g., as described more fully herein. By way of illustration and not limitation, the triggering events may comprise one or more of deleting the initialized to-do task that includes the shared collaborative content, overriding the tracking of events associated with the shared collaborative content, flagging or otherwise assigning the initialized to-do task for a subsequent action or follow-up, accepting the initialized to-do task, declining the initialized to-do task, or sharing, forwarding, etc. the to-do task that includes the shared collaborative content. The triggering event may also include other manipulations of the initialized to-do task, such as copying the content into another software application, such as a word processor, spreadsheet, etc.
  • Sharing the initialized to-do task that includes the shared collaborative content may comprise, for example, re-assigning the initialized to-do task that includes the shared collaborative content to one or more sub-recipients, etc. The sub-recipients may be original recipients of the initialized to-do task that includes the shared collaborative content from the originator, or may not be original recipients of the initialized to-do task that includes the shared collaborative content from the originator. The originator may use the collaborative process software 112 to specify which types of events are to be detected, and may also specify which of the recipients to track the events thereof. For example, the originator may wish to receive notifications that one or more of the recipients re-assigned the initialized to-do task that includes the shared collaborative content to a sub-recipient, but may not wish to receive notification if one or more of the recipients' forwards the initialized to-do task to a group.
  • The originator may use the collaborative process software 112 to specify conditions associated with the propagation of notifications, which are received, e.g., by the collaborative process server at 256, e.g., as described more fully herein.
  • The propagation rules may also be utilized to set up routing of hints as described more fully herein. The various propagation rules 120 selected by the originator may be the same or different for each selected recipient.
  • The originator may use the collaborative process software 112 to specify conditions associated with the transformation associated with the propagated notifications, and such specifications are received at 258, e.g., at the collaborative process server. The conditions associated with the transformation may be specified by the originator by selecting one or more transformation rules 122 to be implemented using the collaborative process software 112, e.g., as described more fully herein. By way of illustration and not limitation, the originator may specify, using the transformation rules 122, that a visual display of a computer processing device is transformed upon the propagation of each notification.
  • The originator may specify that the transformation of the display takes the form of, for example, a modification of data on the display of the originator's computer processing device, e.g., an icon associated with the to-do task software application, e.g., a to-do task icon in the originator's to-do task software application or a color change of the to-do task icon in the originator's to-do task software application, or a new message that appears on the originator's computer processing device's display, etc. Still further, the hint may take different forms depending upon the detected triggering action. For example, if a recipient reassigns the to-do task to another recipient, the hint, e.g., a displayed as an icon, may take a first color, visual appearance, location on the display, etc. Correspondingly, an action, such as deleting the to-do task may take a different form, color, location, visual representation, etc.
  • A server computer is used to share the collaborative content associated with the initialized to-do task with the one or more recipients specified by the originator at 260 in a manner analogous to that already described herein.
  • Upon receipt of the to-do task that includes the shared collaborative content, the recipients may be given notice that events associated with the to-do task are to be tracked at 262, and the recipients may optionally be given the option to override or accept the tracking of events associated with the shared collaborative content at 264, e.g., as described more fully herein.
  • If one or more of the recipients accept the tracking of events at 264, triggering events performed by the accepting recipients associated with the shared collaborative content are automatically detected at 266. The triggering events may be detected according to the event rules 118 that have been specified by the originator for that particular accepting recipient as noted in greater detail herein. That is, a triggering event may be automatically detected if the conditions associated with a corresponding event rule 118, which has been specified by the originator for that particular recipient, are met.
  • Upon the detection of a triggering event corresponding to an event rule 118 by one of the accepting recipients, a notification of the occurrence of the event is propagated to the originator at 268. Details in connection with the propagation of the occurrence of the event are specified by the originator at 256, as discussed above.
  • A display on a computer processing device associated with the originator is transformed at 270. The transformation provides a visual indication of the notification to the originator, to alert the originator of the occurrence of the event. Details in connection with the transformation are discussed in greater detail herein.
  • Referring to FIG. 7, a block diagram of a data processing system is depicted in accordance with the present invention. Data processing system 300, such as one of the processing devices 102 or the collaborative process server 110 described with reference to FIG. 1, may comprise a symmetric multiprocessor (SMP) system or other configuration including a plurality of processors 302 connected to system bus 304. Alternatively, a single processor 302 may be employed. Also connected to system bus 304 is memory controller/cache 306, which provides an interface to local memory 308. An I/O bus bridge 310 is connected to the system bus 204 and provides an interface to an I/O bus 312. The I/O bus may be utilized to support one or more busses and corresponding devices 314, such as bus bridges, input output devices (I/O devices), storage, network adapters, etc. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks.
  • Also connected to the I/O bus may be devices such as a graphics adapter 316, storage 318 and a computer usable storage medium 320 having computer usable program code embodied thereon. The computer usable program code may be executed to execute any aspect of the present invention, for example, to implement any aspect of any of the methods and/or system components illustrated in FIGS. 1-6. Moreover, the computer usable program code may be utilized to implement the tracking of events, implement the graphical user interface or any other processes that are used to perform the tracking of events as set out further herein.
  • The data processing system depicted in FIG. 7 may be, for example, an IBM RS/6000 system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system. An object oriented programming system such as Java may run in conjunction with the operating system and provides calls to the operating system from Java programs or applications executing on data processing system.
  • As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
  • Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing
  • More specific examples of the computer readable storage medium comprise for example, a semiconductor or solid state memory, magnetic tape, an electrical connection having one or more wires, a swappable intermediate storage medium such as floppy drive or other removable computer diskette, tape drive, external hard drive, a portable computer diskette, a hard disk, a rigid magnetic disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a read/write (CD-R/W) or digital video disk (DVD), an optical fiber, disk or storage device, or a transmission media such as those supporting the Internet or an intranet. The computer-usable or computer-readable medium may also comprise paper or another suitable medium upon which the program is printed or otherwise encoded, as the program can be captured, for example, via optical scanning of the program on the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave or a carrier signal. The computer usable program code may also be transmitted using any appropriate medium, including but not limited to the Internet, wire line, wireless, optical fiber cable, RF, etc.
  • Computer program code for carrying out operations of the present invention may be written in any suitable language, including for example, an object oriented programming language such as Java, Smalltalk, C++ or the like. The computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language, or in higher or lower level programming languages. The program code may execute entirely on a single processing device, partly on one or more different processing devices, as a stand-alone software package or as part of a larger system, partly on a local processing device and partly on a remote processing device or entirely on the remote processing device. In the latter scenario, the remote processing device may be connected to the local processing device through a network such as a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external processing device, for example, through the Internet using an Internet Service Provider.
  • The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus systems and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams may be implemented by system components or computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • The present invention may be practiced on any form of computer system, including a standalone computer or one or more processors participating on a distributed network of computers. Thus, computer systems programmed with instructions embodying the methods and/or systems disclosed herein, or computer systems programmed to perform various aspects of the present invention and storage or storing media that store computer readable instructions for converting a general purpose computer into a system based upon the various aspects of the present invention disclosed herein, are also considered to be within the scope of the present invention. Once a computer is programmed to implement the various aspects of the present invention, including the methods of use as set out herein, such computer in effect, becomes a special purpose computer particular to the methods and program structures of this invention. The techniques necessary for this are well known to those skilled in the art of computer systems.
  • The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, one or more blocks in the flowchart or block diagrams may represent a component, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or in the reverse order.
  • The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
  • The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention.
  • Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims.

Claims (20)

1. A method of tracking a collaborative process and propagating a notification of an occurrence of an event to an originator comprising:
receiving at a collaborative process server computer coupled to a network environment, an indication that a user has initiated a computer implemented collaborative process that generates collaborative content, wherein the user defines an originator of the generated collaborative content;
obtaining by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked;
sharing the collaborative content associated with the collaborative process with at least one recipient;
obtaining by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content other than a communication from any recipient back to the originator;
automatically transforming information associated with the collaborative process in response to at least one detected event associated with the shared collaborative content; and
propagating a notification to the originator that informs the originator of the detected event, wherein the notification is generated in response to the detected event and is based upon the transformed information.
2. The method of claim 1, wherein the notification does not reveal details associated with the detected event.
3. The method of claim 1, wherein obtaining by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content comprises detecting that a recipient has one of:
changed the collaborative content associated with the collaborative process;
added to the collaborative content associated with the collaborative process;
deleted at least a portion of the collaborative content associated with the collaborative process; and
shared the collaborative content associated with the collaborative process.
4. The method of claim 1, further comprising:
evaluating at least one rule to determine at least one of: when and how, a given notification is propagated to the originator.
5. The method of claim 1, wherein:
sharing the collaborative content associated with the collaborative process with at least one recipient further comprises:
providing notice to at least one recipient that events are being tracked to send notifications to the originator; and
providing each recipient that receives the notice with an option to enable sending notifications or disable sending notifications; and
propagating a notification to the originator further comprises:
refraining from propagating the notification if the detected event is associated with a recipient that received the notice and that indicated the option to disable sending notifications.
6. The method of claim 1, wherein propagating a notification of the occurrence of the events to the originator comprises:
sending to a processing device of the originator across the network, at least one of: an electronic instant message and an email message.
7. The method of claim 1, wherein obtaining by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content comprises detecting an event that is associated with a recipient taking an action in a first collaborative process application that is different than the application implemented collaborative process that generates the collaborative content.
8. A computer program product to track a computer implemented collaborative process and propagate a notification of an occurrence of an event to an originator comprising:
a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to receive, at a collaborative process server computer coupled to a network environment, an indication that a user has initiated a computer implemented collaborative process that generates collaborative content, wherein the user defines an originator of the generated collaborative content;
computer readable program code configured to obtain, by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked, wherein information associated with the collaborative process is stored in a computer storage device accessible by the collaborative process server computer, and the collaborative process server computer is utilized to share the collaborative content associated with the collaborative process with at least one recipient;
computer readable program code configured to obtain, by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content other than a communication from any recipient back to the originator;
computer readable program code configured to transform the computer stored information associated with the collaborative process in response to at least one detected event associated with the shared collaborative content; and
computer readable program code configured to propagate a notification to the originator that informs the originator of the detected event, wherein the notification is generated in response to the detected event and is based upon the transformed information.
9. The computer program product of claim 8, wherein the computer readable program code configured to propagate a notification to the originator comprises computer readable program code configured to propagate a notification that does not reveal details associated with the detected event.
10. The computer program product of claim 8, wherein the computer readable program code configured to obtain, by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content comprises computer readable program code configured to detect that a recipient has one of:
changed the collaborative content associated with the collaborative process;
added to the collaborative content associated with the collaborative process;
deleted at least a portion of the collaborative content associated with the collaborative process; and
shared the collaborative content associated with the collaborative process.
11. The computer program product of claim 8, further comprising:
computer readable program code configured to evaluate at least one rule to determine at least one of: when and how, a given notification is propagated to the originator.
12. The computer program product of claim 8, wherein sharing the collaborative content associated with the collaborative process with at least one recipient comprises computer readable program code configured to:
provide notice to at least one recipient that events are being tracked to send notifications to the originator; and
provide each recipient that receives the notice with an option to enable sending notifications or disable sending notifications; and
the computer readable program code configured to propagate a notification to the originator further comprises:
computer readable program code configured to refrain from propagating the notification if the detected event is associated with a recipient that received the notice and that indicated the option to disable sending notifications.
13. The computer program product of claim 8, wherein the computer readable program code configured to propagate a notification of the occurrence of the events to the originator comprises:
computer readable program code configured to send to a processing device of the originator across the network, at least one of: an electronic instant message and an email message.
14. The computer program product of claim 8, wherein the computer readable program code configured to detect by the collaborative process server computer, the occurrence of at least one computer detectable event comprises computer readable program code configured to detect an event that is associated with a recipient taking an action in a first collaborative process application that is different than the application implemented collaborative process that generates the collaborative content.
15. A system to track a collaborative process and propagate a notification of an occurrence of an event to an originator comprising:
a collaborative process server computer having a processor and at least one memory device; and
computer readable program code resident in said at least one memory device, which is executed by said processor comprising:
computer readable program code configured to receive at the server computer, an indication that a user has initiated a computer implemented collaborative process that generates collaborative content, wherein the user defines an originator of the generated collaborative content;
computer readable program code configured to obtain by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked;
computer readable program code configured to share the collaborative content associated with the collaborative process with at least one recipient;
computer readable program code configured to obtain by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared collaborative content other than a communication from any recipient back to the originator;
computer readable program code configured to automatically transform information associated with the collaborative process in response to at least one detected event associated with the shared collaborative content; and
computer readable program code configured to propagate a notification to the originator that informs the originator of the detected event, wherein the notification is generated in response to the detected event and is based upon the transformed information.
16. The system according to claim 15, further comprising:
at least one storage device that stores rules to determine at least one of: when and how, a given notification is propagated to the originator.
17. A computer program product to notify a user of a collaborative process that an event of interest has occurred, comprising:
a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to implement a graphical user interface that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked, wherein the user defines an originator of the generated collaborative content;
computer readable program code configured to implement a portion of the graphical user interface that graphically interacts with the originator of the collaborative content to designate at least one event that triggers a notification to the originator of the collaborative content;
computer readable program code configured to implement a portion of the graphical user interface that communicates with a collaborative process server computer coupled to a network environment to identify the collaborative process to be tracked and at least one event associated with the collaborative process to monitor;
computer readable program code configured to share the collaborative content with at least one recipient;
computer readable program code configured to receive by the graphical user interface, an indication from the collaborative process server computer that at least one designated event has occurred other than a communication from any recipient back to the originator; and
computer readable program code configured to transform the graphical user interface to modify a visual display of the shared collaborative content if a designated event associated with the shared collaborative content is detected so as to visually depict the notification of the occurrence of the event to the originator.
18. The computer program product of claim 17, wherein the computer readable program code configured to implement a graphical user interface comprises computer readable program code configured to implement a graphical user interface that, when executed on a processing device, graphically interacts with a user to identify electronically generated collaborative content of a corresponding computer-executed collaborative process that is to be tracked, the computer-executed collaborative process integrated with the graphical user interface.
19. The computer program product of claim 17, wherein the computer readable program code configured to receive by the graphical user interface, an indication from the collaborative process server computer that at least one designated event has occurred comprises computer readable program code configured to receive by the graphical user interface, an indication from the collaborative process server computer that at least one designated event has occurred that is associated with a recipient taking an action in a first collaborative process application that is different than the corresponding computer-executed collaborative process that is to be tracked.
20. The computer program product of claim 17, wherein the graphical user interface graphically interacts with the originator of the collaborative content to designate at least of:
at least one propagation rule for propagating the notification of the occurrence of the designated event to the originator; and
at least one transformation rule for displaying on a computer processing device associated with the originator the visual depiction of the notification.
US12/507,939 2009-07-23 2009-07-23 Event triggered notifications for collaborative processes Abandoned US20110022662A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US12/507,939 US20110022662A1 (en) 2009-07-23 2009-07-23 Event triggered notifications for collaborative processes
TW099118947A TW201112691A (en) 2009-07-23 2010-06-10 Event triggered notifications for collaborative processes
CN2010800317666A CN102473251A (en) 2009-07-23 2010-07-21 Event triggered notifications for collaborative processes
PCT/EP2010/060584 WO2011009896A1 (en) 2009-07-23 2010-07-21 Event triggered notifications for collaborative processes
US14/826,273 US9813460B2 (en) 2009-07-23 2015-08-14 Event triggered notifications for collaborative processes
US15/602,649 US10015211B2 (en) 2009-07-23 2017-05-23 Event triggered notifications for collaborative processes
US15/967,715 US10320858B2 (en) 2009-07-23 2018-05-01 Event triggered notifications for collaborative processes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/507,939 US20110022662A1 (en) 2009-07-23 2009-07-23 Event triggered notifications for collaborative processes

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/826,273 Division US9813460B2 (en) 2009-07-23 2015-08-14 Event triggered notifications for collaborative processes

Publications (1)

Publication Number Publication Date
US20110022662A1 true US20110022662A1 (en) 2011-01-27

Family

ID=43379016

Family Applications (4)

Application Number Title Priority Date Filing Date
US12/507,939 Abandoned US20110022662A1 (en) 2009-07-23 2009-07-23 Event triggered notifications for collaborative processes
US14/826,273 Expired - Fee Related US9813460B2 (en) 2009-07-23 2015-08-14 Event triggered notifications for collaborative processes
US15/602,649 Active US10015211B2 (en) 2009-07-23 2017-05-23 Event triggered notifications for collaborative processes
US15/967,715 Active US10320858B2 (en) 2009-07-23 2018-05-01 Event triggered notifications for collaborative processes

Family Applications After (3)

Application Number Title Priority Date Filing Date
US14/826,273 Expired - Fee Related US9813460B2 (en) 2009-07-23 2015-08-14 Event triggered notifications for collaborative processes
US15/602,649 Active US10015211B2 (en) 2009-07-23 2017-05-23 Event triggered notifications for collaborative processes
US15/967,715 Active US10320858B2 (en) 2009-07-23 2018-05-01 Event triggered notifications for collaborative processes

Country Status (4)

Country Link
US (4) US20110022662A1 (en)
CN (1) CN102473251A (en)
TW (1) TW201112691A (en)
WO (1) WO2011009896A1 (en)

Cited By (63)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110087764A1 (en) * 2009-10-14 2011-04-14 Dror Yaffe Engine for generating and managing communications concerning on-line collaboration among a plurality of users in consideration with a computerized application
US20120171845A1 (en) * 2011-01-03 2012-07-05 Gt Solar Incorporated Chuck for chemical vapor deposition systems and related methods therefor
US20120311460A1 (en) * 2006-09-02 2012-12-06 John Edward Boyd Computer-Based Methods for Arranging Meetings and Systems for Performing the Same
US20130332813A1 (en) * 2012-06-06 2013-12-12 Sap Ag Generic Workspace Awareness Support for Collaborative Web Applications
CN103957278A (en) * 2014-05-20 2014-07-30 薛厚新 Memo system achieving intelligent reminding within specific geographical range and application method thereof
US20140229594A1 (en) * 2013-02-12 2014-08-14 International Business Machines Corporation Applying policy attachment service level management (slm) semantics within a peered policy enforcement deployment
US9256341B2 (en) 2013-03-20 2016-02-09 Microsoft Technology Licensing, Llc Tracking changes in collaborative authoring environment
US20160337166A1 (en) * 2015-05-14 2016-11-17 Honeywell International Inc. Apparatus and method for automated event notification read receipt to support non-repudiated auditing or other functions in industrial process control and automation system
US20170178000A1 (en) * 2015-12-18 2017-06-22 Sap Se Generation and handling of situation definitions
US9813460B2 (en) 2009-07-23 2017-11-07 International Business Machines Corporation Event triggered notifications for collaborative processes
US20170339249A1 (en) * 2016-05-20 2017-11-23 Microsoft Technology Licensing, Llc Content sharing with user and recipient devices
US9983759B1 (en) * 2012-02-29 2018-05-29 Google Llc Method and system for sharing virtual collaboration objects
US10069782B2 (en) 2016-08-12 2018-09-04 Xenovus Inc. Method and system to facilitate electronic communication between internal teams and external contacts
US10402786B2 (en) 2016-12-30 2019-09-03 Dropbox, Inc. Managing projects in a content management system
US10452670B2 (en) * 2015-03-23 2019-10-22 Dropbox, Inc. Processing message attachments in shared folder backed integrated workspaces
US10693911B2 (en) 2013-02-12 2020-06-23 International Business Machines Corporation Dynamic generation of policy enforcement rules and actions from policy attachment semantics
US10693746B2 (en) 2013-02-12 2020-06-23 International Business Machines Corporation Instrumentation and monitoring of service level agreement (SLA) and service policy enforcement
US10719807B2 (en) 2016-12-29 2020-07-21 Dropbox, Inc. Managing projects using references
US10740357B2 (en) 2015-12-18 2020-08-11 Sap Se Generation and handling of situation objects
US10824787B2 (en) 2013-12-21 2020-11-03 Microsoft Technology Licensing, Llc Authoring through crowdsourcing based suggestions
US10838925B2 (en) 2018-11-06 2020-11-17 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US10942944B2 (en) 2015-12-22 2021-03-09 Dropbox, Inc. Managing content across discrete systems
US10970656B2 (en) 2016-12-29 2021-04-06 Dropbox, Inc. Automatically suggesting project affiliations
US10977242B2 (en) * 2017-09-07 2021-04-13 Atlassian Pty Ltd. Systems and methods for managing designated content items
US11012400B1 (en) * 2020-04-14 2021-05-18 Citrix Systems, Inc. Triggering event notifications based on messages to application users
US20220011911A1 (en) * 2018-05-25 2022-01-13 Palantir Technologies Inc. Interactive display with workflow management system
US11226939B2 (en) 2017-12-29 2022-01-18 Dropbox, Inc. Synchronizing changes within a collaborative content management system
US11263228B2 (en) 2014-11-24 2022-03-01 Asana, Inc. Continuously scrollable calendar user interface
US11290296B2 (en) 2018-06-08 2022-03-29 Asana, Inc. Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users
US11288081B2 (en) 2019-01-08 2022-03-29 Asana, Inc. Systems and methods for determining and presenting a graphical user interface including template metrics
US11327645B2 (en) 2018-04-04 2022-05-10 Asana, Inc. Systems and methods for preloading an amount of content based on user scrolling
US11341445B1 (en) 2019-11-14 2022-05-24 Asana, Inc. Systems and methods to measure and visualize threshold of user workload
US11341444B2 (en) 2018-12-06 2022-05-24 Asana, Inc. Systems and methods for generating prioritization models and predicting workflow prioritizations
US11398998B2 (en) 2018-02-28 2022-07-26 Asana, Inc. Systems and methods for generating tasks based on chat sessions between users of a collaboration environment
US11405435B1 (en) 2020-12-02 2022-08-02 Asana, Inc. Systems and methods to present views of records in chat sessions between users of a collaboration environment
US11449836B1 (en) 2020-07-21 2022-09-20 Asana, Inc. Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment
US11455601B1 (en) 2020-06-29 2022-09-27 Asana, Inc. Systems and methods to measure and visualize workload for completing individual units of work
US11496432B2 (en) * 2020-06-18 2022-11-08 T-Mobile Usa, Inc. Synchronizing message status across multiple user devices
US11514399B2 (en) 2013-12-21 2022-11-29 Microsoft Technology Licensing, Llc Authoring through suggestion
US11526263B2 (en) * 2020-06-09 2022-12-13 Fujifilm Business Innovation Corp. Information processing apparatus and non-transitory computer readable medium
US11553045B1 (en) 2021-04-29 2023-01-10 Asana, Inc. Systems and methods to automatically update status of projects within a collaboration environment
US11561677B2 (en) 2019-01-09 2023-01-24 Asana, Inc. Systems and methods for generating and tracking hardcoded communications in a collaboration management platform
US11568339B2 (en) 2020-08-18 2023-01-31 Asana, Inc. Systems and methods to characterize units of work based on business objectives
US11568366B1 (en) * 2018-12-18 2023-01-31 Asana, Inc. Systems and methods for generating status requests for units of work
US11599855B1 (en) * 2020-02-14 2023-03-07 Asana, Inc. Systems and methods to attribute automated actions within a collaboration environment
US11610053B2 (en) 2017-07-11 2023-03-21 Asana, Inc. Database model which provides management of custom fields and methods and apparatus therfor
US11620615B2 (en) 2018-12-18 2023-04-04 Asana, Inc. Systems and methods for providing a dashboard for a collaboration work management platform
US11635884B1 (en) 2021-10-11 2023-04-25 Asana, Inc. Systems and methods to provide personalized graphical user interfaces within a collaboration environment
US11652762B2 (en) 2018-10-17 2023-05-16 Asana, Inc. Systems and methods for generating and presenting graphical user interfaces
US11676107B1 (en) 2021-04-14 2023-06-13 Asana, Inc. Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles
US11694162B1 (en) 2021-04-01 2023-07-04 Asana, Inc. Systems and methods to recommend templates for project-level graphical user interfaces within a collaboration environment
US11720378B2 (en) 2018-04-02 2023-08-08 Asana, Inc. Systems and methods to facilitate task-specific workspaces for a collaboration work management platform
US11756000B2 (en) 2021-09-08 2023-09-12 Asana, Inc. Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events
US11763259B1 (en) * 2020-02-20 2023-09-19 Asana, Inc. Systems and methods to generate units of work in a collaboration environment
US11769115B1 (en) 2020-11-23 2023-09-26 Asana, Inc. Systems and methods to provide measures of user workload when generating units of work based on chat sessions between users of a collaboration environment
US11782737B2 (en) 2019-01-08 2023-10-10 Asana, Inc. Systems and methods for determining and presenting a graphical user interface including template metrics
US11783253B1 (en) 2020-02-11 2023-10-10 Asana, Inc. Systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment
US11792028B1 (en) 2021-05-13 2023-10-17 Asana, Inc. Systems and methods to link meetings with units of work of a collaboration environment
US11803814B1 (en) 2021-05-07 2023-10-31 Asana, Inc. Systems and methods to facilitate nesting of portfolios within a collaboration environment
US11809222B1 (en) 2021-05-24 2023-11-07 Asana, Inc. Systems and methods to generate units of work within a collaboration environment based on selection of text
US11836681B1 (en) 2022-02-17 2023-12-05 Asana, Inc. Systems and methods to generate records within a collaboration environment
US11863601B1 (en) 2022-11-18 2024-01-02 Asana, Inc. Systems and methods to execute branching automation schemes in a collaboration environment
US11900323B1 (en) 2020-06-29 2024-02-13 Asana, Inc. Systems and methods to generate units of work within a collaboration environment based on video dictation

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10380867B2 (en) * 2015-01-30 2019-08-13 Cisco Technology, Inc. Alert management within a network based virtual collaborative space
US10347047B2 (en) * 2015-11-25 2019-07-09 Google Llc Trigger regions
US10855783B2 (en) * 2017-01-23 2020-12-01 Adobe Inc. Communication notification trigger modeling preview
CN110768806A (en) * 2019-10-31 2020-02-07 北京金山云网络技术有限公司 Data processing method and device in collaborative application and electronic equipment
CN111221666A (en) * 2020-01-03 2020-06-02 北京明略软件系统有限公司 Scheduling method, scheduling device, electronic equipment and computer readable storage medium

Citations (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3631470A (en) * 1969-09-26 1971-12-28 Audio Designs & Mfg Audio console delegation system with visual readout
US5204897A (en) * 1991-06-28 1993-04-20 Digital Equipment Corporation Management interface for license management system
US5208748A (en) * 1985-11-18 1993-05-04 Action Technologies, Inc. Method and apparatus for structuring and managing human communications by explicitly defining the types of communications permitted between participants
US5220604A (en) * 1990-09-28 1993-06-15 Digital Equipment Corporation Method for performing group exclusion in hierarchical group structures
US5224163A (en) * 1990-09-28 1993-06-29 Digital Equipment Corporation Method for delegating authorization from one entity to another through the use of session encryption keys
US5245532A (en) * 1988-06-16 1993-09-14 International Business Machines Corporation Electronic mail follow-up system
US5249291A (en) * 1990-11-20 1993-09-28 International Business Machines Corporation Method and apparatus for consensual delegation of software command operations in a data processing system
US5260999A (en) * 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
US5315657A (en) * 1990-09-28 1994-05-24 Digital Equipment Corporation Compound principals in access control lists
US5438508A (en) * 1991-06-28 1995-08-01 Digital Equipment Corporation License document interchange format for license management system
US5737606A (en) * 1996-07-18 1998-04-07 Electronic Data Systems Corporation Method and system for delegation in a class-based language
US5958050A (en) * 1996-09-24 1999-09-28 Electric Communities Trusted delegation system
US6101557A (en) * 1998-05-29 2000-08-08 International Business Machines Corporation Method and system for remote function control and delegation within multifunction bus supported devices
US6185728B1 (en) * 1996-01-31 2001-02-06 Inprise Corporation Development system with methods for type-safe delegation of object events to event handlers of other objects
US6189103B1 (en) * 1998-07-21 2001-02-13 Novell, Inc. Authority delegation with secure operating system queues
US6212549B1 (en) * 1997-10-06 2001-04-03 Nexprise, Inc. Trackpoint-based computer-implemented systems and methods for facilitating collaborative project development and communication
US6220510B1 (en) * 1997-05-15 2001-04-24 Mondex International Limited Multi-application IC card with delegation feature
US6230266B1 (en) * 1999-02-03 2001-05-08 Sun Microsystems, Inc. Authentication system and process
US6247026B1 (en) * 1996-10-11 2001-06-12 Sun Microsystems, Inc. Method, apparatus, and product for leasing of delegation certificates in a distributed system
US6260069B1 (en) * 1998-02-10 2001-07-10 International Business Machines Corporation Direct data retrieval in a distributed computing system
US6343377B1 (en) * 1997-12-30 2002-01-29 Netscape Communications Corp. System and method for rendering content received via the internet and world wide web via delegation of rendering processes
US20020035608A1 (en) * 2000-08-09 2002-03-21 Rajko Milovanovic Automated follow-up to a request
US6367009B1 (en) * 1998-12-17 2002-04-02 International Business Machines Corporation Extending SSL to a multi-tier environment using delegation of authentication and authority
US6449617B1 (en) * 1999-06-15 2002-09-10 Microsoft Corporation Edit command delegation program for editing electronic files
US6523012B1 (en) * 1999-05-21 2003-02-18 Compaq Information Technology Group, L.P. Delegation of permissions in an electronic commerce system
US6549950B2 (en) * 1996-05-31 2003-04-15 Microsoft Corporation Method for automatically tallying voting data in e-mail systems
US6581068B1 (en) * 1999-12-01 2003-06-17 Cartesis, S.A. System and method for instant consolidation, enrichment, delegation and reporting in a multidimensional database
US6601171B1 (en) * 1999-02-18 2003-07-29 Novell, Inc. Deputization in a distributed computing system
US6711679B1 (en) * 1999-03-31 2004-03-23 International Business Machines Corporation Public key infrastructure delegation
US6792462B2 (en) * 2001-01-16 2004-09-14 Netiq Corporation Methods, systems and computer program products for rule based delegation of administration powers
US6854007B1 (en) * 1998-09-17 2005-02-08 Micron Technology, Inc. Method and system for enhancing reliability of communication with electronic messages
US6879690B2 (en) * 2001-02-21 2005-04-12 Nokia Corporation Method and system for delegation of security procedures to a visited domain
US6885388B2 (en) * 2001-04-25 2005-04-26 Probaris Technologies Inc. Method for automatically generating list of meeting participants and delegation permission
US20050160145A1 (en) * 2003-12-29 2005-07-21 Gruen Daniel M. System and method for facilitating collaboration in a shared email repository
US7062490B2 (en) * 2001-03-26 2006-06-13 Microsoft Corporation Serverless distributed file system
US20060246436A1 (en) * 2002-05-22 2006-11-02 Ryuzo Ohno Method for judging sensibility to imatinib
US20070143169A1 (en) * 2005-12-21 2007-06-21 Grant Chad W Real-time workload information scheduling and tracking system and related methods
US20080313536A1 (en) * 2007-06-14 2008-12-18 Microsoft Corporation Situation Sharing and Viewing
US7716593B2 (en) * 2003-07-01 2010-05-11 Microsoft Corporation Conversation grouping of electronic mail records

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7725543B2 (en) * 2002-06-12 2010-05-25 Sharp Kabushiki Kaisha Network communication device for transmitting/receiving an email message containing a disposition notification request
US8306831B2 (en) * 2005-01-10 2012-11-06 International Business Machines Corporation Systems with message integration for data exchange, collection, monitoring and/or alerting
US20110022662A1 (en) 2009-07-23 2011-01-27 International Business Machines Corporation Event triggered notifications for collaborative processes

Patent Citations (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3631470A (en) * 1969-09-26 1971-12-28 Audio Designs & Mfg Audio console delegation system with visual readout
US5208748A (en) * 1985-11-18 1993-05-04 Action Technologies, Inc. Method and apparatus for structuring and managing human communications by explicitly defining the types of communications permitted between participants
US5245532A (en) * 1988-06-16 1993-09-14 International Business Machines Corporation Electronic mail follow-up system
US5315657A (en) * 1990-09-28 1994-05-24 Digital Equipment Corporation Compound principals in access control lists
US5220604A (en) * 1990-09-28 1993-06-15 Digital Equipment Corporation Method for performing group exclusion in hierarchical group structures
US5224163A (en) * 1990-09-28 1993-06-29 Digital Equipment Corporation Method for delegating authorization from one entity to another through the use of session encryption keys
US5249291A (en) * 1990-11-20 1993-09-28 International Business Machines Corporation Method and apparatus for consensual delegation of software command operations in a data processing system
US5260999A (en) * 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
US5204897A (en) * 1991-06-28 1993-04-20 Digital Equipment Corporation Management interface for license management system
US5438508A (en) * 1991-06-28 1995-08-01 Digital Equipment Corporation License document interchange format for license management system
US6185728B1 (en) * 1996-01-31 2001-02-06 Inprise Corporation Development system with methods for type-safe delegation of object events to event handlers of other objects
US6549950B2 (en) * 1996-05-31 2003-04-15 Microsoft Corporation Method for automatically tallying voting data in e-mail systems
US5737606A (en) * 1996-07-18 1998-04-07 Electronic Data Systems Corporation Method and system for delegation in a class-based language
US5958050A (en) * 1996-09-24 1999-09-28 Electric Communities Trusted delegation system
US6247026B1 (en) * 1996-10-11 2001-06-12 Sun Microsystems, Inc. Method, apparatus, and product for leasing of delegation certificates in a distributed system
US6220510B1 (en) * 1997-05-15 2001-04-24 Mondex International Limited Multi-application IC card with delegation feature
US6212549B1 (en) * 1997-10-06 2001-04-03 Nexprise, Inc. Trackpoint-based computer-implemented systems and methods for facilitating collaborative project development and communication
US6343377B1 (en) * 1997-12-30 2002-01-29 Netscape Communications Corp. System and method for rendering content received via the internet and world wide web via delegation of rendering processes
US6260069B1 (en) * 1998-02-10 2001-07-10 International Business Machines Corporation Direct data retrieval in a distributed computing system
US6101557A (en) * 1998-05-29 2000-08-08 International Business Machines Corporation Method and system for remote function control and delegation within multifunction bus supported devices
US6189103B1 (en) * 1998-07-21 2001-02-13 Novell, Inc. Authority delegation with secure operating system queues
US6854007B1 (en) * 1998-09-17 2005-02-08 Micron Technology, Inc. Method and system for enhancing reliability of communication with electronic messages
US6367009B1 (en) * 1998-12-17 2002-04-02 International Business Machines Corporation Extending SSL to a multi-tier environment using delegation of authentication and authority
US6230266B1 (en) * 1999-02-03 2001-05-08 Sun Microsystems, Inc. Authentication system and process
US6601171B1 (en) * 1999-02-18 2003-07-29 Novell, Inc. Deputization in a distributed computing system
US6711679B1 (en) * 1999-03-31 2004-03-23 International Business Machines Corporation Public key infrastructure delegation
US6523012B1 (en) * 1999-05-21 2003-02-18 Compaq Information Technology Group, L.P. Delegation of permissions in an electronic commerce system
US6449617B1 (en) * 1999-06-15 2002-09-10 Microsoft Corporation Edit command delegation program for editing electronic files
US6581068B1 (en) * 1999-12-01 2003-06-17 Cartesis, S.A. System and method for instant consolidation, enrichment, delegation and reporting in a multidimensional database
US20020035608A1 (en) * 2000-08-09 2002-03-21 Rajko Milovanovic Automated follow-up to a request
US6792462B2 (en) * 2001-01-16 2004-09-14 Netiq Corporation Methods, systems and computer program products for rule based delegation of administration powers
US6879690B2 (en) * 2001-02-21 2005-04-12 Nokia Corporation Method and system for delegation of security procedures to a visited domain
US7062490B2 (en) * 2001-03-26 2006-06-13 Microsoft Corporation Serverless distributed file system
US6885388B2 (en) * 2001-04-25 2005-04-26 Probaris Technologies Inc. Method for automatically generating list of meeting participants and delegation permission
US20060246436A1 (en) * 2002-05-22 2006-11-02 Ryuzo Ohno Method for judging sensibility to imatinib
US7716593B2 (en) * 2003-07-01 2010-05-11 Microsoft Corporation Conversation grouping of electronic mail records
US20050160145A1 (en) * 2003-12-29 2005-07-21 Gruen Daniel M. System and method for facilitating collaboration in a shared email repository
US20070143169A1 (en) * 2005-12-21 2007-06-21 Grant Chad W Real-time workload information scheduling and tracking system and related methods
US20080313536A1 (en) * 2007-06-14 2008-12-18 Microsoft Corporation Situation Sharing and Viewing

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Rich et al. "Adding a Collaborative Agent to Graphical User Interface", 1996, ACM, pp. 21-30 *

Cited By (110)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120311460A1 (en) * 2006-09-02 2012-12-06 John Edward Boyd Computer-Based Methods for Arranging Meetings and Systems for Performing the Same
US9355386B2 (en) * 2006-09-02 2016-05-31 Tangible Social, Llc Computer-based methods for arranging meetings and systems for performing the same
US10320858B2 (en) 2009-07-23 2019-06-11 International Business Machines Corporation Event triggered notifications for collaborative processes
US9813460B2 (en) 2009-07-23 2017-11-07 International Business Machines Corporation Event triggered notifications for collaborative processes
US10015211B2 (en) 2009-07-23 2018-07-03 International Business Machines Corporation Event triggered notifications for collaborative processes
US20110087764A1 (en) * 2009-10-14 2011-04-14 Dror Yaffe Engine for generating and managing communications concerning on-line collaboration among a plurality of users in consideration with a computerized application
US20120171845A1 (en) * 2011-01-03 2012-07-05 Gt Solar Incorporated Chuck for chemical vapor deposition systems and related methods therefor
US9983759B1 (en) * 2012-02-29 2018-05-29 Google Llc Method and system for sharing virtual collaboration objects
US20130332813A1 (en) * 2012-06-06 2013-12-12 Sap Ag Generic Workspace Awareness Support for Collaborative Web Applications
US10666514B2 (en) * 2013-02-12 2020-05-26 International Business Machines Corporation Applying policy attachment service level management (SLM) semantics within a peered policy enforcement deployment
US20140229594A1 (en) * 2013-02-12 2014-08-14 International Business Machines Corporation Applying policy attachment service level management (slm) semantics within a peered policy enforcement deployment
US11075956B2 (en) 2013-02-12 2021-07-27 International Business Machines Corporation Dynamic generation of policy enforcement rules and actions from policy attachment semantics
US10693746B2 (en) 2013-02-12 2020-06-23 International Business Machines Corporation Instrumentation and monitoring of service level agreement (SLA) and service policy enforcement
US10693911B2 (en) 2013-02-12 2020-06-23 International Business Machines Corporation Dynamic generation of policy enforcement rules and actions from policy attachment semantics
US9256341B2 (en) 2013-03-20 2016-02-09 Microsoft Technology Licensing, Llc Tracking changes in collaborative authoring environment
US10331290B2 (en) 2013-03-20 2019-06-25 Microsoft Technology Licensing, Llc Tracking changes in collaborative authoring environment
US11514399B2 (en) 2013-12-21 2022-11-29 Microsoft Technology Licensing, Llc Authoring through suggestion
US10824787B2 (en) 2013-12-21 2020-11-03 Microsoft Technology Licensing, Llc Authoring through crowdsourcing based suggestions
CN103957278A (en) * 2014-05-20 2014-07-30 薛厚新 Memo system achieving intelligent reminding within specific geographical range and application method thereof
US11561996B2 (en) 2014-11-24 2023-01-24 Asana, Inc. Continuously scrollable calendar user interface
US11693875B2 (en) 2014-11-24 2023-07-04 Asana, Inc. Client side system and method for search backed calendar user interface
US11263228B2 (en) 2014-11-24 2022-03-01 Asana, Inc. Continuously scrollable calendar user interface
US10997188B2 (en) 2015-03-23 2021-05-04 Dropbox, Inc. Commenting in shared folder backed integrated workspaces
US11567958B2 (en) 2015-03-23 2023-01-31 Dropbox, Inc. Content item templates
US11347762B2 (en) 2015-03-23 2022-05-31 Dropbox, Inc. Intelligent scrolling in shared folder back integrated workspaces
US10558677B2 (en) 2015-03-23 2020-02-11 Dropbox, Inc. Viewing and editing content items in shared folder backed integrated workspaces
US11354328B2 (en) 2015-03-23 2022-06-07 Dropbox, Inc. Shared folder backed integrated workspaces
US10452670B2 (en) * 2015-03-23 2019-10-22 Dropbox, Inc. Processing message attachments in shared folder backed integrated workspaces
US11748366B2 (en) 2015-03-23 2023-09-05 Dropbox, Inc. Shared folder backed integrated workspaces
US11016987B2 (en) 2015-03-23 2021-05-25 Dropbox, Inc. Shared folder backed integrated workspaces
US10997189B2 (en) 2015-03-23 2021-05-04 Dropbox, Inc. Processing conversation attachments in shared folder backed integrated workspaces
US10635684B2 (en) 2015-03-23 2020-04-28 Dropbox, Inc. Shared folder backed integrated workspaces
US20160337166A1 (en) * 2015-05-14 2016-11-17 Honeywell International Inc. Apparatus and method for automated event notification read receipt to support non-repudiated auditing or other functions in industrial process control and automation system
US10505790B2 (en) * 2015-05-14 2019-12-10 Honeywell International Inc. Apparatus and method for automated event notification read receipt to support non-repudiated auditing or other functions in industrial process control and automation system
US20170178000A1 (en) * 2015-12-18 2017-06-22 Sap Se Generation and handling of situation definitions
US10740357B2 (en) 2015-12-18 2020-08-11 Sap Se Generation and handling of situation objects
US11816128B2 (en) 2015-12-22 2023-11-14 Dropbox, Inc. Managing content across discrete systems
US10942944B2 (en) 2015-12-22 2021-03-09 Dropbox, Inc. Managing content across discrete systems
US11233875B2 (en) * 2016-05-20 2022-01-25 Microsoft Technology Licensing, Llc Content sharing with user and recipient devices
US10587724B2 (en) * 2016-05-20 2020-03-10 Microsoft Technology Licensing, Llc Content sharing with user and recipient devices
US20170339249A1 (en) * 2016-05-20 2017-11-23 Microsoft Technology Licensing, Llc Content sharing with user and recipient devices
US10069782B2 (en) 2016-08-12 2018-09-04 Xenovus Inc. Method and system to facilitate electronic communication between internal teams and external contacts
US10776755B2 (en) 2016-12-29 2020-09-15 Dropbox, Inc. Creating projects in a content management system
US10719807B2 (en) 2016-12-29 2020-07-21 Dropbox, Inc. Managing projects using references
US10970679B2 (en) 2016-12-29 2021-04-06 Dropbox, Inc. Presenting project data managed by a content management system
US10970656B2 (en) 2016-12-29 2021-04-06 Dropbox, Inc. Automatically suggesting project affiliations
US11017354B2 (en) 2016-12-30 2021-05-25 Dropbox, Inc. Managing projects in a content management system
US11900324B2 (en) 2016-12-30 2024-02-13 Dropbox, Inc. Managing projects in a content management system
US10402786B2 (en) 2016-12-30 2019-09-03 Dropbox, Inc. Managing projects in a content management system
US11775745B2 (en) 2017-07-11 2023-10-03 Asana, Inc. Database model which provides management of custom fields and methods and apparatus therfore
US11610053B2 (en) 2017-07-11 2023-03-21 Asana, Inc. Database model which provides management of custom fields and methods and apparatus therfor
US10977242B2 (en) * 2017-09-07 2021-04-13 Atlassian Pty Ltd. Systems and methods for managing designated content items
US11816096B2 (en) 2017-09-07 2023-11-14 Atlassian Pty Ltd. Systems and methods for managing designated content in collaboration systems
US11226939B2 (en) 2017-12-29 2022-01-18 Dropbox, Inc. Synchronizing changes within a collaborative content management system
US11398998B2 (en) 2018-02-28 2022-07-26 Asana, Inc. Systems and methods for generating tasks based on chat sessions between users of a collaboration environment
US11695719B2 (en) 2018-02-28 2023-07-04 Asana, Inc. Systems and methods for generating tasks based on chat sessions between users of a collaboration environment
US11720378B2 (en) 2018-04-02 2023-08-08 Asana, Inc. Systems and methods to facilitate task-specific workspaces for a collaboration work management platform
US11327645B2 (en) 2018-04-04 2022-05-10 Asana, Inc. Systems and methods for preloading an amount of content based on user scrolling
US11656754B2 (en) 2018-04-04 2023-05-23 Asana, Inc. Systems and methods for preloading an amount of content based on user scrolling
US20220011911A1 (en) * 2018-05-25 2022-01-13 Palantir Technologies Inc. Interactive display with workflow management system
US11831457B2 (en) 2018-06-08 2023-11-28 Asana, Inc. Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users
US11290296B2 (en) 2018-06-08 2022-03-29 Asana, Inc. Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users
US11632260B2 (en) 2018-06-08 2023-04-18 Asana, Inc. Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users
US11652762B2 (en) 2018-10-17 2023-05-16 Asana, Inc. Systems and methods for generating and presenting graphical user interfaces
US11100053B2 (en) 2018-11-06 2021-08-24 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US10896154B2 (en) 2018-11-06 2021-01-19 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US11194767B2 (en) 2018-11-06 2021-12-07 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US10838925B2 (en) 2018-11-06 2020-11-17 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US11194766B2 (en) 2018-11-06 2021-12-07 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US11593314B2 (en) 2018-11-06 2023-02-28 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US10929349B2 (en) 2018-11-06 2021-02-23 Dropbox, Inc. Technologies for integrating cloud content items across platforms
US11694140B2 (en) 2018-12-06 2023-07-04 Asana, Inc. Systems and methods for generating prioritization models and predicting workflow prioritizations
US11341444B2 (en) 2018-12-06 2022-05-24 Asana, Inc. Systems and methods for generating prioritization models and predicting workflow prioritizations
US11568366B1 (en) * 2018-12-18 2023-01-31 Asana, Inc. Systems and methods for generating status requests for units of work
US11810074B2 (en) 2018-12-18 2023-11-07 Asana, Inc. Systems and methods for providing a dashboard for a collaboration work management platform
US11620615B2 (en) 2018-12-18 2023-04-04 Asana, Inc. Systems and methods for providing a dashboard for a collaboration work management platform
US11288081B2 (en) 2019-01-08 2022-03-29 Asana, Inc. Systems and methods for determining and presenting a graphical user interface including template metrics
US11782737B2 (en) 2019-01-08 2023-10-10 Asana, Inc. Systems and methods for determining and presenting a graphical user interface including template metrics
US11561677B2 (en) 2019-01-09 2023-01-24 Asana, Inc. Systems and methods for generating and tracking hardcoded communications in a collaboration management platform
US11341445B1 (en) 2019-11-14 2022-05-24 Asana, Inc. Systems and methods to measure and visualize threshold of user workload
US11783253B1 (en) 2020-02-11 2023-10-10 Asana, Inc. Systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment
US11847613B2 (en) * 2020-02-14 2023-12-19 Asana, Inc. Systems and methods to attribute automated actions within a collaboration environment
US11599855B1 (en) * 2020-02-14 2023-03-07 Asana, Inc. Systems and methods to attribute automated actions within a collaboration environment
US20230162155A1 (en) * 2020-02-14 2023-05-25 Asana, Inc. Systems and methods to attribute automated actions within a collaboration environment
US11763259B1 (en) * 2020-02-20 2023-09-19 Asana, Inc. Systems and methods to generate units of work in a collaboration environment
US11012400B1 (en) * 2020-04-14 2021-05-18 Citrix Systems, Inc. Triggering event notifications based on messages to application users
CN113170283A (en) * 2020-04-14 2021-07-23 思杰系统有限公司 Triggering event notifications based on messages to application users
US11336606B2 (en) * 2020-04-14 2022-05-17 Citrix Systems, Inc. Triggering event notifications based on messages to application users
US11526263B2 (en) * 2020-06-09 2022-12-13 Fujifilm Business Innovation Corp. Information processing apparatus and non-transitory computer readable medium
US11496432B2 (en) * 2020-06-18 2022-11-08 T-Mobile Usa, Inc. Synchronizing message status across multiple user devices
US11636432B2 (en) 2020-06-29 2023-04-25 Asana, Inc. Systems and methods to measure and visualize workload for completing individual units of work
US11900323B1 (en) 2020-06-29 2024-02-13 Asana, Inc. Systems and methods to generate units of work within a collaboration environment based on video dictation
US11455601B1 (en) 2020-06-29 2022-09-27 Asana, Inc. Systems and methods to measure and visualize workload for completing individual units of work
US11720858B2 (en) 2020-07-21 2023-08-08 Asana, Inc. Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment
US11449836B1 (en) 2020-07-21 2022-09-20 Asana, Inc. Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment
US11568339B2 (en) 2020-08-18 2023-01-31 Asana, Inc. Systems and methods to characterize units of work based on business objectives
US11734625B2 (en) 2020-08-18 2023-08-22 Asana, Inc. Systems and methods to characterize units of work based on business objectives
US11769115B1 (en) 2020-11-23 2023-09-26 Asana, Inc. Systems and methods to provide measures of user workload when generating units of work based on chat sessions between users of a collaboration environment
US11902344B2 (en) 2020-12-02 2024-02-13 Asana, Inc. Systems and methods to present views of records in chat sessions between users of a collaboration environment
US11405435B1 (en) 2020-12-02 2022-08-02 Asana, Inc. Systems and methods to present views of records in chat sessions between users of a collaboration environment
US11694162B1 (en) 2021-04-01 2023-07-04 Asana, Inc. Systems and methods to recommend templates for project-level graphical user interfaces within a collaboration environment
US11676107B1 (en) 2021-04-14 2023-06-13 Asana, Inc. Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles
US11553045B1 (en) 2021-04-29 2023-01-10 Asana, Inc. Systems and methods to automatically update status of projects within a collaboration environment
US11803814B1 (en) 2021-05-07 2023-10-31 Asana, Inc. Systems and methods to facilitate nesting of portfolios within a collaboration environment
US11792028B1 (en) 2021-05-13 2023-10-17 Asana, Inc. Systems and methods to link meetings with units of work of a collaboration environment
US11809222B1 (en) 2021-05-24 2023-11-07 Asana, Inc. Systems and methods to generate units of work within a collaboration environment based on selection of text
US11756000B2 (en) 2021-09-08 2023-09-12 Asana, Inc. Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events
US11635884B1 (en) 2021-10-11 2023-04-25 Asana, Inc. Systems and methods to provide personalized graphical user interfaces within a collaboration environment
US11836681B1 (en) 2022-02-17 2023-12-05 Asana, Inc. Systems and methods to generate records within a collaboration environment
US11863601B1 (en) 2022-11-18 2024-01-02 Asana, Inc. Systems and methods to execute branching automation schemes in a collaboration environment

Also Published As

Publication number Publication date
WO2011009896A1 (en) 2011-01-27
US20160026975A1 (en) 2016-01-28
US20170257404A1 (en) 2017-09-07
US9813460B2 (en) 2017-11-07
US10015211B2 (en) 2018-07-03
US10320858B2 (en) 2019-06-11
US20180248922A1 (en) 2018-08-30
CN102473251A (en) 2012-05-23
TW201112691A (en) 2011-04-01

Similar Documents

Publication Publication Date Title
US10320858B2 (en) Event triggered notifications for collaborative processes
US20210065134A1 (en) Intelligent notification system
US7584258B2 (en) Method and system for managing instant messaging status
US7523397B2 (en) Centralized alert and notifications repository, manager, and viewer
US8091035B2 (en) System and method for sharing data
US20130173486A1 (en) Collaboration cloud
US20070100991A1 (en) Method and program product for tracking a file attachment in an e-mail
US20070300164A1 (en) Method and system for managing instant message logs from within a calendar application
US20120278406A1 (en) Most recently used list for attaching files to messages
US9659089B2 (en) Prioritizing work and personal items from various data sources using a user profile
US8990189B2 (en) Determining relevant contacts based on expertise and availability
JP6655134B2 (en) Apparatus and method for processing message repository that can be implemented online
US8775527B2 (en) Collaborative email filtering
US20220351148A1 (en) Productivity entity containers and unified view interface for different productivity entity types
JP7149546B2 (en) Business chat room processing device and business chat room processing method
WO2016175257A1 (en) Information sharing program, information processing device, and information sharing method
US20130174093A1 (en) Compass menu
US20100274619A1 (en) Enhanced Calendaring Notification
US20090282348A1 (en) Method and system for enhanced management of meeting cancellations
US9577867B2 (en) Determining a time before a post is viewed by a recipient
US20240031321A1 (en) Notification systems and methods for centralized threading and presentation of messages
KR20220064698A (en) Apparatus and method of displaying work schedule
KR101987045B1 (en) Apparatus for providing folder chatting room and apparatus for receiving the same
KR20220064668A (en) Apparatus and method of displaying work schedule
KR101851602B1 (en) Apparatus for assisting strategy map management to provide internal customer satisfaction

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BARBER-MINGO, CYNTHIA E.;DENNE, ARNO;HARPUR, LIAM S.;AND OTHERS;SIGNING DATES FROM 20090717 TO 20090723;REEL/FRAME:022996/0319

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION