Abstract: An improved data system supports creation of multiple hierarchical database catalogs under a particular account. Users or organizations have the flexibility to organize their data, native or external, into an n-level hierarchy of their choice. There is a root database catalog of the account, and other catalogs (1 or n-levels) are created under it. The data system has extract, transform, and load (ETL) features that allows data to be moved between different data sources and targets.

Abstract: Aspects of the present disclosure are directed to on-device firewall and library agents integrated with secure agents on network connected endpoints. The on-device firewall and library agents enable inline analysis and inspection of data packets using protocol fingerprints generated for the data packets using an on-device malware detection engine. In one aspect, a network device includes a driver configured to capture a plurality of data packets received at the network device; and an on-device malware detection engine configured to receive at least a subset of the plurality of packets, and generate a fingerprint for the subset of the plurality of packets, the fingerprint being indicative of whether the plurality of data packets are associated with an external malware communication.

Abstract: An improved data system supports creation of multiple hierarchical database catalogs under a particular account. Users or organizations have the flexibility to organize their data, native or external, into an n-level hierarchy of their choice. There is a root database catalog of the account, and other catalogs (1 or n-levels) are created under it. The data system has extract, transform, and load (ETL) features that allows data to be moved between different data sources and targets.

Abstract: Aspects of the present disclosure are directed to on-device firewall and library agents integrated with secure agents on network connected endpoints. The on-device firewall and library agents enable inline analysis and inspection of data packets using protocol fingerprints generated for the data packets using an on-device malware detection engine. In one aspect, a network device includes a driver configured to capture a plurality of data packets received at the network device; and an on-device malware detection engine configured to receive at least a subset of the plurality of packets, and generate a fingerprint for the subset of the plurality of packets, the fingerprint being indicative of whether the plurality of data packets are associated with an external malware communication.

Abstract: The examples described herein extend application lifecycle management (ALM) processes (e.g., create, update, delete, retrieve, import, export, uninstall, publish) to user-created application platform components. First and second components are generated within an application platform. The first component is customized at least by indicating whether the first component is subject to localization, defining a layering of the first component, and indicating whether the first component is protected from downstream modification. The second component is customized in accordance with customizing the first component, and is further customized by defining a dependency of the second component on the first component. The components are deployed in a target environment with metadata representing the customizations and enabling the ALM processes.

Abstract: Respective delegation records indicating that a first access controller and a second access controller have been authorized to grant access to a respective set of cells of a table of a storage management service are stored. In response to receiving an access request of a data accessor, permission records indicating that the access controllers have granted permissions to the data accessor to respective subsets of the table's cells are identified. A collection of cells of the table to which the data accessor has been granted access permission is identified using the permission records, and a response to the access request is generated using the collection.

Abstract: Aspects of the present disclosure are directed to on-device firewall and library agents integrated with secure agents on network connected endpoints. The on-device firewall and library agents enable inline analysis and inspection of data packets using protocol fingerprints generated for the data packets using an on-device malware detection engine. In one aspect, a network device includes a driver configured to capture a plurality of data packets received at the network device; and an on-device malware detection engine configured to receive at least a subset of the plurality of packets, and generate a fingerprint for the subset of the plurality of packets, the fingerprint being indicative of whether the plurality of data packets are associated with an external malware communication.

Abstract: Respective delegation records indicating that a first access controller and a second access controller have been authorized to grant access to a respective set of cells of a table of a storage management service are stored. In response to receiving an access request of a data accessor, permission records indicating that the access controllers have granted permissions to the data accessor to respective subsets of the table's cells are identified. A collection of cells of the table to which the data accessor has been granted access permission is identified using the permission records, and a response to the access request is generated using the collection.

Abstract: A federated permission management service provides clients with customized access to a data set using customized authorization metadata. The federated permission management service may define and apply permissions that are defined at a data lake that provides access to many different data sets from many different sources, as well as those permissions that may be defined at the source of the data set, which may be provided when performing a data sharing request. By allowing for permissions to be specified at the data lake in addition to permissions specified at a source of a data set, the permission management service can provide a fine-grained access control to specific objects of the data set, such as specific columns, specific rows, or specific cells of a database to be shared, even for those data sets in the data lake having different sources.

Abstract: The examples described herein extend application lifecycle management (ALM) processes (e.g., create, update, delete, retrieve, import, export, uninstall, publish) to user-created application platform components. First and second components are generated within an application platform. The first component is customized at least by indicating whether the first component is subject to localization, defining a layering of the first component, and indicating whether the first component is protected from downstream modification. The second component is customized in accordance with customizing the first component, and is further customized by defining a dependency of the second component on the first component. The components are deployed in a target environment with metadata representing the customizations and enabling the ALM processes.

Abstract: The examples described herein extend application lifecycle management (ALM) processes (e.g., create, update, delete, retrieve, import, export, uninstall, publish) to user-created application platform components. First and second components are generated within an application platform. The first component is customized at least by indicating whether the first component is subject to localization, defining a layering of the first component, and indicating whether the first component is protected from downstream modification. The second component is customized in accordance with customizing the first component, and is further customized by defining a dependency of the second component on the first component. The components are deployed in a target environment with metadata representing the customizations and enabling the ALM processes.

Abstract: Deployment of a software unit into a software application layer stack using deployment parameters including an ordering behavior parameter and a reference parameter. The deployment of the software unit may be in response to receipt of a software package for installation of the software unit. Installation of the software unit may be provided according to a hierarchical rule structure that includes determining whether the software unit comprises an upgrade or a patch to an existing software unit in the layer stack. If not an upgrade or a patch, an ordering behavior parameter may indicate a relative position to install the software unit in relation to a software unit designated by the reference parameter. If the deployment parameters are not valid, installation of the software unit may be provided according to a default rule.

Abstract: The examples described herein extend application lifecycle management (ALM) processes (e.g., create, update, delete, retrieve, import, export, uninstall, publish) to user-created application platform components. First and second components are generated within an application platform. The first component is customized at least by indicating whether the first component is subject to localization, defining a layering of the first component, and indicating whether the first component is protected from downstream modification. The second component is customized in accordance with customizing the first component, and is further customized by defining a dependency of the second component on the first component. The components are deployed in a target environment with metadata representing the customizations and enabling the ALM processes.

Abstract: Deployment of a software unit into a software application layer stack using deployment parameters including an ordering behavior parameter and a reference parameter. The deployment of the software unit may be in response to receipt of a software package for installation of the software unit. Installation of the software unit may be provided according to a hierarchical rule structure that includes determining whether the software unit comprises an upgrade or a patch to an existing software unit in the layer stack. If not an upgrade or a patch, an ordering behavior parameter may indicate a relative position to install the software unit in relation to a software unit designated by the reference parameter. If the deployment parameters are not valid, installation of the software unit may be provided according to a default rule.

Abstract: A method and a device for direct launching of an interface to selected functionalities of an application are provided. The method includes receiving a user input gesture on an application icon, displaying a plurality of user interface (UI) elements on the application icon, in response to the received user input gesture, wherein each of the plurality of UI elements corresponds to at least one functionality of an application, receiving a user selection of at least one UI element of the plurality of UI elements, and launching the functionality corresponding to the selected UI element.

Abstract: Methods, systems, and computer program products are described herein for implementing a workflow development system that enables users to incorporate custom functionality within a workflow. During runtime execution of the workflow, the custom functionality (e.g., custom code) is executed in a sandboxed environment, thereby ensuring that the custom code consumes only a limited amount of computing resources (e.g., processing power, memory, storage, etc.) that may be shared with other processes. The foregoing may be achieved without requiring the user to be aware that a sandboxed environment is being utilized. Instead, the user simply needs to select and associate a custom function with a particular workflow step, and the workflow development system manages the interactions with the sandboxed environment without any further user involvement.

Abstract: Embodiments are directed to connectors that use a common contract to expose data sources to applications. The common contract provides access to a plurality of different dataset types without requiring the applications to know the specific dataset type used by the data sources.

Abstract: The cell phone holder is an adjustable casing. The cell phone holder contains a cellular phone. The cell phone holder is removably attached to an automobile. The dimensions of the cell phone holder are adjustable such that the cell phone holder will accommodate cellular phones of various sizes. The cell phone holder comprises a first spring, a second spring, a first side panel, a second side panel, a rear panel, and a bottom panel. The first side panel attaches to the first spring. The second side panel attaches to the second spring. The bottom panel, the first spring, and the second spring attach to the rear panel.

Abstract: The various example embodiments herein disclose a method and apparatus for controlling at least one device by a wearable device, the method comprising determining a position of the wearable device on a finger of a user based on a biometric parameter of the finger, activating a profile corresponding to the determined position of the wearable device on the user's finger; and controlling the at least one device based on the activated profile.

Abstract: A method and a device for direct launching of an interface to selected functionalities of an application are provided. The method includes receiving a user input gesture on an application icon, displaying a plurality of user interface (UI) elements on the application icon, in response to the received user input gesture, wherein each of the plurality of UI elements corresponds to at least one functionality of an application, receiving a user selection of at least one UI element of the plurality of UI elements, and launching the functionality corresponding to the selected UI element.