# US 10,769,119 B2 · 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 10,769,119 B2 - Document ID: US10769119B2 - Status: Granted - Kind: B2 - Application number: 15/794,698 - Filed: 2017-10-26 - Published: 2018-05-31 - Granted: 2020-09-08 - 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/US10769119B2 ## 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 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 2) 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. ### Claim 4 (depends on 3) The system of claim 3, wherein the designated event comprises adding an opportunity to an account. ### Claim 5 (depends on 3) The system of claim 3, wherein the designated event comprises adding a task to an opportunity. ### Claim 6 (depends on 2) The system of claim 2, wherein the at least one post rule is a pre-defined system rule associated with a workflow. ### Claim 7 (depends on 2) 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. ### Claim 8 (depends on 1) 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. ### Claim 9 (depends on 1) 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. ### Claim 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. ### Claim 11 (depends on 10) 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. ### Claim 12 (depends on 11) 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. ### Claim 13 (depends on 12) 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. ### Claim 14 (depends on 11) The method of claim 11, wherein the at least one post rule is a pre-defined system rule associated with a workflow. ### Claim 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. ### Claim 16 (depends on 15) 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. ### Claim 17 (depends on 16) 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. ### Claim 18 (depends on 17) 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. ### Claim 19 (depends on 16) The computer program product of claim 16, wherein the at least one post rule is a pre-defined system rule associated with a workflow. ### Claim 20 (depends on 16) 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.