US 12,231,517 B2
Group-based communication apparatus, method, and computer program product configured to manage draft messages in a group-based communication system
Madeline Shortt, San Francisco, CA (US); and Ryan Greenberg, Montclair, NJ (US)
Assigned to Salesforce, Inc., San Francisco, CA (US)
Filed by Salesforce, Inc., San Francisco, CA (US)
Filed on Jan. 20, 2023, as Appl. No. 18/099,879.
Application 18/099,879 is a continuation of application No. 17/706,405, filed on Mar. 28, 2022, granted, now 11,563,825.
Application 17/706,405 is a continuation of application No. 16/588,646, filed on Sep. 30, 2019, granted, now 11,290,560, issued on Mar. 29, 2022.
Prior Publication US 2023/0164240 A1, May 25, 2023
Int. Cl. H04L 67/5683 (2022.01); H04L 12/18 (2006.01); H04L 51/04 (2022.01); H04L 51/216 (2022.01)
CPC H04L 67/5683 (2022.05) [H04L 12/1813 (2013.01); H04L 51/04 (2013.01); H04L 51/216 (2022.05)] 20 Claims
OG exemplary drawing
 
1. An apparatus comprising:
a processor; and
at least one non-transitory computer-readable media storing instructions that, when executed by the processor, cause the apparatus to:
receive, by one or more servers of a communication platform at a first application programming interface (API) and via a first user interface of a first client associated with a user identifier and a group identifier, a create draft message request associated with a first draft messaging communication, wherein the first draft messaging communication comprises a draft identifier and a first version identifier, wherein the first API is configured to receive requests to at least one of create, update, delete, or sync draft messaging communications, and a second API is configured to receive requests to post messaging communications;
cause, by the one or more servers, the first draft messaging communication to be stored in a communication repository associated with the communication platform;
propagate, by the one or more servers, the first draft messaging communication to at least a second client associated with the user identifier and the group identifier;
responsive at least in part to propagating the first draft messaging communication, cause to be presented, by the one or more servers via a second user interface of the second client, an indication of creation of a new draft messaging communication;
receive, from the second client via the first API, a delete draft request associated with the draft identifier;
conduct a query of the communication repository for all draft messaging communications associated with the draft identifier;
delete all draft messaging communications associated with the draft identifier; and
propagate a delete draft message event associated with the draft identifier to all clients associated with the user identifier and the group identifier.