System and method for automating actions in distributed computing

Patent metadata

Field	Value
Publication number	US-10972564-B2
Application number	US-202016736565-A
Country	US
Kind code	B2
Filing date	Jan 7, 2020
Priority date	May 5, 2017
Publication date	Apr 6, 2021
Grant date	Apr 6, 2021

Abstract

Systems, methods, and media for actions in distributed computing by receiving trigger event specification that defines a trigger event that will cause a notification to be transmitted. A determination is made whether the trigger event has occurred. Responsive to the determination that the trigger event has occurred, a notification is generated. Excess data is removed from the notification. The notification, with the excess data removed, is sent.

First claim

What is claimed is:

1. A system comprising:
non-transitory memory; and
one or more hardware processors configured to read instructions from the non-transitory memory to perform operations comprising:
receiving one or more trigger event specifications that define one or more trigger events that will cause notifications to be transmitted;
determining that the one or more trigger events have occurred;
responsive to the determination that the one or more trigger events have occurred, generating a first notification that uses a first delivery mechanism;
responsive to the determination that the one or more trigger events have occurred, generating a second notification that uses a second delivery mechanism;
determining that excess content is to be included in the first notification based on usage or availability of resources of the first delivery mechanism or the second delivery mechanism;
including the excess content in the first notification; and
sending the first notification and the second notification, wherein the first notification includes the excess content that is not included in the second notification.

2. The system of claim 1 , wherein the first notification comprises information populated from circumstances of the one or more trigger events.

3. The system of claim 1 , wherein the first notification comprises information input in a user interface during receiving the one or more trigger event specifications.

4. The system of claim 1 , wherein the first delivery mechanism comprises a mobile device notification mechanism, a desktop notification mechanism, an email notification mechanism, an audio notification mechanism, or any combination thereof.

5. The system of claim 1 , wherein the one or more trigger events comprise one of the following trigger event types: a selection of a button, new communication in an electronic forum-based conversation, a step in a project has been reached, an automated test in an automated test framework (ATF) has begun, the automated test in the ATF has completed, the automated test in the ATF has failed, or any combination thereof.

6. The system of claim 5 , wherein the first notification corresponds to a first type of the trigger event types, and the second notification has a second type of the trigger event types.

7. The system of claim 1 , wherein the excess content comprises images in the first notification that are excluded from the second notification.

8. The system of claim 1 , wherein the excess content comprises an attachment to the first notification that is excluded from the second notification.

9. The system of claim 1 , wherein the operations comprise:
determining whether the first and second notifications are generated within a threshold time of each other; and
responsive to the determination that the first and second notifications are generated within the threshold time of each other, batching the first and second notifications, wherein sending the first and second notifications comprises sending the batched first and second notifications.

10. The system of claim 1 , wherein the second delivery mechanism comprises a mobile device notification, a desktop notification, an email notification, an audio notification, or any combination thereof.

11. A method, comprising:
determining that a first trigger event has occurred;
responsive to the determination that a first trigger event has occurred, generating a first notification that uses a first delivery mechanism;
determining that a second trigger event has occurred;
responsive to the determination that the second trigger event has occurred, generating a second notification that uses a second delivery mechanism;
determining that the first and second notifications are generated within a threshold time of each other;
responsive to the determination that the first and second notifications are generated within the threshold time of each other, batching the first and second notifications; and
sending the first and second notifications in a batch with the first notification including excess content that is not included in the second notification, wherein the excess content is to be included based on the usage or availability of resources of the first delivery mechanism or the second delivery mechanism.

12. The method of claim 11 , wherein the excess content comprises an attachment that is attached to the first notification and not to the second notification.

13. The method of claim 11 , comprising:
determining that a third and fourth notification are not sent within the threshold time of each other; and
responsive to the determination that the third and fourth notifications are not generated within the threshold time of each other, sending the third and fourth notifications individually for each notification comprises removing excess content in each notification sent separately.

14. The method of claim 11 , wherein the excess content is included in the first notification based at least in part on a notification priority of the first notification being higher than a notification priority of the second notification.

15. The method of claim 14 , wherein sending the second notification comprises inserting an indication of omission of the excess content from the second notification.

16. Tangible, non-transitory, and computer-readable medium having instructions stored thereon that, when executed, are configured to cause one or more processors to:
receive one or more trigger event specifications that defines one or more trigger events that will cause notifications to be transmitted;
determine that the one or more trigger events have occurred;
responsive to the determination that the one or more trigger events have occurred, generate a first notification that uses a first delivery mechanism;
responsive to the determination that the one or more trigger events have occurred, generate a second notification that uses a second delivery mechanism; and
send the first notification and the second notification, wherein the first notification includes excess content that is not included in the second notification, wherein the excess content is to be included based on the usage or availability of resources of the first delivery mechanism or the second delivery mechanism.

17. The tangible, non-transitory, and computer-readable medium of claim 16 , wherein the excess content is included in the first notification based at least in part on the first notification having a higher notification priority than the second notification.

18. The tangible, non-transitory, and computer-readable medium of claim 16 , wherein the first delivery mechanism comprises a mobile device notification mechanism, a desktop notification mechanism, an email notification mechanism, an audio notification mechanism, or any combination thereof.

19. The tangible, non-transitory, and computer readable medium of claim 16 , wherein the availability of the first delivery mechanism or the second delivery mechanism comprises an amount of email box storage available.

20. The tangible, non-transitory, and computer readable medium of claim 16 , wherein the usage or availability of the first delivery mechanism or the second delivery mechanism comprises an amount of cellular data used for the first delivery mechanism or the second delivery mechanism.

Assignees

• Servicenow Inc

Inventors

• Barnard Bryan Mather
• Brennan Mark
• Dias Rebecca Anita
• Rodriguez Natallia Rabtsevich

Classifications

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L51/08 Primary

  Annexed information, e.g. attachments · CPC title

• G06F11/3672

  Test management · CPC title

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• H04L67/55 Primary

  Push-based network services · CPC title