Granted Patent B2

US 12,231,517 · App. 18/099,879 · Granted Feb 18, 2025

Inventors: Madeline Shortt (San Francisco, CA); Ryan Greenberg (Montclair, NJ)

Assignee: Salesforce, Inc.

H04L67/5683H04L12/1813H04L51/04H04L51/216

Abstract

Claims (67)

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.

2. The apparatus of claim 1 , wherein the delete draft request is received via the second user interface or via a third user interface of the second client.

3. The apparatus of claim 1 , wherein the draft identifier comprises a first draft identifier, the instructions further causing the apparatus to:

receive, from the second client, an update draft message request associated with a second draft messaging communication, wherein the second draft messaging communication comprises the user identifier, a second draft identifier, and a second version identifier;

determine that the second draft messaging communication satisfies a draft message validation rule, wherein determining that the second draft messaging communication satisfies the draft message validation rule comprises determining that the first draft identifier is a same draft identifier as the second draft identifier and that the first version identifier is a same version identifier as the second version identifier;

based at least in part on determining that the second draft messaging communication satisfies the draft message validation rule, propagate the second draft messaging communication to all clients associated with the user identifier and the group identifier; and

cause storage of the second draft messaging communication in the communication repository.

4. The apparatus of claim 3 ,

wherein the first draft messaging communication comprises first message metadata that is stored in association with the first draft messaging communication in the communication repository, the first message metadata including the first draft identifier and the first version identifier,

wherein the second draft messaging communication comprises second message metadata that is stored in association with the second draft messaging communication in the communication repository, the second message metadata including the second draft identifier and the second version identifier, and

wherein the second draft messaging communication fails to satisfy the draft message validation rule based at least in part on a determination that the first draft identifier is a same draft identifier as the second draft identifier and that the first version identifier is different from the second version identifier.

5. The apparatus of claim 1 , wherein the create draft message request is received from the first client via a web-based application.

6. The apparatus of claim 1 , wherein the create draft message request is received from the first client via an application executing on the first client.

7. The apparatus of claim 1 , wherein the create draft message request is received via a draft message application programming interface.

8. The apparatus of claim 1 , the instructions further causing the apparatus to propagate the first draft messaging communication to all clients associated with the user identifier and the group identifier.

9. The apparatus of claim 1 , the instructions further causing the apparatus to propagate the first draft messaging communication to all clients associated with the user identifier and the group identifier.

10. A method comprising:

receiving, 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;

causing, by the one or more servers, the first draft messaging communication to be stored in a communication repository associated with the communication platform;

propagating, 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, causing presentation of, 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;

receiving, from the second client via the first API, a delete draft request associated with the draft identifier;

conducting a query of the communication repository for all draft messaging communications associated with the draft identifier;

deleting all draft messaging communications associated with the draft identifier; and

propagating a delete draft message event associated with the draft identifier to all clients associated with the user identifier and the group identifier.

11. The method of claim 10 , wherein causing the first draft messaging communication to be presented via the second user interface of the second client is responsive at least in part to input to the second user interface to a third user interface of the second client.

12. The method of claim 10 , wherein the draft identifier comprises a first draft identifier, and the method further comprising:

receiving, from the second client, an update draft message request associated with a second draft messaging communication, wherein the second draft messaging communication comprises the user identifier, a second draft identifier, and a second version identifier;

determining that the second draft messaging communication satisfies a draft message validation rule wherein determining that the second draft messaging communication satisfies the draft message validation rule comprises determining that the first draft identifier is a same draft identifier as the second draft identifier and that the first version identifier is a same version identifier as the second version identifier;

based at least in part on determining that the second draft messaging communication satisfies the draft message validation rule, propagating the second draft messaging communication to all clients associated with the user identifier and the group identifier; and

causing storage of the second draft messaging communication in the communication repository.

13. The method of claim 12 ,

wherein the first draft messaging communication comprises first message metadata that is stored in association with the first draft messaging communication in the communication repository, the first message metadata including the first draft identifier and the first version identifier,

wherein the second draft messaging communication comprises second message metadata that is stored in association with the second draft messaging communication in the communication repository, the second message metadata including the second draft identifier and the second version identifier, and

wherein the second draft messaging communication fails to satisfy the draft message validation rule based at least on a determination that the first draft identifier is a same draft identifier as the second draft identifier and that the first version identifier is different from the second version identifier.

14. The method of claim 10 , wherein the create draft message request is received from the first client via a web-based application.

15. The method of claim 10 , wherein the create draft message request is received from the first client via an application executing on the first client.

16. One or more non-transitory computer-readable media storing instructions executable by one or more processors, wherein the instructions causing the one or more processors 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 APIis 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 returned by the query; and

propagate a delete draft message event associated with the draft identifier to all clients associated with the user identifier and the group identifier.

17. The one or more non-transitory computer-readable media of claim 16 , wherein causing the first draft messaging communication to be presented via the second user interface of the second client is responsive at least in part to input to the second user interface or to a third user interface of the second client.

18. The one or more non-transitory computer-readable media of claim 16 , wherein the draft identifier comprises a first draft identifier, the instructions further causing the one or more processors to:

receive, from the second client, an update draft message request associated with a second draft messaging communication, wherein the second draft messaging communication comprises the user identifier, a second draft identifier, and a second version identifier;

determine that the second draft messaging communication satisfies a draft message validation rule wherein determining that the second draft messaging communication satisfies the draft message validation rule comprises determining that the first draft identifier is a same as the second draft identifier and that the first version identifier is a same as the second version identifier;

based at least in part on determining that the second draft messaging communication satisfies the draft message validation rule, propagating the second draft messaging communication to all clients associated with the user identifier and the group identifier; and

causing storage of the second draft messaging communication in the communication repository.

19. The one or more non-transitory computer-readable media of claim 18 ,

wherein the first draft messaging communication comprises first message metadata that is stored in association with the first draft messaging communication in the communication repository, the first message metadata including the first draft identifier and the first version identifier,

wherein the second draft messaging communication comprises second message metadata that is stored in association with the second draft messaging communication in the communication repository, the second message metadata including the second draft identifier and the second version identifier, and

wherein the second draft messaging communication fails to satisfy the draft message validation rule based at least in part on a determination that the first draft identifier is a same as the second draft identifier and that the first version identifier is different from the second version identifier.

20. The one or more non-transitory computer-readable media of claim 16 , wherein the create draft message request is received from the first client via a web-based application.

Assignments (3)

Continuity (3)

References Cited (68)