Abstract: Methods and systems are provided that leverage existing information displayed or presented to a user by an app without requiring the integration of new libraries or requiring a user to use a specific app. Rather, methods and systems presented herein identify a task, select an app or multiple apps capable of performing the task, obtain information that may be required by the app or apps, determine a contextual understanding of what is displayed by the selected app or apps, and finally generate and automate the interaction with the app or apps such that the interaction with the app or apps is handled by an automation agent, allowing a user to stay focused on one or more tasks that the user needs to accomplish.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for generating searchable data structures using observational context data are provided. An indication to process observational context data surfaced by a local computing device may be received. The observational context data may comprise display data or audio data. The observational context data may be processed by a context analysis engine. A determination may be made of a current context type occurring on the local computing device. The current context type may be determined from a plurality of context types, each having a semantic data structure comprising a unique set of entity types. A canvas comprising a searchable data structure of the current context type may be generated and populated with objects having entity types corresponding to the current context type. A displayable representation of the canvas may be displayed.

Abstract: An intelligent agent may assume a ghost presence in a meeting on behalf of a non-participant, monitor data communications between participants of the meeting, and identify appropriate triggers or events relating to the non-participant. For example, the agent may detect questions directed at the non-participant or that the non-participant has the knowledge to answer. The non-participant may be auto-summoned with respect to the meeting when the events relating to the non-participant are identified. The auto-summoning may be performed by communicating information about identified event to the non-participant, for example in real-time. The communication about the identified event may be transmitted over any of a variety of communication channels or modalities, including instant message chat, SMS, phone call, establishing a video call, or pager.

Abstract: An intelligent agent may assume a ghost presence in a meeting on behalf of a non-participant, monitor data communications between participants of the meeting, and identify appropriate triggers or events relating to the non-participant. For example, the agent may detect questions directed at the non-participant or that the non-participant has the knowledge to answer. The non-participant may be auto-summoned with respect to the meeting when the events relating to the non-participant are identified. The auto-summoning may be performed by communicating information about identified event to the non-participant, for example in real-time. The communication about the identified event may be transmitted over any of a variety of communication channels or modalities, including instant message chat, SMS, phone call, establishing a video call, or pager.

Abstract: Methods and systems are provided that leverage existing information displayed or presented to a user by an app without requiring the integration of new libraries or requiring a user to use a specific app. Rather, methods and systems presented herein identify a task, select an app or multiple apps capable of performing the task, obtain information that may be required by the app or apps, determine a contextual understanding of what is displayed by the selected app or apps, and finally generate and automate the interaction with the app or apps such that the interaction with the app or apps is handled by an automation agent, allowing a user to stay focused on one or more tasks that the user needs to accomplish.

Abstract: A statement in a software code segment for an application that associates the software code segment to a feature is identified. The software code segment includes a first code block and a second code block for the feature. A feature configuration for the feature is read from a manifest that lists a set of features in the application. When a staging option corresponds to a first staging option, the statement is evaluated against the staging option to remove one of the first code block and the second code block in executable code. When the staging option corresponds to a second staging option, the first software code block and the second code block are included in the executable code. The first code block and the second code block are configurable at runtime to be selected or not selected. The first version or the second version of the executable code are output.

Abstract: A statement in a software code segment for an application that associates the software code segment to a feature is identified. The software code segment includes a first code block and a second code block for the feature. A feature configuration for the feature is read from a manifest that lists a set of features in the application. When a staging option corresponds to a first staging option, the statement is evaluated against the staging option to remove one of the first code block and the second code block in executable code. When the staging option corresponds to a second staging option, the first software code block and the second code block are included in the executable code. The first code block and the second code block are configurable at runtime to be selected or not selected. The first version or the second version of the executable code are output.

Abstract: The use of logic for routing data. Metadata that is associated with data residing on a first computing system is sent to at least a second computing system. The metadata is structured so that when interpreted by the second system, the second system provides an appearance that the data is local. The first system then receives a communication from the second computing system, demonstrating that a user has interacted with the appearance of data on the second system. Logic may be applied to determine how and when to send the data to the second system. Based on the determination made by applying logic, the data is sent to the second system in a manner that is associated with the identifier for the entire data.

Abstract: The use of logic for routing data. Metadata that is associated with data residing on a first computing system is sent to at least a second computing system. The metadata is structured so that when interpreted by the second system, the second system provides an appearance that the data is local. The first system then receives a communication from the second computing system, demonstrating that a user has interacted with the appearance of data on the second system. Logic may be applied to determine how and when to send the data to the second system. Based on the determination made by applying logic, the data is sent to the second system in a manner that is associated with the identifier for the entire data.