Integrating applications in a portal

Abstract

Disclosed are various embodiments for integrating applications in a portal. An object type is identified in a user interface that is received from a first application. An action associated with the object type that can be performed by a second application and/or a view associated with the object type that can be provided by a third application is determined based in part on an account configuration of the first application. The user interface can be modified to include a component for selecting the action and a component for selecting the view.

Therefore, the following is claimed: 
     
         1 . A system, comprising:
 at least one computing device;   a first application executable in the at least one computing device, wherein, when executed, the first application causes the at least one computing device to at least generate a user interface including an object type;   a second application executable in the at least one computing device, wherein, when executed, the second application causes the at least one computing device to at least perform an action associated with the object type; and   a portal executable in the at least one computing device, wherein, when executed, the portal causes the at least one computing device to at least modify the user interface received from the first application to include a component for selecting the action associated with the object type.   
     
     
         2 . The system of  claim 1 , wherein, when executed, the portal further causes the at least one computing device to at least identify the object type in the user interface based at least in part on at least one of a markup code included in the user interface or a format rule. 
     
     
         3 . The system of  claim 1 , wherein, when executed, the portal further causes the at least one computing device to at least determine the action associated with the object type based at least in part on account configuration of the first application. 
     
     
         4 . The system of  claim 3 , wherein, when executed, the portal further causes the at least one computing device to receive the account configuration from the first application. 
     
     
         5 . The system of  claim 3 , wherein, when executed, the portal further causes the at least one computing device to receive the account configuration from a cache over a network. 
     
     
         6 . The system of  claim 1 , further comprising, a third application executable in the at least one computing device, wherein, when executed, the third application causes the at least one computing device to at least provide a view associated with the object type. 
     
     
         7 . The system of  claim 6 , wherein the component comprises a first component, and when executed, the portal further comprises the at least one computing device to at least modify the user interface to include a second component for selecting the view associated with the object type. 
     
     
         8 . A non-transitory computer-readable medium embodying a program executable in a computing device, wherein, when executed, the program causes the computing device to at least:
 identify an object type included in a user interface received from a first application; and   modify the user interface to include a first component configured to select a view associated with the object type and a second component for selecting an action associated with the object type, the view being provided by a second application, and the action being performed by a third application.   
     
     
         9 . The non-transitory computer-readable medium of  claim 8 , wherein, when executed, the program further causes the computing device to at least determine the action and the view based at least in part on an account configuration of the first application. 
     
     
         10 . The non-transitory computer-readable medium of  claim 9 , wherein, when executed, the program causes the computing device to at least receiving the account configuration from the first application over a network. 
     
     
         11 . The non-transitory computer-readable medium of  claim 9 , wherein, when executed, the program causes the computing device to at least receiving the account configuration from a cache. 
     
     
         12 . The non-transitory computer-readable medium of  claim 11 , wherein the computing device is a client and the cache is local. 
     
     
         13 . The non-transitory computer-readable medium of  claim 8 , wherein identifying the object type is based at least in part on a markup code in the user interface. 
     
     
         14 . The non-transitory computer-readable medium of  claim 8 , wherein identifying the object type is based at least in part upon a format rule. 
     
     
         15 . A method, comprising:
 identifying, via at least one computing device, an object type included in a user interface received from a first application;   determining, via the at least one computing device, an action associated with the object type, the action performed by a second application; and   modifying, via the at least one computing device, the user interface to include a first component for selecting the action associated with the object type.   
     
     
         16 . The method of  claim 15 , wherein the action is a particular action of a plurality of actions, and determining the action further comprises selecting the action from the plurality of actions based at least in part on an account configuration of the first application. 
     
     
         17 . The method of  claim 16 , further comprising, obtaining, via the at least computing device, the account configuration from the first application. 
     
     
         18 . The method of  claim 15 , further comprising:
 determining, via the at least one computing device, a view associated with the object type, the view being associated with a third application; and   modifying the user interface to include a second component for selecting the view associated with the object type.   
     
     
         19 . The method of  claim 18 , wherein the first component and the second component are included in a menu of the user interface. 
     
     
         20 . The method of  claim 15 , wherein identifying the object type further comprises examining the user interface for a predefined markup that designates one or more instances of the object type.