# US 12,762,109 B2 · Notifications of events of a system of record > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,762,109 B2 - Document ID: US12762109B2 - Status: Granted - Kind: B2 - Application number: 19/202,519 - Filed: 2025-05-08 - Published: 2025-11-27 - Granted: 2026-10-13 - Earliest claimed: 2023-10-17 - Assignees: DevRev, Inc. - Applicants: DevRev, Inc. - Inventors: Brian Byrne; Victor Kamanga; Amisha Kothari - Web page: https://patentgrep.com/patent/US12762109B2 ## CPC - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 16/22: Indexing; Data structures therefor; Storage structures - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Techniques for notifying users of events for objects in a system of record are described. A request to generate the event is received. The event is indicative of a modification of an object. The event is recorded in a timeline table for a timeline of the object. Based on the modified object in the timeline table and a user table, one or more users may be identified. Further, the event is classified to determine a notification type of the one or more users from the user table. All interested users are selected from the one or more users and notified of the event. In an example, the system automatically subscribes users to receive notification of the occurrence of an event for the object. In an example, the one or more users may request to stop receiving the notification of the occurrence of the event for the object. ## Claims ### Claim 1 A system to notify an event for one or more objects deployed in a connected environment having a plurality of distinct ecosystems, the system comprising: a processor to: receive a request from a user to generate the event, wherein the event is indicative of a modification of an object deployed in the connected environment; process the request for the modification of the object to obtain a modified object; record the event in a timeline database that records a history of changes associated with objects in the connected environment, wherein the event is recorded in the timeline database in a timeline table comprising attributes corresponding to events in the history of changes to the objects; publish the timeline table with the modified object for the user; update the event in a user table, wherein an event type of the timeline table is mapped with a notification type in the user table; identify one or more linked users based on the modified object in the timeline table and the user table, wherein the one or more linked users include at least one of a user referenced in the modified object and a user subscribed to receive a notification of an occurrence of the event for the object; determine the notification type of the one or more linked users in the user table, wherein the notification type indicates a user preference to receive the notification of the occurrence of the event for the object; select a user from the one or more linked users based on the user preference; and notify the selected user of the event. ### Claim 2 (depends on 1) The system of claim 1, wherein the modification of the object comprises at least one of: an update in the object, wherein the update is indicative of a change in the object; and a comment in the object; wherein the comment is indicative of at least one of a discussion and a reference in the object. ### Claim 3 (depends on 1) The system of claim 1, wherein the processor is to: ascertain whether the user, creating the request for the event, is included in the user table; add the user in the user table upon ascertaining that the user is not included in the user table; and map the event type of the timeline table with the notification type of the user table for the user. ### Claim 4 (depends on 1) The system of claim 1, wherein the processor is to: automatically subscribe the user to receive a notification of an occurrence of an event for the object. ### Claim 5 (depends on 1) The system of claim 1, wherein the processor is to: receive another request, by the one or more users, to stop receiving the notification of the occurrence of the event for the object based on the user preference; flag the one or more users to stop receiving the notification; and process another request to update the notification type in the user table. ### Claim 6 (depends on 1) The system of claim 1, wherein the processor is to: determine the event type, wherein the event type comprises at least one of a discussion event, a reference event, and a change event; and determine the notification type associated with the event type. ### Claim 7 A method for notifying an event for one or more objects deployed in a connected environment having a plurality of distinct ecosystems, the method comprising: receiving a request from a user to generate the event, wherein the event is indicative of a modification of an object deployed in the connected environment; processing the request for the modification of the object to obtain a modified object; recording the event in a timeline database that records a history of changes associated with objects in the connected environment, wherein the event is recorded in the timeline database in a timeline table comprising attributes corresponding to events in the history of changes to the objects; publishing the timeline table with the modified object for the user; updating the event in a user table, wherein an event type of the timeline table is mapped with a notification type in the user table; identifying one or more linked users based on the modified object in the timeline table and the user table, wherein the one or more linked users include at least one of a user referenced in the modified object and a user subscribed to receive a notification of an occurrence of the event for the object; determining the notification type of the one or more linked users in the user table, wherein the notification type indicates a user preference to receive the notification of the occurrence of the event for the object; selecting a user from the one or more linked users based on the user preference; and notifying the selected user of the event. ### Claim 8 (depends on 7) The method of claim 7, wherein the modification of the object comprises at least one of: creating an update in the object, wherein the update is indicative of a change in the object; and creating a comment in the object; wherein the comment is indicative of at least one of a discussion and a reference in the object. ### Claim 9 (depends on 7) The method of claim 7, further comprising: ascertaining whether the user, creating the request for the event, is included in the user table; adding the user in the user table upon ascertaining that the user is not included in the user table; and mapping the event type of the timeline table with the notification type of the user table for the user. ### Claim 10 (depends on 7) The method of claim 7, further comprising: automatically subscribing the user to receive a notification of an occurrence of an event for the object. ### Claim 11 (depends on 7) The method of claim 7, further comprising: receiving another request, by the one or more users, to stop receiving the notification of the occurrence of the event for the object based on the user preference; flagging the one or more users to stop receiving the notification; and processing another request to update the notification type in the user table. ### Claim 12 (depends on 7) The method of claim 7, wherein for notifying the selected user of the event, the method comprises: determining the event type, wherein the event type comprises at least one of a discussion event, a reference event, and a change event; and determining the notification type associated with the event type. ### Claim 13 A non-transitory computer-readable medium comprising instructions to notify an event for one or more objects deployed in a connected environment having a plurality of distinct ecosystems, the instructions being executable by a processing resource to: receive a request from a user to generate the event, wherein the event is indicative of a modification of an object deployed in the connected environment; process the request for the modification of the object to obtain a modified object; record the event in a timeline database that records a history of changes associated with objects in the connected environment, wherein the event is recorded in the timeline database in a timeline table comprising attributes corresponding to events in the history of changes to the objects; publish the timeline table with the modified object for the user; update the event in a user table, wherein an event type of the timeline table is mapped with a notification type in the user table; identify one or more linked users based on the modified object in the timeline table and the user table, wherein the one or more linked users include at least one of a user referenced in the modified object and a user subscribed to receive a notification of an occurrence of the event for the object; determine the notification type of the one or more linked users in the user table, wherein the notification type indicates a user preference to receive the notification of the occurrence of the event for the object; select a user from the one or more linked users based on the user preference; and notify the selected user of the event. ### Claim 14 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the modification of the object comprises at least one of: an update in the object, wherein the update is indicative of a change in the object; and a comment in the object; wherein the comment is indicative of at least one of a discussion and a reference in the object. ### Claim 15 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the processor is to: ascertain whether the user, creating the request for the event, is included in the user table; add the user in the user table upon ascertaining that the user is not included in the user table; and map the event type of the timeline table with the notification type of the user table for the user. ### Claim 16 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the processor is to: automatically subscribe the user to receive a notification of an occurrence of an event for the object. ### Claim 17 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the processor is to: receive another request, by the one or more users, to stop receiving the notification of the occurrence of the event for the object based on the user preference; flag the one or more users to stop receiving the notification; and process another request to update the notification type in the user table. ### Claim 18 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the processor is to: determine the event type, wherein the event type comprises at least one of a discussion event, a reference event, and a change event; and determine the notification type associated with the event type.