Dynamic extensions to legacy application tasks
First Claim
1. A method in a computing system for modernizing a menu-based legacy application comprising:
- causing a task associated with the menu-based legacy application to be executed without invoking any menus of the legacy application;
wherein the executing task corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and is executed on a host computing system, the executing task accessed through a communication session between the computing system and the host computing system;
receiving screen output from the executing task associated with the menu-based legacy applicationdetermining whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing task; and
when determined that the criterion has been satisfied, displaying, along with the received screen output, a user interface control configured to cause the non-legacy code to be executed when the user interface control is selected.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods, systems, and techniques for adding extensions to legacy tasks as part of modernizing such tasks are provided. A user can add dynamically add task extensions to an individual legacy task by configuring them, even while a task is running. Role extensions can be added to a home desktop of a role through configuration parameters. Task extensions can be made accessible to users through UI controls added as part of the modernization procedure when a legacy task data stream is received from a host computing system. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.
-
Citations
24 Claims
-
1. A method in a computing system for modernizing a menu-based legacy application comprising:
-
causing a task associated with the menu-based legacy application to be executed without invoking any menus of the legacy application;
wherein the executing task corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and is executed on a host computing system, the executing task accessed through a communication session between the computing system and the host computing system;receiving screen output from the executing task associated with the menu-based legacy application determining whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing task; and when determined that the criterion has been satisfied, displaying, along with the received screen output, a user interface control configured to cause the non-legacy code to be executed when the user interface control is selected. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A computer-readable medium containing instructions that enable a computing system to modernize an existing menu-based legacy application, by performing a method comprising:
-
causing a task associated with the menu-based legacy application to be executed without invoking any menus of the legacy application;
wherein the executing task corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and is executed on a host computing system, the executing task accessed through a communication session between the computing system and the host computing system;receiving screen output from the executing task associated with the menu-based legacy application; determining whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing task; and when determined that the criterion has been satisfied, displaying, along with the received screen output, a user interface control configured to cause the non-legacy code to be executed when the user interface control is selected. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
15. A computing system comprising:
-
a memory; and a module that is stored on the memory and that is configured, when executed, to; cause a task associated with a menu-based legacy application to be executed without invoking any menus of the legacy application;
wherein the executing task corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and is executed on a host computing system, the executing task accessed through a communication session between the computing system and the host computing system;receive screen output from the executing task associated with the menu-based legacy application; determine whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing task; and when determined that the criterion has been satisfied, display, along with the received screen output, a user interface control configured to cause the non-legacy code to be executed when the user interface control is selected. - View Dependent Claims (16, 17, 18, 19)
-
-
20. A computer-readable medium whose contents enable a computing system to modernize an existing menu-based legacy application, by performing a method comprising:
-
receiving indication of a non-legacy code module; receiving an indication of one or more conditions for displaying access to the non-legacy code module, the conditions associated with data from a data stream received from an executing legacy task of a menu-based legacy application, wherein the executing legacy task is executed without invoking any menus of the menu-based legacy application and corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and wherein the executing legacy task is executed on a host computing system and accessed through a communication session between the computing system and the host computing system; and causing an interface to the non-legacy code module to be provided as a supplement to an interface to the executing legacy task when the indicated one or more conditions are met, such that, when the interface to the non-legacy code module is invoked, the indicated non-legacy code module is executed. - View Dependent Claims (21, 22, 23, 24)
-
Specification