IP Library › Granted Patent US 10,769,119
Granted Patent B2
US 10,769,119 · App. 15/794,698 · Granted Sep 8, 2020

Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment

Inventors: William Gradin (San Francisco, CA); Matthew Davidchuk (San Francisco, CA); Qiu Ma (San Leandro, CA); Leonid Zemskov (San Mateo, CA); Amy Palke (Oakland, CA)
Assignee: salesforce.com, inc.
G06F16/21G06F16/282G06F16/90G06F16/903G06F16/23
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,769,119
App. No.
15/794,698
Granted
Sep 8, 2020
Kind
B2
Abstract

Disclosed are systems, apparatus, methods, and computer readable media for suppressing network feed activities using an information feed in an on-demand database service environment. In one embodiment, a message is received, including data indicative of a user action. An entity associated with the user action is identified, where the entity is a type of record stored in a database. A type of the entity is identified. It is determined whether the entity type is a prohibited entity type. When the entity type is not a prohibited entity type, the message data is saved to one or more tables in the database. The tables are configured to store feed items of an information feed capable of being displayed on a device. When the entity type is a prohibited entity type, the saving of the message data, to the one or more tables in the database configured to store the feed items, is prohibited.

Claims (38)

1. A system comprising:

a database system implemented using a server system, the database system configurable to cause:

obtaining, using the database system, data indicating a user action having occurred with respect to at least one customer relationship management (CRM) record stored in at least one CRM database, the user action being related to at least one of: creating the at least one record, updating the at least one record, deleting the at least one record, retrieving the at least one record, performing an assignment with respect to the at least one record, or sharing information related to the at least one record;

identifying, using the database system, the at least one record as being one of a plurality of types of CRM records;

determining, using the database system, that the identified CRM record type of the at least one record is an account or an opportunity designated in the database system as being enabled for storing and/or displaying updates; and

enabling, responsive to determining that the identified CRM record type is the account or the opportunity, storing and/or displaying in a user interface on a user device an update associated with the user action and associated with the at least one record as a post of an activity feed of a feed system associated with the at least one CRM database.

2. The system of claim 1 , wherein determining that the identified CRM record type is the account or the opportunity comprises:

processing at least one post rule associated with the identified CRM record type, the at least one post rule being programmable to be enabled or disabled.

3. The system of claim 2 , wherein the at least one post rule is programmable to create a localized and parameterized auto-post responsive to occurrence of a designated event.

4. The system of claim 3 , wherein the designated event comprises adding an opportunity to an account.

5. The system of claim 3 , wherein the designated event comprises adding a task to an opportunity.

6. The system of claim 2 , wherein the at least one post rule is a pre-defined system rule associated with a workflow.

7. The system of claim 2 , wherein the at least one post rule comprises an auto-post rule associated with at least one of: a new opportunity for an account, a new opportunity for a contact, an opportunity updated for an account or an opportunity updated for a contact.

8. The system of claim 1 , wherein identifying the CRM record type of the at least one record comprises:

processing properties associated with the at least one record, the properties comprising values stored in at least one database table.

9. The system of claim 1 , wherein identifying the CRM record type of the at least one record comprises:

reading at least one field of the at least one record, the at least one field associated with the user action.

10. A method comprising:

obtaining, using a database system, data indicating a user action having occurred with respect to at least one customer relationship management (CRM) record stored in at least one CRM database, the user action being related to at least one of: creating the at least one record, updating the at least one record, deleting the at least one record, retrieving the at least one record, performing an assignment with respect to the at least one record, or sharing information related to the at least one record;

identifying, using the database system, the at least one record as being one of a plurality of types of CRM records;

determining, using the database system, that the identified CRM record type of the at least one record is an account or an opportunity designated in the database system as being enabled for storing and/or displaying updates; and

enabling, responsive to determining that the identified CRM record type is the account or the opportunity, storing and/or displaying in a user interface on a user device an update associated with the user action and associated with the at least one record as a post of an activity feed of a feed system associated with the at least one CRM database.

11. The method of claim 10 , wherein determining that the identified CRM record type is the account or the opportunity comprises:

processing at least one post rule associated with the identified CRM record type, the at least one post rule being programmable to be enabled or disabled.

12. The method of claim 11 , wherein the at least one post rule is programmable to create a localized and parameterized auto-post responsive to occurrence of a designated event.

13. The method of claim 12 , wherein the designated event comprises at least one of: adding an opportunity to an account, or adding a task to an opportunity.

14. The method of claim 11 , wherein the at least one post rule is a pre-defined system rule associated with a workflow.

15. A computer program product comprising program code capable of being executed by at least one processor when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause:

obtaining, using a database system, data indicating a user action having occurred with respect to at least one customer relationship management (CRM) record stored in at least one CRM database, the user action being related to at least one of: creating the at least one record, updating the at least one record, deleting the at least one record, retrieving the at least one record, performing an assignment with respect to the at least one record, or sharing information related to the at least one record;

identifying, using the database system, the at least one record as being one of a plurality of types of CRM records;

determining, using the database system, that the identified CRM record type of the at least one record is an account or an opportunity designated in the database system as being enabled for storing and/or displaying updates; and

enabling, responsive to determining that the identified CRM record type is the account or the opportunity, storing and/or displaying in a user interface on a user device an update associated with the user action and associated with the at least one record as a post of an activity feed of a feed system associated with the at least one CRM database.

16. The computer program product of claim 15 , wherein determining that the identified CRM record type is the account or the opportunity comprises:

processing at least one post rule associated with the identified CRM record type, the at least one post rule being programmable to be enabled or disabled.

17. The computer program product of claim 16 , wherein the at least one post rule is programmable to create a localized and parameterized auto-post responsive to occurrence of a designated event.

18. The computer program product of claim 17 , wherein the designated event comprises at least one of: adding an opportunity to an account, or adding a task to an opportunity.

19. The computer program product of claim 16 , wherein the at least one post rule is a pre-defined system rule associated with a workflow.

20. The computer program product of claim 16 , wherein the at least one post rule comprises an auto-post rule associated with at least one of: a new opportunity for an account, a new opportunity for a contact, an opportunity updated for an account or an opportunity updated for a contact.

Continuity (5)
Continuation 15153026 · May 12, 2016
Continuation 14245743 · Apr 4, 2014
Continuation 13025069 · Feb 10, 2011
Provisional Application 61385906 · Sep 23, 2010
Related Publication 20180150482A1 · May 31, 2018
Cited By (1)
US 12,688,165