G06F16/2358

Hybrid Runtime Data Object Preventing Intermingling of Data of Different Entities in a Multi-Tenant Environment

Methods, systems, devices, and tangible non-transitory computer readable media facilitating runtime reporting across multiple entities using a multi-tenant database including data of the multiple entities without intermingling the data. In an example embodiment, at a reporting runtime, the disclosed technology can: execute a hybrid class to generate a hybrid runtime data object that can include location-specific reporting data that can correspond to multiple entities and multiple reporting locations; evaluate, with respect to a certain reporting location, a mapping file of the hybrid class to determine whether to retrieve a reporting value of a reporting data field from a first data object corresponding to a first entity or from a second data object corresponding to a second entity; and/or access the first data object or the second data object to retrieve the reporting value based at least in part on evaluation of the mapping file.

SYSTEMS AND METHODS FOR IMPLEMENTING INTELLIGENT LOADING OF DATA

Disclosed is a system for implementing intelligent loading of data in client application database, the system comprising: client device(s) configured to execute client application associated with the client application database and target server communicably coupled to client device(s), wherein, upon start-up, client application is configured to: determine whether data is present or not in client application database, data comprising content of communication thread(s); when data is present in client application database, obtain from target server, updated version of data using first process, wherein the first process is based on recent updates or incremental updates; and when data is not present in client application database, obtain from target server, updated version of data using second process, wherein the second process is based on recent updates.

Orchestration in a multi-layer network
11570122 · 2023-01-31 · ·

Techniques are disclosed relating to creating and managing an information flow within a multi-layer computer network. In various embodiments, a computer system in a first layer within a multi-layer computer network, maintains state information defining an information flow within the multi-layer computer network. In various embodiments, the computer system assigns a particular action (that is included in the information flow) to be performed at a second, different layer of the multi-layer computer network. In various embodiments, the computer system generates program instructions to perform the particular action. The program instructions may be generated using device information accessible to the computer system and indicative of characteristics of a computer system within the second layer. In various embodiments, the computer system in the first layer causes the program instructions to be sent to the computer system in the second layer to perform the particular action as part of the defined information flow.

Method and system for improving efficiency in the management of data references

Methods, computer program products, and computer systems for the management of data references in an efficient and effective manner are disclosed. Such methods, computer program products, and computer systems include receiving a change tracking stream at the computer system, identifying a data object group, and performing a deduplication management operation on the data object group. The change tracking stream is received from a client computing system. The change tracking stream identifies one or more changes made to a plurality of data objects of the client computing system. The identifying is based, at least in part, on at least a portion of the change tracking stream. The data object group represents the plurality of data objects.

COMPUTING SYSTEMS AND METHODS FOR CREATING AND EXECUTING USER-DEFINED ANOMALY DETECTION RULES AND GENERATING NOTIFICATIONS FOR DETECTED ANOMALIES

A computing platform may be installed with software technology for creating and executing user-defined anomaly detection rules that configures the computing platform to: (1) receive, from a client device, data defining a given anomaly detection rule that has been created by a user, wherein the given anomaly detection rule comprises at least one anomaly condition that is to be applied to at least one streaming event queue, (2) store a data representation of the given anomaly detection rule in a data store, (3) convert the data representation of the given anomaly detection rule to a streaming query statement, (4) iteratively apply the streaming query statement to the at least one streaming event queue, and (5) while iteratively applying the streaming query statement, make at least one determination that the at least one anomaly condition is satisfied and then cause at least one anomaly notification to be issued to the user.

Concurrent update management

Aspects of the present disclosure relate to managing concurrent updates on data. A transactional update on at least one record within a data set is detected. A log is generated for the transactional update, the log including an image of the at least one record within the data set before the transactional update. A batch update is detected. A determination is made whether the batch update collides with the transactional update by referencing the log. In response to determining that the batch update collides with the transactional update, a collision policy is referenced. A collision action indicated in the collision policy is then issued.

Personalized entity repository

Systems and methods are provided for a personalized entity repository. For example, a computing device comprises a personalized entity repository having fixed sets of entities from an entity repository stored at a server, a processor, and memory storing instructions that cause the computing device to identify fixed sets of entities that are relevant to a user based on context associated with the computing device, rank the fixed sets by relevancy, and update the personalized entity repository using selected sets determined based on the rank and on set usage parameters applicable to the user. In another example, a method includes generating fixed sets of entities from an entity repository, including location-based sets and topic-based sets, and providing a subset of the fixed sets to a client, the client requesting the subset based on the client's location and on items identified in content generated for display on the client.

Product usage discovery signature based on database table content changes

Technology for logging application usage based on monitoring of read or change operations on database elements and then using the information from log data to determine application usage states (for example, active, inactive) in time.

Message Object Traversal In High-Performance Network Messaging Architecture
20230027817 · 2023-01-26 · ·

A communications system implements instructions including maintaining a message object that includes an array of entries. Each entry of the array includes a field identifier, a data type, and a next entry pointer. The next entry pointers and a head pointer establish a linked list of entries. The instructions include, in response to a request to add a new entry to the message object, calculating an index based on a field identifier of the new entry and determining whether the entry at the calculated index within the array of entries is active. The instructions include, if the entry is inactive, writing a data type, field identifier, and data value of the new entry to the calculated index, and inserting the new entry into the linked list. The instructions include, if the entry is already active, selectively expanding the size of the array and repeating the calculating and determining.

TECHNIQUES FOR METADATA UPDATING AND RETRIEVAL

Processing a read request to read metadata from an entry of a metadata page may include: determining whether the metadata page is cached; responsive to determining the metadata page is cached, obtaining the first metadata from the cached metadata page; responsive to determining the metadata page is not cached, determining whether the requested metadata is in a metadata log of metadata changes stored in a volatile memory; and responsive to determining the metadata is the metadata log of metadata changes stored in the volatile memory, obtaining the requested metadata from the metadata log. Processing a write request that overwrites an existing value of a metadata page with an updated value may include: recording a metadata change in the metadata log that indicates to update the metadata page with the updated value; and performing additional processing during destaging that uses the existing value prior to overwriting it with the updated value.