US 12,066,986 B2
Methods and apparatus for suppressing network feed activities using an information feed in an on-demand database service environment
William Gradin, San Francisco, CA (US); Matthew Davidchuk, San Francisco, CA (US); Qiu Ma, San Leandro, CA (US); Leonid Zemskov, San Mateo, CA (US); and Amy Palke, Oakland, CA (US)
Assigned to Salesforce, Inc., San Francisco, CA (US)
Filed by salesforce.com, inc., San Francisco, CA (US)
Filed on Sep. 21, 2022, as Appl. No. 17/934,015.
Application 17/934,015 is a continuation of application No. 16/947,360, filed on Jul. 29, 2020, granted, now 11,487,718.
Application 16/947,360 is a continuation of application No. 15/794,698, filed on Oct. 26, 2017, granted, now 10,769,119, issued on Sep. 8, 2020.
Application 15/794,698 is a continuation of application No. 15/153,026, filed on May 12, 2016, granted, now 9,830,340, issued on Nov. 28, 2017.
Application 15/153,026 is a continuation of application No. 14/245,743, filed on Apr. 4, 2014, granted, now 9,367,643, issued on Jun. 14, 2016.
Application 14/245,743 is a continuation of application No. 13/025,069, filed on Feb. 10, 2011, granted, now 8,732,150, issued on May 20, 2014.
Claims priority of provisional application 61/385,906, filed on Sep. 23, 2010.
Prior Publication US 2023/0085714 A1, Mar. 23, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/21 (2019.01); G06F 16/23 (2019.01); G06F 16/28 (2019.01); G06F 16/90 (2019.01); G06F 16/903 (2019.01); G06F 16/9035 (2019.01); G06F 16/906 (2019.01)
CPC G06F 16/21 (2019.01) [G06F 16/23 (2019.01); G06F 16/282 (2019.01); G06F 16/90 (2019.01); G06F 16/903 (2019.01); G06F 16/9035 (2019.01); G06F 16/906 (2019.01)] 20 Claims
OG exemplary drawing
 
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.