Automatically subscribing users of an enterprise network to a record

• US 9,483,526 B2
• Filed: 03/21/2014
• Issued: 11/01/2016
• Est. Priority Date: 03/21/2013
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Nahm, Stephen Xavier
• Primary Examiner(s): Ho, Binh V
• Application Number:
  US14/221,678
• Publication Number:
  US 20140289272A1
• Time in Patent Office: 956 Days
• Field of Search: 707/769
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2455 Query execution

Abstract

Various implementations are directed to systems, apparatus, computer-implemented methods and storage media for detecting a change in a status of a record and, in response to the detection of the change in status, identifying related users that are currently relevant to the record based on the change in the status. The identified users are subscribed to the record, and as a result, communications generated for the record are distributed to them. In some implementations, currently relevant users are users that have a role in developing, working with or supervising the record in the record'"'"'s current status, or a role in transitioning the record from its current status to another status. It can be desirable to subscribe currently relevant users because the distribution of communications concerning the record in its current status to these users can benefit an enterprise by virtue of these users knowing the information in the communications.

Claims

1. A server-system-implemented method for associating users of an enterprise network to a record stored in a database of records, the method comprising:

detecting, by a server system of a multi-tenant database system, a change in a status of a first record in a database of records of the multi-tenant database system, the first record including enterprise-related information, the first record having an associated state field having one of two or more possible states, each of the two or more states representing a respective status of the first record, the detection of the change in the status including detecting a change of the state in the state field; and

in response to the detection of the change in the status;

identifying, by the server system, one or more related users in the enterprise network that are currently relevant to the first record based on the change in the status, the identifying including;

identifying one or more records in the database of records that are related to the first record; and

identifying, for each of the one or more related records, one or more users in the enterprise network that are related to the respective related record; and

subscribing, by the server system, each of the one or more related users to the first record.

2. The method of claim 1, further including, in response to the detection of the change in the status:

identifying, by the server system, one or more users currently subscribed to the first record that are no longer relevant to the first record based on the change in the status; and

unsubscribing each of the one or more no longer relevant currently subscribed users from the first record.

3. The method of claim 1, wherein:

each record in the database of records is stored as a respective record data object in the database;

each record data object includes a respective state field associated with the record;

each record data object further includes a record identifier field that identifies the record with a respective record identifier;

each record data object further includes one or more related record fields, each related record field having one or more record identifiers for one or more respective related records; and

identifying the one or more records in the database that are related to the first record includes;

accessing the record data object associated with the first record;

selecting one or more of the one or more related record fields in the record data object based on the change in the status;

accessing the one or more selected record fields; and

identifying one or more record identifiers in each of one or more of the selected record fields.

4. The method of claim 3, wherein each of the selected record fields is selected based on a current relevance of the respective selected record, the relevance of each of the respective selected records being associated with a relationship between information in the respective selected record and information in the first record.

5. The method of claim 3, wherein:

each user of the enterprise network is associated with a respective user identifier;

each record data object further includes one or more related user fields, each related user field having one or more user identifiers for one or more respective related users; and

identifying, for each of the one or more related records, the one or more users in the enterprise network that are related to the respective related record includes;

accessing the respective record data object associated with the respective related record;

selecting one or more of the one or more related user fields in the respective record data object based on the change in the status;

accessing the one or more selected user fields; and

identifying one or more user identifiers in each of one or more of the selected user fields.

6. The method of claim 5, wherein each of the selected user fields is selected based on a current relevance of the respective selected user, the relevance of each of the respective selected users being associated with a role of the respective selected user in developing or working with the first record in the first record'"'"'s changed status or a role in transitioning the first record from the changed status to another status.

7. The method of claim 5, wherein each of the selected user fields is selected based on a status of the respective related record or a combination of the status of the first record and the status of the respective related record.

8. The method of claim 1, wherein:

each user of the enterprise network is associated with a respective user identifier;

each record data object further includes one or more related user fields, each related user field having one or more user identifiers for one or more respective related users; and

identifying the one or more related users in the enterprise network that are currently relevant to the first record based on the change in the status includes;

accessing the record data object associated with the first record;

selecting one or more of the one or more related user fields in the record data object;

accessing the one or more selected user fields; and

identifying one or more user identifiers in each of one or more of the selected user fields.

9. The method of claim 1, wherein the state field includes a picklist including two or more possible items, each item in the picklist representing a respective one of the two or more states.

10. The method of claim 1, wherein the two or more possible states are fixed.

11. The method of claim 1, wherein:

the change in the status is a change from a non-actionable status to an actionable status; and

the method further includes;

detecting a second change in the status of the first record, the second change in the status being a change from the actionable status to a non-actionable status; and

in response to the detection of the second change in the status, unsubscribing one or more of the users that were subscribed to the first record in response to the change in the status from the non-actionable status to the actionable status.

12. A system for associating users of an enterprise network to a record stored in a database of records, the system comprising:

a database system implemented using a server system including one or more processors and a database of records, the database system configurable to;

detect a change in a status of a first record in the database of records, the first record including enterprise-related information, the first record having an associated state field having one of two or more possible states, each of the two or more states representing a respective status of the first record, the detection of the change in the status including detecting a change of the state in the state field; and

in response to the detection of the change in the status;

identify one or more related users in the enterprise network that are currently relevant to the first record based on the change in the status, the identification including;

identifying one or more records in the database of records that are related to the first record; and

identifying, for each of the one or more related records, one or more users in the enterprise network that are related to the respective related record; and

subscribe each of the one or more related users to the first record.

13. The system of claim 12, wherein the database system is further configurable to, in response to the detection of the change in the status:

identify one or more users currently subscribed to the first record that are no longer relevant to the first record based on the change in the status; and

unsubscribe each of the one or more no longer relevant currently subscribed users from the first record.

14. The system of claim 12, wherein:

each record in the database of records is stored as a respective record data object in the database;

each record data object includes a respective state field associated with the record;

each record data object further includes a record identifier field that identifies the record with a respective record identifier;

each record data object further includes one or more related record fields, each related record field having one or more record identifiers for one or more respective related records; and

identifying the one or more records in the database that are related to the first record includes;

accessing the record data object associated with the first record;

selecting one or more of the one or more related record fields in the record data object based on the change in the status;

accessing the one or more selected record fields; and

identifying one or more record identifiers in each of one or more of the selected record fields.

15. The system of claim 14, wherein each of the selected record fields is selected based on a current relevance of the respective selected record, the relevance of each of the respective selected records being associated with a relationship between information in the respective selected record and information in the first record.

16. The system of claim 14, wherein:

each user of the enterprise network is associated with a respective user identifier;

each record data object further includes one or more related user fields, each related user field having one or more user identifiers for one or more respective related users; and

identifying, for each of the one or more related records, the one or more users in the enterprise network that are related to the respective related record includes;

accessing the respective record data object associated with the respective related record;

selecting one or more of the one or more related user fields in the respective record data object based on the change in the status;

accessing the one or more selected user fields; and

identifying one or more user identifiers in each of one or more of the selected user fields.

17. The system of claim 16, wherein each of the selected user fields is selected based on a current relevance of the respective selected user, the relevance of each of the respective selected users being associated with a role of the respective selected user in developing or working with the first record in the first record'"'"'s changed status or a role in transitioning the record from the current status to another status.

18. The system of claim 16, wherein each of the selected user fields is selected based on a status of the respective related record or a combination of the status of the first record and the status of the respective related record.

19. The system of claim 12, wherein:

each user of the enterprise network is associated with a respective user identifier;

each record data object further includes one or more related user fields, each related user field having one or more user identifiers for one or more respective related users; and

identifying the one or more related users in the enterprise network that are currently relevant to the first record based on the change in the status includes;

accessing the record data object associated with the first record;

selecting one or more of the one or more related user fields in the record data object;

accessing the one or more selected user fields; and

identifying one or more user identifiers in each of one or more of the selected user fields.

20. The system of claim 12, wherein the state field includes a picklist including two or more possible items, each item in the picklist representing a respective one of the two or more states.

21. The system of claim 12, wherein the two or more possible states are fixed.

22. The system of claim 12, wherein:

the change in the status is a change from a non-actionable status to an actionable status; and

the database system is further configurable to;

detect a second change in the status of the first record, the second change in the status being a change from the actionable status to a non-actionable status; and

in response to the detection of the second change in the status, unsubscribe one or more of the users that were subscribed to the first record in response to the change in the status from the non-actionable status to the actionable status.