G06F2209/545

CUSTOM COMPONENTS IN A DATA-AGNOSTIC DASHBOARD RUNTIME

A method implements a dashboard runtime that comprises a custom visualization component to render a visual representation of a data items of one or more queried datasets in a GUI; at least one query associated with at least the custom component; and an API to provide communication between the custom component and the at least one query. The API detects a user interaction with of a portion of the custom component via a first message that informs the dashboard runtime of the detected user interaction; passes a second message to the at least one query instructing the at least one query to rerun to receive an updated query dataset; and passes the updated dataset via a third message to the custom component and to any other components associated with the at least one query, such that the custom component and the other components automatically render updated visual representations of the updated dataset.

MULTI-PRESENCE APPLICATION ARCHITECTURE
20230044823 · 2023-02-09 ·

A principal application may be executed on a principal computing device. A surrogate application may be executed on a surrogate computing device. The surrogate application running on the surrogate computing device may be a surrogate for the principal application running on the principal computing device. The principal application running on the principal computing device and the surrogate application running on the surrogate computing device may form multiple presences of the principal application on separate computing devices. Information may be relayed between the principal application running on the principal computing device and the surrogate application running on the surrogate computing device.

Issue tracking system having temporary notification suppression corresponding to group activity
11709721 · 2023-07-25 · ·

An issue tracking system configured to track issues, tickets, or tasks is described herein. The issue tracking system may be used to create, modify, and delete issue records during a live meeting or event. The issue tracking system may be adapted to determine a likelihood of user attendance or user proximity and, in accordance with the likelihood exceeding a threshold or meeting a criteria, suppress transmission of notifications to a subset of user devices. Normal or unsuppressed notification transmission is maintained to another subset of user devices.

MANAGING CONTACT-CONTROL PRIVILEGES VIA MANAGING CLIENT DEVICE INTERFACES

The present disclosure relates to systems, non-transitory computer-readable media, and methods for dynamically providing a activity dashboard for display within a graphical user interface. In particular, the disclosed systems can intelligently display, within the activity dashboard, insights of digital activity within an application of a child account. For example, the disclosed systems can monitor digital activity associated with recent contacts and groups, contact updates, and digital media items exchanged in messaging chat threads. In turn, the disclosed system can selectively surface one or more portions (and/or indications) of the monitored digital activity in the activity dashboard along with corresponding actionable options available for user selection. In response to user interaction with the actionable options corresponding to the selectively surfaced digital activity, the disclosed systems can intuitively modify the child account to regulate viewable content and digital communications with third-party child accounts.

Distributed remote network systems for processing resource center operations
11570177 · 2023-01-31 · ·

A remote distributed system for processing resource center operations by extracting one or more interaction entity profiles from one or more resource entity systems, store the one or more interaction entity profiles in a repository in the memory of the distributed remote networks systems, identifying that at least one third party entity system is requesting permission to access at least one interaction entity profile, where in the at least one third party entity system is associated with a resource center, authenticating the at least one third party system and displaying, via a graphical user interface, the at least one interaction entity profile on the at least one third party system, wherein the at least one interaction entity profile is used by the at least one third party entity to process interactions associated with the resource entity and an interaction entity associated with the at least one interaction entity profile.

DETERMINING WHETHER AND/OR WHEN TO PROVIDE NOTIFICATIONS, BASED ON APPLICATION CONTENT, TO MITIGATE COMPUTATIONALLY WASTEFUL APPLICATION-LAUNCHING BEHAVIOR
20230229530 · 2023-07-20 ·

Implementations set forth herein relate to intervening notifications provided by an application for mitigating computationally wasteful application launching behavior that is exhibited by some users. A state of a module of a target application can be identified by emulating user inputs previously provided by the user to the target application. In this way, the state of the module can be determined without visibly launching the target application. When the state of the module is determined to satisfy criteria for providing a notification to the user, the application can render a notification for the user. The application can provide intervening notifications for a variety of different target applications in order to reduce a frequency at which the user launches and closes applications to check for variations in target application content.

Service processing method and apparatus, electronic device, and storage medium

Disclosed are a service processing method and apparatus, an electronic device, and a computer-readable storage medium. The method includes: when receiving a User Interface (UI) request, creating a process instance corresponding to the UI request, and storing instance information of the process instance in a storage module (S101); determining a target process instance from the storage module, and determining a step to be executed of the target process instance based on target instance information of the target process instance (S102); searching, from a register, and executing a target method corresponding to the step to be executed, wherein the register includes all methods compiled according to a preset development specification (S103).

METHOD AND DEVICE FOR ANALYZING FEATURE-LEVEL USAGE OF APP
20230004452 · 2023-01-05 ·

Provided are a method and a device for analyzing feature-level usage of an app.

The method may include: detecting an event generated in a user terminal; extracting a user interface component for the detected event as a layout element; detecting a feature of the app based on the extracted layout element; and analyzing a usage at the detected feature-level.

Methods and user interface generation and application modification
11544085 · 2023-01-03 · ·

A method of generating a user interface for presentation to a user. The method comprises executing a first application computer program to provide a user interface, executing agent computer program code to interrogate and modify said user interface during execution of said first application computer program, and presenting said modified user interface. The first application computer program may be run on a server, while the modified user interface may be presented to a user at a client connected to said server.

Event type-based notification filtering

Technologies for filtering notification content based on event type are provided. The disclosed techniques include causing a plurality of notifications to be presented on a computing device, where the plurality of notifications includes a first notification of a first event type and a second notification of a second event type that is different than the first event type. A plurality of filters is caused to be presented on the computing device, where the plurality of filters includes a first filter that is associated with one or more first event types and a second filter that is associated with one or more second event types. An input that selects the first filter is then received. In response to receiving the input, the one or more first event types are identified. A strict subset of the plurality of notifications that are of one or more of the one or more first event types is identified from among the plurality of notifications. The strict subset of the plurality of notifications is then caused to be presented on the computing device without causing any notifications outside of the strict subset to be presented on the computing device.