Hero cards that display contextual information and actions for backend systems
Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there.
1. A non-transitory, computer-readable medium containing instructions executed by at least one processor to perform stages for generating hero cards, the stages comprising:
receiving an email within an email application of a user device, the email application being unassociated with a plurality of backend systems;
detecting trigger content within the email by a hero agent of the user device;
sending, by the hero agent, a service request for hero content to a hero server, the service request including the trigger content and authentication tokens associated with the user device to be used by the hero server to determine a subset of backend systems, from the plurality of backend systems, that relate to both the trigger content and at least one of the authentication tokens;
receiving the hero content related to the email, wherein the hero content is not part of the email as originally sent;
displaying a first hero card within a graphical user interface (GUI) of the email application, wherein the first hero card includes at least a portion of the hero content and an action button for performing a function in the backend systems related to both the trigger content and at least one of the authentication tokens.
2. The non-transitory, computer-readable medium of claim 1 , wherein the hero content is received prior to, or concurrent with, delivery of the email to the email application.
3. The non-transitory, computer-readable medium of claim 1 , wherein the stages further comprise:
defining a region for displaying hero cards within the GUI of the email application; and
cycling through multiple hero cards in the region, wherein a second hero card displayed in the region includes different hero content than the first hero card, the different hero content being related to a second email received by the email application.
4. The non-transitory, computer-readable medium of claim 1 , wherein the stages further comprise:
receiving a swipe gesture associated with the email on the GUI; and
displaying an action associated with the hero content as a result of the swipe.
5. The non-transitory, computer-readable medium of claim 1 , wherein the action button causes an action to be carried out by an application other than the email application.
6. The non-transitory, computer-readable medium of claim 1 , wherein the stages further comprise:
receiving selection of a second email within the GUI of the email application;
requesting additional hero content related to the second email; and
displaying a second hero card in place of the first hero card based on the selection.
7. The non-transitory, computer-readable medium of claim 1 , wherein displaying the first hero card includes determining at least one region to display from amongst at least a header region, an information region, and an action region, wherein the determination is based on the hero content received.
8. A system for providing hero cards, the system comprising:
a non-transitory, computer-readable medium that contains instructions;
a processor that executes the instructions to perform stages including:
receiving an email within an email application of a user device, the email application being unassociated with a plurality of backend systems;
detecting trigger content within the email by a hero agent of the user device;
sending, by the hero agent, a service request for hero content to a hero server, the service request including the trigger content and authentication tokens associated with the user device to be used by the hero server to determine a subset of backend systems, from the plurality of backend systems, that relate to both the trigger content and at least one of the authentication tokens;
receiving the hero content related to the email before or concurrently with the email, wherein the hero content is not part of the email as originally sent;
displaying a first hero card within a graphical user interface (GUI) of the email application, wherein the first hero card includes the hero content and an action button for performing a function in the backend systems related to both the trigger content and at least one of the authentication tokens.
9. The system of claim 8 , the stages further comprising:
receiving selection of the email within the GUI of the email application; and
displaying the hero content as a result of the selection.
10. The system of claim 8 , wherein the stages further comprise:
defining a region for displaying hero cards within the GUI of the email application; and
cycling through multiple hero cards in the region, wherein a second hero card displayed in the region includes different hero content than the first hero card, the different hero content being related to a second email.
11. The system of claim 8 , wherein the stages further comprise:
receiving a swipe of the email on the GUI; and
displaying an action associated with the hero content as a result of the swipe.
12. The system of claim 8 , wherein the action button causes an action to be carried out by an application other than the email application.
13. The system of claim 8 , wherein the stages further comprise:
receiving selection of a second email within the GUI of the email application;
requesting additional hero content related to the second email; and
displaying a second hero card in place of the first hero card based on the selection.
14. The system of claim 8 , wherein displaying the first hero card includes determining which regions to display from amongst at least a header region, an information region, and an action region, wherein the determination is based on the hero content received.
15. A method for presenting backend content within an application using hero cards, comprising:
receiving an email within an email application of a user device, the email application being unassociated with a plurality of backend systems;
detecting trigger content within the email by a hero agent of the user device;
sending, by the hero agent, a service request for hero content to a hero server, the service request including the trigger content and authentication tokens to be used by the hero server to determine a subset of backend systems, from the plurality of backend systems, that relate to both the trigger content and at least one of the authentication tokens;
receiving the hero content prior to or concurrent with delivery of the email to the email application, wherein the hero content is not part of the email as originally sent;
displaying a first hero card within a graphical user interface (GUI) of the email application, wherein the first hero card includes the hero content and action button for performing a function in the backend systems related to both the trigger content and at least one of the authentication tokens.
16. The method of claim 15 , further comprising:
receiving selection of the email within the GUI of the email application; and
displaying the hero content as a result of the selection.
17. The method of claim 15 , further comprising:
defining a region for displaying hero cards within the GUI of the email application; and
cycling through multiple hero cards in the region, wherein a second hero card displayed in the region includes different hero content than the first hero card, the different hero content being related to a second email.
18. The method of claim 15 , further comprising:
receiving a swipe of the email on the GUI; and
displaying an action associated with the hero content as a result of the swipe.
19. The method of claim 15 , wherein the action button causes an action to be carried out by an application other than the email application.
20. The method of claim 15 , further comprising:
receiving selection of a second email within the GUI of the email application;
requesting additional hero content related to the second email; and
displaying a second hero card in place of the first hero card based on the selection.