19. A system, comprising: a memory, a processor in communication with the memory, the processor configured to execute instructions for a method comprising: parsing an application program document at a front-end computer into a plurality of tokens; searching a database on a back-end server to determine if the tokens match data objects stored in the back-end server; if there is a match between a token and a matching data object in the back-end server, creating and storing in a buffer at the front-end computer a context link associating the token to the matching data object in the back-end server, wherein determining the match and creating the context link comprise: if there is one hit for a token to match one data object type in the back-end server, creating and storing in the buffer at the front-end computer the context link associating the token to a single hit data object of the matching data object type in the back-end server; if there are multiple hits for a token to match one data object type in the back-end server: storing the token in a wait list for the matched data object type, the token being stored according to an order in which it is found in the application program document; determining if there are other tokens in the wait list for the matched data object type; combining the token with a preceding token in the waiting list to form a phrase; determining whether the phrase is related to a single data object on the back-end server; and upon determining the phrase is related to a single data object on the back-end server, creating and storing in the buffer at the front-end computer the context link associating the phrase to the single data object; responsive to the context link being selected, displaying in a menu structure with a list of actions including menu entries for each data object type and a relations entry for other data objects related to the matching data object; retrieving from the back-end server a dynamic list of linkable data object types for other data objects that are related to the matching data object; responsive to a selection of the relations entry, displaying a submenu with the list of linkable data object types for the data object; responsive to a selection of one linkable data object type from the dynamic list, displaying a next level of the submenu with a list of data objects of the selected linkable data object type associated with the matching data object; responsive to a selection of a data object from the list of data objects of the selected linkable data object type, displaying another level of the submenu with another list of actions associated with the selected data object; and responsive to a selection of one of the listed actions in the application program on the front-end computer, sending a request to a back-end server to perform the selected action on a data object that is related to the selected context link.
19. A system, comprising: a memory, a processor in communication with the memory, the processor configured to execute instructions for a method comprising: parsing an application program document at a front-end computer into a plurality of tokens; searching a database on a back-end server to determine if the tokens match data objects stored in the back-end server; if there is a match between a token and a matching data object in the back-end server, creating and storing in a buffer at the front-end computer a context link associating the token to the matching data object in the back-end server, wherein determining the match and creating the context link comprise: if there is one hit for a token to match one data object type in the back-end server, creating and storing in the buffer at the front-end computer the context link associating the token to a single hit data object of the matching data object type in the back-end server; if there are multiple hits for a token to match one data object type in the back-end server: storing the token in a wait list for the matched data object type, the token being stored according to an order in which it is found in the application program document; determining if there are other tokens in the wait list for the matched data object type; combining the token with a preceding token in the waiting list to form a phrase; determining whether the phrase is related to a single data object on the back-end server; and upon determining the phrase is related to a single data object on the back-end server, creating and storing in the buffer at the front-end computer the context link associating the phrase to the single data object; responsive to the context link being selected, displaying in a menu structure with a list of actions including menu entries for each data object type and a relations entry for other data objects related to the matching data object; retrieving from the back-end server a dynamic list of linkable data object types for other data objects that are related to the matching data object; responsive to a selection of the relations entry, displaying a submenu with the list of linkable data object types for the data object; responsive to a selection of one linkable data object type from the dynamic list, displaying a next level of the submenu with a list of data objects of the selected linkable data object type associated with the matching data object; responsive to a selection of a data object from the list of data objects of the selected linkable data object type, displaying another level of the submenu with another list of actions associated with the selected data object; and responsive to a selection of one of the listed actions in the application program on the front-end computer, sending a request to a back-end server to perform the selected action on a data object that is related to the selected context link. 22. The system of claim 19 , wherein the searching comprises: searching a buffer in the front-end computer for the token; and if the token was not found in the buffer, requesting that the back-end server search for the token, wherein the search identifies a match between the token and a data object in the back-end server if the token was found in the buffer or in the back-end server.