Abstract: In one aspect, an example methodology implementing the disclosed techniques includes, by a computing device, receiving clickstream information of a customer visiting a website of an organization, the clickstream information is indicative of an active web session of the customer on the website, and predicting, using a machine learning (ML) model, a propensity of the customer performing a particular action during the active web session on the website. The method also includes, by the computing device, providing proactive customer support to the customer based on the predicted propensity of the customer performing the particular action. The website may be a support website of the organization. The particular action may include contacting technical support of the organization and/or making a purchase during the active web session of the customer on the website.

Abstract: A medical device communication method that may be implemented within a variety of medical devices including but not limited to infusion pumps. The method may be implemented with a protocol stack for at least intra-device communication. Embodiments provide connection-oriented, connectionless-oriented, broadcast and multicast data exchange with priority handling of data, fragmentation, and reassembly of data, unique static and dynamic address assignment and hot swap capability for connected peripherals or subsystems.

Abstract: The present application provides a stateful clutch system for a DC motor connected with self-locking worm gear. The system includes a first gearbox housing for accommodating a motor coil with a gearbox. Further, the system includes a second gearbox housing for accommodating at least one gear and a driving shaft. Specifically, the gear is adapted for displacing inward and outward movement by establishing a connection with a motor shaft. The driving shaft is adapted for locking and unlocking the gear rotation by transferring and stopping torque. Additionally, the DC motor is used for receiving an input signal from a motor driver for rotating in a clockwise direction and an anticlockwise direction. Moreover, the DC motor rotates in a clockwise direction to disengage connection with the gear moving outward which stops the transfer of the torque through the driving shaft.

Abstract: Disclosed herein are system, method, and computer program product embodiments for implementing failure classification and recommendation delivery. An embodiment operates by receiving, by a failure classification and recommendation system, a plurality of conditions and patterns for a plurality of failures associated with one or more applications/functions automated executions using various tools and receiving one or more recommendations for each one of the plurality of failures. The embodiment further includes storing the plurality of conditions and patterns and the one or more recommendations for each one of the plurality of failures. This embodiment can further include receiving a report from a first tool indicating a failure associated with one or more applications/functions automated executions using the first tool and determining a recommendation based on the received report.

Abstract: A threat management facility receives data from a variety of sources such as compute instances within an enterprise network, cloud service providers supporting the enterprise network, and third-party data providers such as geolocation services. In order to facilitate prompt notification of potential risks, the threat management facility may incrementally update data for use in threat assessments as the data becomes available from these different sources, and create suitable alerts or notifications whenever the currently accumulated data provides an indication of threat meeting a predetermined threshold.

Abstract: A threat management system stores an attack matrix characterizing tactics and techniques, and provides threat detection based on patterns of traversal of the attack matrix. Where the threat management system provides a data lake of security events and a query interface for using the data lake to investigate security issues, useful inferences may also be drawn by comparing query activity in the query interface with the patterns of traversal of the attack matrix, such as by using a malicious pattern of traversal to identify a concurrent chain of queries indicative of a threat, or by presenting separate threat scores to an analyst based on query activity and patterns of traversal.

Abstract: A platform for managing threat data integrates threat data from a variety of sources including internal threat data from instrumented compute instances associated with an enterprise network and threat data from one or more independent, external resources. Threat assessments are incrementally revised as this threat data is asynchronously received from various sources, and a threat intervention container is automatically created and presented to an investigator when a composite threat score for one or more of the compute instances meets a predetermined threshold.

Abstract: An asynchronous stream of security events is added to a data lake for enterprise security by identifying groups of related events related to a security threat, and creating rules to fold these related events into a single security event along with metadata. The folding rules may then be applied to security events in the event stream to compress data in the data lake and improve detection efficiency.

Abstract: A platform for threat investigation in an enterprise network receives threat data from managed endpoints, and is augmented with data from cloud computing platforms and other third-party resources. The resulting merged data set can be incrementally updated and used to automatically launch investigations at appropriate times.

Abstract: Systems and methods for namespace masking in an integration flow. In order to mitigate issues arising due to application updates impacting integration flows, during the metadata generation phase, all the elements which are available for operation selection can be cloned and replaced with a new namespace. The original elements are deleted from the metadata. The systems and methods can maintain the original namespace and the element name at a predefined place in the metadata (e.g., as an attribute of the cloned Element). The cloned element in addition to all the original fields of the element, can have one additional field which will store the value of the original namespace.

Abstract: Described herein are systems and methods for suppressing inbound payload to an integration flow of an orchestration based application integration. The systems and methods described herein can, based upon a scan of an integration, identify and exclude from memory certain portions of one or more payloads that are received at the integration flow.

Abstract: In accordance with an embodiment, described herein are systems and methods identifying capabilities and limitations of an orchestration based application integration. The systems and methods described herein can detect and publish/expose such a set of limitations and capabilities of the adapters/connectors to the integration platform. In this way, such metadata can be used, for example, by a user of an integration system in designing an integration of applications, or in selecting an orchestration, based upon, e.g., the published metadata that indicates the capabilities of the individual adapters/connectors, or the orchestration as a whole (or parts thereof). This way, once an orchestration is active for processing requests, then it can also publish a metadata considering the metadata of involved adapters. This metadata can be used in adjusting requests to an integration.

Abstract: Systems and methods for supporting rollback of changes made to target systems via an integration platform. Systems and methods can support reverting changes made to target applications via an integration platform (e.g., integration platform as a service (iPaaS)) with the help of a rollback activity. In order to aid the development and design of integration orchestrations, the integration platform can provide suggested rollback actions. In case of a failure in integration runtime, this rollback activity will revert changes made to the target applications prior to the point of fault. This helps ensure that systems remain in consistent state.

Abstract: According to some embodiments, a system and method comprising a plurality of automation tools; and a shared automation module, coupled to the plurality of automation tools including: a computer processor; a computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the shared automation module to: receive a selection of a first automation tool of the plurality of automation tools; receive a selection of a second automation tool of the plurality of automation tools; execute the first automation tool to generate a first automation tool output; and execute the second automation tool using the stored first automation tool output to generate a second automation tool output. Numerous other aspects are provided.

Abstract: A medical device communication method that may be implemented within a variety of medical devices including but not limited to infusion pumps. The method may be implemented with a protocol stack for at least intra-device communication. Embodiments provide connection-oriented, connectionless-oriented, broadcast and multicast data exchange with priority handling of data, fragmentation, and reassembly of data, unique static and dynamic address assignment and hot swap capability for connected peripherals or subsystems.

Abstract: Apparatus, systems, and methods are disclosed for cooling an electronic device. An example electronic device includes a chassis including a first cover and a second cover. The example electronic device also includes a first looped frame spaced apart from the first cover, a second looped frame spaced apart from the second cover, and a printed circuit board between the first looped frame and the second looped frame.

Abstract: An adsorbent composition for reducing impurities of heat transfer fluids is provided and a process for the preparation of the same. The adsorbent composition comprises a layered double hydroxide in an amount in the range of 15 to 70 wt % of the total mass of the composition; alumina in an amount in the range of 30 to 85 wt % of the total mass of the composition; and optionally activated bauxite in an amount in the range of 15 to 50 wt % of the total mass of the composition. The adsorbent composition is economical and eco-friendly, having feed processing capacity in the range of 58 to 600 gm/gm.

Abstract: Various embodiments for providing a user interface test and validation system are described herein. An embodiment operates by determining user interface (UI) settings and metadata, and fetching data corresponding to the metadata. A plurality of test procedures corresponding to the UI element are identified. A plurality of states to be present in a rendering of the UI element based on the plurality of test procedures, the metadata, and the data are identified. A rendering of the UI element is validated against the plurality of states. A test report is provided based on the validating.

Abstract: Systems and methods for supporting rollback of changes made to target systems via an integration platform. Systems and methods can support reverting changes made to target applications via an integration platform (e.g., integration platform as a service (iPaaS)) with the help of a rollback activity. In order to aid the development and design of integration orchestrations, the integration platform can provide suggested rollback actions. In case of a failure in integration runtime, this rollback activity will revert changes made to the target applications prior to the point of fault.

Abstract: The embodiments described herein provide for methods and systems for removing power supply induced jitter from a Phase Lock Loop to provide a Power Supply Induced jitter-free clock signal to a system-on-a-chip and GDDR6 DRAM interface. In operation, a circuit reduces a DC offset between a reference voltage and a voltage regulator output to identify low frequency noise on the voltage regulator output to apply as negative feedback to reduce the low frequency noise on the voltage regulator output. The bandwidth of the circuit is increased to detect high frequency noise, which is applied as negative feedback on the voltage regulator output. Very high frequency noise is then detected and applied as negative feedback to the voltage regulator output. The circuit outputs a regulated output equal to the reference voltage and immune to the low, high, and very high frequency noise of power delivery network supply to the regulator.