# US 2016/0253360 A1 · Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0253360 A1
- Document ID: US20160253360A1
- Status: Published application
- Kind: A1
- Application number: 15/153,026
- Filed: 2016-05-12
- Published: 2016-09-01
- Earliest claimed: 2010-09-23
- Assignees: salesforce.com, inc.
- Applicants: salesforce.com, inc.
- Inventors: William Gradin; Matthew Davidchuk; Qiu Ma; Leonid Zemskov; Amy Palke
- Web page: https://patentgrep.com/patent/US20160253360A1

## CPC

- G06F 16/21: Design, administration or maintenance of databases
- G06F 16/23: Updating
- G06F 16/282: {Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes}
- G06F 16/90: Details of database functions independent of the retrieved data types
- G06F 16/903: Querying (for retrieval from the web G06F16/953)
- G06F 16/9035: Filtering based on additional data, e.g. user or group profiles
- G06F 16/906: Clustering; Classification
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
processing, using a database system, data indicating a user action having occurred with respect to at least one record stored in at least one database of the database system, 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, or communicating information regarding the at least one record;
identifying, using the database system, a record type of the at least one record;
determining, using the database system, that the identified record type of the at least one record is a prohibited record type, the prohibited record type being a calendar event or task; and
prohibiting, responsive to determining that the identified record type is the prohibited record type, at least one of storing or displaying a communication associated with the user action as a feed item of a social network feed of a social networking system associated with the database system to cause the communication to be omitted from the feed when the feed is displayed in a user interface on a user device.

### Claim 22 (depends on 21)

The method of claim 21, wherein identifying the record type of the at least one record comprises:
identifying the record type of the at least one record based on a plurality of properties associated with the at least one record.

### Claim 23 (depends on 22)

The method of claim 22, wherein the properties comprise values stored in at least one database table.

### Claim 24 (depends on 21)

The method of claim 21, wherein identifying the 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.

### Claim 25 (depends on 21)

The method of claim 21, wherein the at least one record is identified by the user action.

### Claim 26 (depends on 21)

The method of claim 21, wherein the at least one record has a hierarchical relationship with a further record identified by the user action.

### Claim 27

A software database system comprising software instructions stored on a non-transitory computer-readable medium, the software instructions configurable to cause:
processing, using the database system, data indicating a user action having occurred with respect to at least one record stored in at least one database of the database system, 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, or communicating information regarding the at least one record;
identifying, using the database system, a record type of the at least one record;
determining, using the database system, that the identified record type of the at least one record is a prohibited record type, the prohibited record type being a calendar event or task; and
prohibiting, responsive to determining that the identified record type is the prohibited record type, at least one of storing or displaying a communication associated with the user action as a feed item of a social network feed of a social networking system associated with the database system to cause the communication to be omitted from the feed when the feed is displayed in a user interface on a user device.

### Claim 28 (depends on 27)

The software database system of claim 27, wherein identifying the record type of the at least one record comprises:
identifying the record type of the at least one record based on a plurality of properties associated with the at least one record.

### Claim 29 (depends on 28)

The software database system of claim 28, wherein the properties comprise values stored in at least one database table.

### Claim 30 (depends on 27)

The software database system of claim 27, wherein identifying the 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.

### Claim 31 (depends on 27)

The software database system of claim 27, wherein the at least one record is identified by the user action.

### Claim 32 (depends on 27)

The software database system of claim 27, wherein the at least one record has a hierarchical relationship with a further record identified by the user action.

### Claim 33

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:
processing, using a database system, data indicating a user action having occurred with respect to at least one record stored in at least one database of the database system, 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, or communicating information regarding the at least one record;
identifying, using the database system, a record type of the at least one record;
determining, using the database system, that the identified record type of the at least one record is a prohibited record type, the prohibited record type being a calendar event or task; and
prohibiting, responsive to determining that the identified record type is the prohibited record type, at least one of storing or displaying a communication associated with the user action as a feed item of a social network feed of a social networking system associated with the database system to cause the communication to be omitted from the feed when the feed is displayed in a user interface on a user device.

### Claim 34 (depends on 33)

The computer program product of claim 33, wherein identifying the record type of the at least one record comprises:
identifying the record type of the at least one record based on a plurality of properties associated with the at least one record.

### Claim 35 (depends on 34)

The computer program product of claim 34, wherein the properties comprise values stored in at least one database table.

### Claim 36 (depends on 33)

The computer program product of claim 33, wherein identifying the 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.

### Claim 37

A system comprising:
a database system implemented using a server system, the database system configurable to cause:
processing, using the database system, data indicating a user action having occurred with respect to at least one record stored in at least one database of the database system, 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, or communicating information regarding the at least one record;
identifying, using the database system, a record type of the at least one record;
determining, using the database system, that the identified record type of the at least one record is a prohibited record type, the prohibited record type being a calendar event or task; and
prohibiting, responsive to determining that the identified record type is the prohibited record type, at least one of storing or displaying a communication associated with the user action as a feed item of a social network feed of a social networking system associated with the database system to cause the communication to be omitted from the feed when the feed is displayed in a user interface on a user device.

### Claim 38 (depends on 37)

The system of claim 37, wherein identifying the record type of the at least one record comprises:
identifying the record type of the at least one record based on a plurality of properties associated with the at least one record.

### Claim 39 (depends on 38)

The system of claim 38, wherein the properties comprise values stored in at least one database table.

### Claim 40 (depends on 37)

The system of claim 37, wherein identifying the 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.
