Abstract: Methods and systems are described for intelligently managing hero cards generated for a user profile. In an example, a server can collect user interaction data that measures how a user interacts with system components. The system components can include emails, hero cards, and software applications. The server can analyze the user interaction data to determine whether a new hero card type should be enabled for a user profile, whether an active hero card type should be disabled for the user profile, and whether parameters for action options on hero cards should be changed for the user profile. The server can make changes to hero cards for the user profile so that the user can receive customized hero cards based on the user's behavior.

Abstract: Disclosed are various approaches for workflow service email integration. In some examples, an email application executed on a client device receives an email message that includes a workflow micro application. The workflow micro application has a workflow information component, and evaluation component, and a workflow actions component. The evaluation component identifies a presence or an absence of a management software development kit (SDK) on the client device. The email application renders a user interface that shows or hides a workflow actions interface area based on the presence or absence of the management SDK.

Abstract: Disclosed are various approaches for dynamically creating content to present to a user based on an identified intent, or other context, associated with a message (e.g., email). A message that is received from a message server can be analyzed to identify the message content within the message prior to distributing to the recipient client device. Trained intent identification models can be applied to the identified message content to determine an intent, or other type of context, associated with the message. Upon identifying the intent, the message header can be modified to include the intent prior to forwarding the message to the recipient client device. The client device can then display a user interface including the message and a user interface element corresponding to a third-party service. The user interface element can be dynamically generated to include an action component that upon selection, triggers an action associated with the intent.

Abstract: Disclosed are various embodiments for integrating client applications with hosted applications. For example, an email can be received from an email client. It can then be determined whether the email is associated with a hosted application. In response to a determination that the email is associated with the hosted application, a request can be made to a connector for a calendar object. The calendar object is then received and returned to the email client.

Abstract: Examples described herein can identify items from third-party or backend services, obtain relevant information for those items, and automatically populate hyperlinks relevant to those items in a draft email. A regular expressions search can be executed on the text of a draft email. When a match is found, the email client can request, from a server, an object associated with the matching expression. The server can obtain the object, using one or more connectors that provide access to a backend system, and provide it to the email client. The email client can extract a URL from the object and enter the URL into a links table stored on the user device. The email client can pull the URL from the links table and use it to automatically generate a hyperlink of the regular expression within the body of the draft email.

Abstract: A battery support for a motor vehicle comprising a tray for receiving at least one battery, a device for holding the battery or batteries on the tray, the holding device comprising a flange on a threaded rod, and a device for clamping the flange on the battery or batteries, wherein the clamping device comprises a sleeve slidably mounted on the threaded rod and comprising a collar bearing on the flange, a nut mounted on the threaded rod and bearing on the collar of the sleeve, and the contact surfaces between the nut and the collar of the bushing comprises serrations.

Abstract: Methods and systems are described for intelligently managing hero cards generated for a user profile. In an example, a server can collect user interaction data that measures how a user interacts with system components. The system components can include emails, hero cards, and software applications. The server can analyze the user interaction data to determine whether a new hero card type should be enabled for a user profile, whether an active hero card type should be disabled for the user profile, and whether parameters for action options on hero cards should be changed for the user profile. The server can make changes to hero cards for the user profile so that the user can receive customized hero cards based on the user's behavior.

Abstract: Disclosed are various embodiments for integrating an email client with hosted applications. An email is received from an email client. An image that is a component of the email is identified and sent to an optical character recognition (OCR) service. Extracted text is received from the OCR service. A request for an action object is then sent to a connector for an application, the action object representing a potential action that could be performed with the application based on the extracted text from the OCR service. The action object is then sent to the email client, which is configured to display a prompt allowing a user to perform the action represented by the action object.

Abstract: Systems and methods disclosed herein provide context-based application suggestions to a user in real time. A user device can identify a keyword displayed in an application, such as an email application. The user device can request a card from a connector external to the user device. The connector can identify an application that relates to the keyword and determine a current installation status for the application with respect to the user device. The connector can query a management server at which the user device is enrolled to request the installation status. If the application is not installed on the user device, the connector can instruct the user device to prompt the user to install the application. If the application is installed, the connector can instruct the user device to prompt the user to launch the installed application.

Abstract: Disclosed are various approaches for facilitating single sign-on (SSO) for third-party services that are accessible through messages (e.g., email) received by a user. A user can receive a message that includes an embedded URL or link that opens in a third-party service that requires authentication. Instead of requiring the user to enter authentication credentials for accessing the third-party service, a tunnel service can be used to intercept requests for authentication and redirect the requests to an identity manager that can issue a SSO token following an authentication of the user and device. Upon supplying the third-party service with the SSO token, the user can access the content associated with the third-party service without entering authentication credentials.

Abstract: Disclosed are various embodiments for integrating client applications with hosted applications. For example, an email can be received from an email client. It can then be determined whether the email is associated with a hosted application. In response to a determination that the email is associated with the hosted application, a request can be made to a connector for a calendar object. The calendar object is then received and returned to the email client.

Abstract: Disclosed are various embodiments for integrating client applications with hosted applications. For example, an email can be received from an email client. It can then be determined whether the email is associated with a hosted application. In response to a determination that the email is associated with the hosted application, a request can be made to a connector for a calendar object. The calendar object is then received and returned to the email client.

Abstract: Methods and systems are described for intelligently managing hero cards generated for a user profile. In an example, a server can collect user interaction data that measures how a user interacts with system components. The system components can include emails, hero cards, and software applications. The server can analyze the user interaction data to determine whether a new hero card type should be enabled for a user profile, whether an active hero card type should be disabled for the user profile, and whether parameters for action options on hero cards should be changed for the user profile. The server can make changes to hero cards for the user profile so that the user can receive customized hero cards based on the user's behavior.

Abstract: Methods and systems are described for intelligently managing hero cards generated for a user profile. In an example, a server can collect user interaction data that measures how a user interacts with system components. The system components can include emails, hero cards, and software applications. The server can analyze the user interaction data to determine whether a new hero card type should be enabled for a user profile, whether an active hero card type should be disabled for the user profile, and whether parameters for action options on hero cards should be changed for the user profile. The server can make changes to hero cards for the user profile so that the user can receive customized hero cards based on the user's behavior.

Abstract: Disclosed are various embodiments for integrating an email client with hosted applications. An email is received from an email client. An image that is a component of the email is identified and sent to an optical character recognition (OCR) service. Extracted text is received from the OCR service. A request for an action object is then sent to a connector for an application, the action object representing a potential action that could be performed with the application based on the extracted text from the OCR service. The action object is then sent to the email client, which is configured to display a prompt allowing a user to perform the action represented by the action object.

Abstract: Disclosed are various approaches for workflow service email integration. In some examples, an email application executed on a client device receives an email message that includes a workflow micro application. The workflow micro application has a workflow information component, and evaluation component, and a workflow actions component. The evaluation component identifies a presence or an absence of a management software development kit (SDK) on the client device. The email application renders a user interface that shows or hides a workflow actions interface area based on the presence or absence of the management SDK.

Abstract: Disclosed are various approaches for workflow service email integration. In some examples, a request is transmitted to a workflow service. The request includes workflow content associated with an email message being composed. A workflow micro application associated with the workflow content is received form the workflow service. The workflow micro application is generated using network service data retrieved from a network service. The workflow micro application includes: an information component that renders the network service data for display within the email message. The workflow micro application also includes an evaluation component that evaluates a management status of a client device.

Abstract: Disclosed are various embodiments for integrating client applications with hosted applications. For example, an email can be received from an email client. It can then be determined whether the email is associated with a hosted application. In response to a determination that the email is associated with the hosted application, a request can be made to a connector for a calendar object. The calendar object is then received and returned to the email client.

Abstract: Examples described herein can identify items from third-party or backend services, obtain relevant information for those items, and automatically populate hyperlinks relevant to those items in a draft email. A regular expressions search can be executed on the text of a draft email. When a match is found, the email client can request, from a server, an object associated with the matching expression. The server can obtain the object, using one or more connectors that provide access to a backend system, and provide it to the email client. The email client can extract a URL from the object and enter the URL into a links table stored on the user device. The email client can pull the URL from the links table and use it to automatically generate a hyperlink of the regular expression within the body of the draft email.

Abstract: Disclosed are various approaches for dynamically creating content to present to a user based on an identified intent, or other context, associated with a message (e.g., email). A message that is received from a message server can be analyzed to identify the message content within the message prior to distributing to the recipient client device. Trained intent identification models can be applied to the identified message content to determine an intent, or other type of context, associated with the message. Upon identifying the intent, the message header can be modified to include the intent prior to forwarding the message to the recipient client device. The client device can then display a user interface including the message and a user interface element corresponding to a third-party service. The user interface element can be dynamically generated to include an action component that upon selection, triggers an action associated with the intent.