Abstract: Techniques are disclosed relating to determining whether to utilize an alternative query plan for a subsequent execution of a database query. A computer system accesses a trace record detailing an execution of the database query in accordance with a first query plan selected by a query optimizer. The computer system may determine, based on the trace record, whether the execution of the database query satisfies a set of performance criteria. In response to determining that the execution of the database query does not satisfy the set of performance criteria, the computer system may determine whether one or more alternative query plans for the query include a second query plan that is predicted to be more performant than the first query plan. The computer system may provide an instruction to utilize the second query plan in place of the first query plan for the subsequent execution of the database query.

Abstract: Methods, systems, apparatuses, devices, and computer program products are described. A communication process flow management service may display a set of actions associated with a communication process flow configured to manage communications for a tenant. To update a segment of entities on which the communication process flow is to be executed, a user may navigate to a separate browser tab from that of the communication process flow management service, and may update the segment using an entity segmentation service. The communication process flow management service may receive an indication from an entity segmentation service that a segment of entities is updated and display a notification or a toast popup indicating the segment update to a user interface.

Abstract: A computing system may process entity name variations. The entity name variations may be transformed into vector representations. The vector representations may be stored in a database. The entity name variations may be clustered into groups of similar entity name variations based on a similarity metric between the vector representations. A canonical identifier for each group of similar entity name variations may be stored in the database. Each canonical identifier identifying a distinct entity.

Abstract: Techniques are disclosed relating to determining query plans for execution by database systems. In various embodiments, a query optimizer determines a first query plan to implement a query requesting data from a database system. The determining includes selecting one of a plurality of query plans evaluated based on a cost analysis and caching plan fragments of the unselected query plans. The database system can then determine a second query plan for the query by replacing a plan fragment in the first query plan with one of the cached plan fragments of the unselected query plans.

Abstract: A method and apparatus for autonomous configuration-based release orchestration. A first engine obtains stagger configuration data that includes an indication of container clusters in each stagger and a stagger order, selects a current stagger based on the order, and attempts to deploy the feature release to the current stagger by causing an app config update to be sent to a second engine within each container cluster of the current stagger, and receives an indication of success or failure of the attempted deployment of the feature release to the current stagger. Responsive to the indication of success or failure, the first engine performs one of a plurality of actions that include attempting to deploy the feature release to a next one of the staggers according to the order responsive to the indication indicating success, and causing a roll back of the current stagger responsive to the indication indicating failure.

Abstract: Techniques for providing a collaborative document in association with a virtual meeting on a communication platform are discussed herein. Users may communicate within the communication platform via text-based messages, which may include links, documents, videos, etc. Users may request a virtual meeting with audio and/or video capabilities. Responsive to a request, users within the communication channel may be invited to the virtual meeting and the collaborative document. The collaborative document can enable messaging and sharing functionalities attributable to a virtual space. The collaborative document may be populated with communications previously exchanged within the communication channel, such that links, documents, videos, content, etc. that occurred or were shared within the communication channel may be indicated within the collaborative document to provide context to the virtual meeting.

Abstract: Apparatus and method for dynamic and persistent data sharing between cloud services. To address limitations in existing systems, resource provisioning and application deployment pipelines are configured with calls to share data using a configuration service. In some implementations, the configuration service includes an API, which is called by one or more stages of the resource provisioning pipeline to write configuration data in key-value pairs (e.g., data related to resource provisioning). One or more stages of the application deployment pipeline are configured with calls to access the configuration data. The stages then use the configuration data for application deployment. The configuration service manages the key-value store using versioning, repeatability, and immutability, to ensures that a configuration generated by any pipeline execution can be automatically re-used by another pipeline, at execution time.

Abstract: Techniques and mechanisms described herein relate to a database system. A digital asset referenced in one or more database tables within an on-demand database system accessible to a plurality of entities may be identified. The digital asset may be owned by a first one of the plurality of entities. A smart contract that includes a token identifying the digital asset may be generated. The smart contract may be recorded within a distributed trust ledger. The token may be owned by a first account within the distributed trust ledger. The on-demand database system may include a correspondence linking the first entity with the first account. The on-demand database system may be updated to include a reference linking the digital asset with the token.

Abstract: Techniques are disclosed relating to database configuration settings overrides. In some embodiments, a database system stores a set of default configuration settings that control operation of the database system. The database system receives a query requesting data from the database system, and metadata about the query. The database system determines, based on the query and the metadata, that a configuration settings override has been specified for the query, where the configuration settings override indicates that one or more of the default configuration settings are to be replaced with one or more configuration settings specific to the query. In response to the determining that a configuration settings override has been specified, the database system executes the query using the one or more specific configuration settings.

Abstract: A computer system monitors for a change in a first data output generated by execution of a predefined dataflow. In accordance with a determination that the first data output has changed and the first data output meets triggering criteria, the computer system triggers execution of a predefined second dataflow distinct from the first dataflow. The execution of the second dataflow is dependent on the change in the first data output generated by the first dataflow. In accordance with a determination that the first data output has changed and the first data output does not meet triggering criteria, the computer system forgoes triggering execution of the second data flow. In accordance with a determination that the first data output has not changed, the computer system forgoes triggering execution of the second dataflow.

Abstract: Techniques described herein support component maintenance that accounts for a similarity between characteristics of different components. To identify components with similar characteristics, one or more techniques described herein support generation of a data structure (e.g., a tree) that represents a component, where each characteristic may be represented in a different leaf node. The system may generate a similarity score, or value (e.g., as a percentage), between multiple components based on comparing individual nodes of a tree representing each component, respectively. If the similarity score satisfies a threshold, then the system may display, at the UI, a message indicating to a user to preferentially implement one component over another.

Abstract: A conversational artificial intelligence (AI) point-of-sale (POS) system uses generative AI to help a store associate complete tasks in a retail environment. This POS system combines four technologies: (1) speech recognition; (2) natural language processing; (3) acting in response to verbal command in the context of a retail store and a POS device; and (4) providing bi-directional and fully conversational responses. The AI, which runs in an app on a smartphone, tablet, or other mobile device, uses a machine learning (ML) model, such as a small language model (SLM) or large language model (LLM), that is trained against support tickets and other product documentation. The AI understands dependencies (e.g., the tills should be reconciled before closing the store) and predict appropriate responses to conversational inputs.

Abstract: Examples include a system and computer-implemented method to receive a notification from an application programming interface (API) of creation of a just in time (JIT) grant, the JIT grant defining a request for a user to be authorized to access a cluster according to a JIT policy; determine if access to the cluster by the user is authorized according to the JIT policy; grant access to the user to the cluster when access is authorized according to the JIT policy; and send a notification to the API that access by the user to the cluster is granted.

Abstract: Systems, devices, and techniques are disclosed for automation with composable asynchronous tasks. A prompt may be received at a computing device. Using a first large language model (LLM) composable asynchronous tasks may be determined from the prompt. One of the composable asynchronous tasks may use a second LLM. The composable asynchronous tasks may be performed. Performing one of the composable asynchronous tasks may include generating a first output with the second LLM based on the prompt and validating the first output of the LLM. Performing another of the composable asynchronous tasks may include generating a second output using the first output.

Abstract: Methods, systems, and devices for data processing are described. A federation management service may receive a user input indicating multiple data sources as federation inputs into federated application programming interface (API). The one or more data sources may have a first metadata input that defines a target schema for a computed field and a second metadata input that defines a transformation for computing a value for the computed field from a data source schema to the target schema for the computed field. A runtime service of the federation management service may compute the value of the computed field using the second metadata input. The federation management service may generate the federated API from the data sources, where the federated API includes the computed field.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for processing consent information. A data consolidation system obtains, from each of two or more computing systems, a corresponding set of data objects such that two or more sets of objects are obtained. Each data object is associated with a corresponding individual and includes consent information indicating whether the individual consents to an action in relation to corresponding contact information of the individual. Consent information is extracted, for at least one individual, from the sets of data objects such that two or more sets of consent information are collected, the sets of consent information including a first set of consent information corresponding to a first computing system and a second set of consent information corresponding to a second computing system.