US2014214829A1PendingUtilityA1

Implementing enterprise level business information networking

69
Assignee: SALESFORCE COM INCPriority: Nov 12, 2009Filed: Mar 31, 2014Published: Jul 31, 2014
Est. expiryNov 12, 2029(~3.3 yrs left)· nominal 20-yr term from priority
G06Q 10/40G06F 16/2282G06Q 10/10G06F 16/122G06Q 30/02G06F 16/1873G06F 16/185G06F 21/6227G06F 16/176G06F 16/245G06F 17/30424G06F 17/30339
69
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Systems, apparatus, and methods for implementing enterprise level social and business information networking are provided. Users can receive relevant information about a database system and its users at an appropriate time. Users can then use this relevant information to reduce errors and limit redundant efforts. For example, an update of a record in the database can be identified, and a story created automatically about the update and sent to the users that are following the record. Which updates have stories created and which stories are to be sent to which users can be configured. Other events besides updating of records can also be tracked. For example, actions of a user that result in an event can be tracked, where such tracking can also be configurable. Subscriptions to follow an object can be automatic, and access checks can be used to ensure that unauthorized users do not see certain data.

Claims

exact text as granted — not AI-modified
1 . An apparatus for tracking events in a database system to provide feeds to users of the database system, the apparatus comprising:
 one or more processors; and   a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to:   receive data indicative of an event, the event being a change in a field of a first record from an old value to a new value;   analyze the event to determine that the event is being tracked; and   add a new entry into an event history table corresponding to the event, the new entry including information that identifies the event and the object updated by the event, the object updated by the event being the first record, the event being a change in a field of the first record, the field change being indicated by one of a plurality of feed items of a feed configured to be displayed on a display of a computing device, the one feed item being positioned relative to other feed items in the display of the feed according to an importance level determined by application of one or more criteria to the event.   
     
     
         2 . The apparatus of  claim 1 , wherein the plurality instructions, which when executed further cause the one or more processors to:
 receive, from a first user, a request to view a feed of one or more objects;   query the event history table using identifiers associated with the one or more objects to obtain a plurality of events;   obtain one or more feed items corresponding to each event; and   display the obtained one or more feed items.   
     
     
         3 . The apparatus of  claim 1 , wherein the plurality instructions, which when executed further cause the one or more processors to store the old value of the field and the new value of the field in a field change table. 
     
     
         4 . The apparatus of  claim 3 , wherein the old value and the new value are stored in the field change table along with an event identifier. 
     
     
         5 . The apparatus of  claim 1 , wherein the object updated by a first event is a first user's profile, the first event being a message to first user's profile, and wherein the one or more processors are further configured to execute instructions to store text of the message in a second table along with an event identifier. 
     
     
         6 . The apparatus of  claim 1 , wherein the plurality instructions, which when executed further cause the one or more processors to:
 receive an event that includes a comment on another event; and   store the comment into a third table along with an event identifier.   
     
     
         7 . The apparatus of  claim 1 , wherein the plurality instructions, which when executed further cause the one or more processors to:
 determine one or more users following the object updated by the event being tracked; and   associate the one or more users with the event.   
     
     
         8 . The apparatus of  claim 7 , wherein associating a user with the event includes adding a user identifier and an event identifier to a same entry of a table. 
     
     
         9 . The apparatus of  claim 8 , wherein each user following the object is added as a separate entry to a news feed table, wherein each separate entry includes a respective user identifier and the event identifier. 
     
     
         10 . The apparatus of  claim 1 , wherein the criteria include one or more of: an identification of a user who posted a feed item, a time a feed item was posted, and an indication of a first feed item as being related to a second feed item. 
     
     
         11 . The apparatus of  claim 1 , wherein the first record is a customer relationship management (CRM) record storing CRM data. 
     
     
         12 . The apparatus of  claim 11 , wherein the CRM record is one of: an account, a case, a contact, a lead, and an opportunity. 
     
     
         13 . A method of tracking events in a database system to provide feeds to users of the database system, the method comprising:
 receiving data indicative of an event, the event being a change in a field of a first record from an old value to a new value;   analyzing the event to determine that the event is being tracked; and   adding a new entry into an event history table corresponding to the event, the new entry including information that identifies the event and the object updated by the event, the object updated by the event being the first record, the event being a change in a field of the first record, the field change being indicated by one of a plurality of feed items of a feed configured to be displayed on a display of a computing device, the one feed item being positioned relative to other feed items in the display of the feed according to an importance level determined by application of one or more criteria to the event.   
     
     
         14 . The method of  claim 13 , further comprising:
 receiving, from a first user, a request to view a feed of one or more objects;   querying the event history table using identifiers associated with the one or more objects to obtain a plurality of events;   obtaining one or more feed items corresponding to each event; and   displaying the obtained one or more feed items.   
     
     
         15 . The method of  claim 13 , the method further comprising storing the old value of the field and the new value of the field in a field change table. 
     
     
         16 . The method of  claim 15 , wherein the old value and the new value are stored in the field change table along with an event identifier. 
     
     
         17 . The method of  claim 13 , wherein the object updated by a first event is a first user's profile, and wherein the first event is a message to first user's profile, the method further comprising:
 storing text of the message in a second table along with an event identifier.   
     
     
         18 . The method of  claim 13 , further comprising:
 receiving an event that includes a comment on another event; and   storing the comment into a third table along with an event identifier.   
     
     
         19 . The method of  claim 13 , further comprising:
 determining one or more users following the object updated by the event being tracked; and   associating the one or more users with the event.   
     
     
         20 . The method of  claim 19 , wherein associating a user with the event includes adding a user identifier and an event identifier to a same entry of a table. 
     
     
         21 . The method of  claim 20 , wherein each user following the object is added as a separate entry to a news feed table, wherein each separate entry includes a respective user identifier and the event identifier. 
     
     
         22 . The method of  claim 13 , wherein the criteria include one or more of: an identification of a user who posted a feed item, a time a feed item was posted, and an indication of a first feed item as being related to a second feed item. 
     
     
         23 . The method of  claim 13 , wherein the first record is a customer relationship management (CRM) record storing CRM data. 
     
     
         24 . The method of  claim 23 , wherein the CRM record is one of: an account, a case, a contact, a lead, and an opportunity. 
     
     
         25 . A computer program product comprising a non-transitory computer readable medium storing a plurality of instructions for controlling a processor to perform an operation of tracking events in a database system to provide feeds to users of the database system, the instructions comprising:
 receiving data indicative of an event, the event being a change in a field of a first record from an old value to a new value;   analyzing the event to determine that the event is being tracked; and   adding a new entry into an event history table corresponding to the event, the new entry including information that identifies the event and the object updated by the event, the object updated by the event being the first record, the event being a change in a field of the first record, the field change being indicated by one of a plurality of feed items of a feed configured to be displayed on a display of a computing device, the one feed item being positioned relative to other feed items in the display of the feed according to an importance level determined by application of one or more criteria to the event.   
     
     
         26 . The computer program product of  claim 25 , wherein the instructions further comprise:
 receiving, from a first user, a request to view a feed of one or more objects;   querying the event history table using identifiers associated with the one or more objects to obtain a plurality of events;   obtaining one or more feed items corresponding to each event; and   displaying the obtained one or more feed items.   
     
     
         27 . The computer program product of  claim 25 , the method further comprising storing the old value of the field and the new value of the field in a field change table. 
     
     
         28 . The method of  claim 27 , wherein the old value and the new value are stored in the field change table along with an event identifier. 
     
     
         29 . The computer program product of  claim 25 , wherein the object updated by a first event is a first user's profile, and wherein the first event is a message to first user's profile, the method further comprising:
 storing text of the message in a second table along with an event identifier.   
     
     
         30 . The computer program product of  claim 25 , further comprising:
 receiving an event that includes a comment on another event; and   storing the comment into a third table along with an event identifier.   
     
     
         31 . The computer program product of  claim 25 , further comprising:
 determining one or more users following the object updated by the event being tracked; and   associating the one or more users with the event.   
     
     
         32 . The computer program product of  claim 31 , wherein associating a user with the event includes adding a user identifier and an event identifier to a same entry of a table. 
     
     
         33 . The computer program product of  claim 32 , wherein each user following the object is added as a separate entry to a news feed table, wherein each separate entry includes a respective user identifier and the event identifier. 
     
     
         34 . The computer program product of  claim 25 , wherein the first record is a customer relationship management (CRM) record storing CRM data. 
     
     
         35 . The computer program product of  claim 34 , wherein the CRM record is one of: an account, a case, a contact, a lead, and an opportunity.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.