US 10,769,119 B2Granted

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

Assigneesalesforce.com, inc.

InventorsWilliam Gradin, Matthew Davidchuk, Qiu Ma, Leonid Zemskov, Amy Palke

Life of this patent

Estimating the term…

Loading patent…

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.

Claims20

Dependent claims

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.

4 more elements

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.

3 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/794,698Filed 26 Oct 2017 · continuation
Priority: 23 Sep 2010
Published: US 2018/0150482 A131 May 2018
Granted: 8 Sep 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification8 codes

G06F 16/21
Of structured data, e.g. relational data: design, administration or maintenance of databases
G06F 16/23
Of structured data, e.g. relational data: updating
G06F 16/282
Databases characterised by their database models, e.g. relational or object models: hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
G06F 16/90
Information retrieval; Database structures therefor; File system structures therefor: details of database functions independent of the retrieved…

Family

Application61/385,906Us provisional application · filed 23 Sep 2010
Application13/025,069Parent of this continuation · filed 10 Feb 2011
Application14/245,743Parent of this continuation · filed 4 Apr 2014
US 8,732,150 B2Parent of this continuation · filed 20 May 2014
Application15/153,026Parent of this continuation · filed 12 May 2016
US 9,367,643 B2Parent of this continuation · filed 14 Jun 2016
US 2018/0150482 A1Pre-grant publication · published 31 May 2018
US 9,830,340 B2Parent of this continuation
US 2012/0078981 A1Published application
US 2014/0222814 A1Published application
US 2016/0253360 A1Published application
US 10,769,119 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key