IP Library › Granted Patent US 11,954,088
Granted Patent B2
US 11,954,088 · App. 17/162,433 · Granted Apr 9, 2024

Alert feed and subscription management

Inventors: Nathaniel Botwick (San Francisco, CA); Norris Lee (South San Francisco, CA)
Assignee: Salesforce, Inc.
G06F16/2358G06F9/542G06F16/219G06F16/252
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,954,088
App. No.
17/162,433
Granted
Apr 9, 2024
Kind
B2
Abstract

Described herein are a system, apparatus, device, method, and/or computer program product embodiments and/or combinations and sub-combinations thereof for managing alerts and subscriptions in a cloud collaborative system. In one embodiment, a modification notice identifying a change to a field of a record is obtained, and the change is compared with a criterion specified in a subscription for a user. If the change satisfies the criterion, an alert is generated based on the modification notice. An alert GUI is transmitted to a user device to display alerts for the user. The user may access an expanded view of the record through the alert in the alert GUI. The user may also publish the alert to a chat session involving other users of the cloud collaborative system.

Claims (78)

1. A method, comprising:

generating, by one or more processors, a first subscription based on a frequently viewed field accessed by a first user in a collaborative document stored in a cloud collaborative environment, wherein the first subscription specifies a criterion of a change to the frequently viewed field within the collaborative document, and wherein users of the cloud collaborative environment have permissions to collaboratively change the frequently viewed field within the collaborative document from a respective device;

generating, by the one or more processors, an alert based on a first modification notice identifying a change to a first field of the collaborative document, wherein a second user of the cloud collaborative environment changes the collaborative document and the change satisfies a criterion specified in the first subscription for the first user of the cloud collaborative environment; and

inserting, by the one or more processors, the alert in an alert feed configured in an alert graphical user interface (GUI) to display a plurality of alerts for the first user of the cloud collaborative environment.

2. The method of claim 1 , wherein:

the first modification notice comprises a subset of fields of the collaborative document including the first field,

the alert comprises the subset of fields extracted from the first modification notice,

the subset of fields are visible in the alert in the alert feed.

3. The method of claim 2 , wherein first modification notice further comprises a statement with the change, and wherein the statement is visible in the alert in the alert feed.

4. The method of claim 2 , further comprising:

receiving, by the one or more processors, a request for an expanded view of the collaborative document from the first device,

wherein the first modification notice further comprises a link to the expanded view of the collaborative document,

wherein the first alert further comprises the link to the expanded view of the collaborative document extracted from the first modification notice, and

wherein the request for the expanded view is triggered by the first user invoking the link from within the alert GUI.

5. The method of claim 2 , further comprising:

receiving, by the one or more processors, a request to publish a message based on the alert,

wherein the request to publish the message is triggered by the first user invoking a share feature within the alert GUI.

6. The method of claim 1 , further comprising:

determining, by the one or more processors, a frequently viewed column in a plurality of collaborative documents; and

generating, by the one or more processors, a suggested subscription for a second field corresponding to the frequently viewed column,

wherein the alert GUI comprises a subscriptions component configured to display the suggested subscription to the first user.

7. The method of claim 1 , further comprising:

receiving, by the one or more processors, a second modification notice identifying a change to the collaborative document;

comparing, by the one or more processors, the change to the collaborative document with a criterion specified in a second subscription for the first user;

in response to the change to the collaborative document satisfying the criterion specified in the second subscription, generating, by the one or more processors, an additional alert based on the change to the collaborative document for display in the alert feed comprising the plurality of alerts for the first user.

8. The method of claim 1 , further comprising:

storing the alert feed in an alert repository;

determining, by the one or more processors, the first user is operating a second device; and

in response to determining the user is operating the second device:

retrieving the alert feed from the alert repository; and

transmitting the alert GUI and the alert feed to the second device.

9. A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

generate a first subscription based on a frequently viewed field accessed by a first user in a collaborative document stored in a cloud collaborative environment, wherein the first subscription specifies a criterion of a change to the frequently viewed field within the collaborative document, wherein users of the cloud collaborative environment have permissions to collaboratively change the frequently viewed field within the collaborative document from a respective device;

generate an alert based on a first modification notice identifying a change to a first field of the collaborative document, wherein a second user of the cloud collaborative environment changes the collaborative document and the change satisfies a criterion specified in the first subscription for the first user of the cloud collaborative environment; and

insert the alert in an alert feed configured in an alert graphical user interface (GUI) to display a plurality of alerts for the first user.

10. The system of claim 9 , wherein:

the first modification notice comprises a subset of fields of the collaborative document including the first field,

the alert comprises the subset of fields extracted from the first modification notice,

the subset of fields are visible in the alert in the alert feed.

11. The system of claim 10 , wherein first modification notice further comprises a statement with the change, and wherein the statement is visible in the alert in the alert feed.

12. The system of claim 10 , wherein the at least one processor is further configured to:

receive, a request for an expanded view of the collaborative document record from the device,

wherein the first modification notice further comprises a link to the expanded view of the collaborative document,

wherein the alert further comprises the link to the expanded view of the collaborative document extracted from the first modification notice, and

wherein the request for the expanded view is triggered by the first user invoking the link from within the alert GUI.

13. The system of claim 10 , wherein the at least one processor is further configured to:

receive a request to publish a message based on the alert,

wherein the request to publish the message is triggered by the first user invoking a share feature within the alert GUI.

14. The system of claim 9 , wherein the at least one processor is further configured to:

determine a frequently viewed column in a plurality of collaborative documents; and

generate a suggested subscription for a second field corresponding to the frequently viewed column,

wherein the alert GUI comprises a subscriptions component configured to display the suggested subscription.

15. The system of claim 9 , wherein the at least one processor is further configured to:

receive a second modification notice identifying a change to a collaborative document;

compare the change to the collaborative document with a criterion specified in a second subscription for the first user;

in response to the change to the collaborative document satisfying the criterion specified in the second subscription, generate an additional alert based on the change to the collaborative document for display in the alert feed comprising the plurality of alerts for the first user.

16. A non-transitory computer readable medium (CRM) having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

generating a first subscription based on a frequently viewed field accessed by a first user in a collaborative document stored in a cloud collaborative environment, wherein the first subscription specifies a criterion of a change to the frequently viewed field within the collaborative document, and wherein users of the cloud collaborative environment have permissions to collaboratively change the frequently viewed field within the collaborative document from a respective device;

generating an alert based on a first modification notice identifying a change to a first field of the collaborative document, wherein a second user of the cloud collaborative environment changes the collaborative document and the change satisfies criterion specified in the first subscription for the first user of the cloud collaborative environment;

inserting the alert in an alert feed configured in an alert graphical user interface (GUI) to display a plurality of alerts for the first user.

17. The non-transitory CRM of claim 16 , wherein:

the first modification notice comprises a subset of fields of the collaborative document including the first field,

the alert comprises the subset of fields extracted from the first modification notice, and

the subset of fields are visible in the alert in the alert feed.

18. The non-transitory CRM of claim 17 , the operations further comprising:

receiving a request for an expanded view of the collaborative document from the device,

wherein the first modification notice further comprises a link to the expanded view of the collaborative document,

wherein the alert further comprises the link to the expanded view of the collaborative document extracted from the first modification notice, and

wherein the request for the expanded view is triggered by the first user invoking the link from within the alert GUI.

19. The non-transitory CRM of claim 17 , the operations further comprising:

receiving a request to publish a message based on the alert,

wherein the request to publish the message is triggered by the first user invoking a share feature within the alert GUI.

20. The non-transitory CRM of claim 16 , the operations further comprising:

determining a frequently viewed column in a plurality of collaborative documents; and

generating a suggested subscription for a second field corresponding to the frequently viewed column,

wherein the alert GUI comprises a subscriptions component configured to display the suggested subscription to the first user.

Assignments (2)
CHANGE OF NAME Recorded Aug 4, 2026
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 076118/0548 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2021
From: BOTWICK, NATE; LEE, NORRIS
To: SALESFORCE.COM, INC.
Reel/Frame 055213/0893 →
Continuity (2)
Provisional Application 63050658 · Jul 10, 2020
Related Publication 20220012227A1 · Jan 13, 2022