Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment
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.
1. A system comprising:
a database system implemented using a server system, the database system configurable to cause:
detecting an event associated with at least a first customer relationship management (CRM) record stored in at least one database;
identifying a second CRM record stored in the at least one database as having a parent relationship with the first CRM record;
identifying a rule associated with the first and second CRM records, the rule being configurable to:
be enabled or disabled, and
cause automatic sharing of a post regarding the event and the first and second CRM records in a feed in response to the event; and
applying the rule in response to the event, the applying comprising:
generating a post, and
providing the post to the feed.
2. The system of claim 1 , wherein the database system is implemented to include a cloud-based customer relationship management (CRM) system.
3. The system of claim 1 , wherein the event includes at least one of: creation of an account, or closure of a won opportunity.
4. The system of claim 1 , wherein the post is generated if at least one attribute is specified, the at least one attribute including at least one of: a customer ID, a parent account ID or a parent contact ID.
5. The system of claim 1 , wherein the second CRM record has a set of attributes, and each attribute represents a data item of a particular type.
6. The system of claim 5 , wherein the second CRM record is an account, and the set of attributes includes a name, an address, and an owner ID.
7. The system of claim 1 , wherein the event includes at least one of: an opportunity being added to an account, a task being added to an opportunity, creation of an opportunity, closure of an account, creation of a lead, closure of a lead, creation of a contact, or closure of a contact.
8. 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:
detecting an event associated with at least a first customer relationship management (CRM) record stored in at least one database;
identifying a second CRM record stored in the at least one database as having a parent relationship with the first CRM record;
identifying a rule associated with the first and second CRM records, the rule being configurable to:
be enabled or disabled, and
cause automatic sharing of a post regarding the event and the first and second CRM records in a feed in response to the event; and
applying the rule in response to the event, the applying comprising:
generating a post, and
providing the post to the feed.
9. The computer program product of claim 8 , wherein the at least one database is implemented with a cloud-based customer relationship management (CRM) system.
10. The computer program product of claim 8 , wherein the event includes at least one of: creation of an account, or closure of a won opportunity.
11. The computer program product of claim 8 , wherein the post is generated if at least one attribute is specified, the at least one attribute including at least one of: a customer ID, a parent account ID or a parent contact ID.
12. The computer program product of claim 8 , wherein the second CRM record has a set of attributes, and each attribute represents a data item of a particular type.
13. The computer program product of claim 12 , wherein the second CRM record is an account, and the set of attributes includes a name, an address, and an owner ID.
14. The computer program product of claim 8 , wherein the event includes at least one of: an opportunity being added to an account, a task being added to an opportunity, creation of an opportunity, closure of an account, creation of a lead, closure of a lead, creation of a contact, or closure of a contact.
15. A computer-implemented method comprising:
detecting an event associated with at least a first customer relationship management (CRM) record stored in at least one database;
identifying a second CRM record stored in the at least one database as having a parent relationship with the first CRM record;
identifying a rule associated with the first and second CRM records, the rule being configurable to:
be enabled or disabled, and
cause automatic sharing of a post regarding the event and the first and second CRM records in a feed in response to the event; and
applying the rule in response to the event, the applying comprising:
generating a post, and
providing the post to the feed.
16. The method of claim 15 , wherein the at least one database is implemented with a cloud-based customer relationship management (CRM) system.
17. The method of claim 15 , wherein the event includes at least one of: creation of an account, or closure of a won opportunity.
18. The method of claim 15 , wherein the post is generated if at least one attribute is specified, the at least one attribute including at least one of: a customer ID, a parent account ID or a parent contact ID.
19. The method of claim 15 , wherein the second CRM record has a set of attributes, and each attribute represents a data item of a particular type.
20. The method of claim 19 , wherein the second CRM record is an account, and the set of attributes includes a name, an address, and an owner ID.