Dynamic extensions to legacy application tasks

• US 9,106,685 B2
• Filed: 10/28/2010
• Issued: 08/11/2015
• Est. Priority Date: 10/28/2009
• Status: Active Grant

• Current Assignee: ADVANCED BusinessLink Corporation
• Original Assignee: ADVANCED BusinessLink Corporation
• Inventors: Lategan, Christopher F.
• Primary Examiner(s): Bycer, Eric J
• Application Number:
  US12/914,843
• Publication Number:
  US 20110271231A1
• Time in Patent Office: 1,748 Days
• Field of Search: 715/810
• US Class Current: 1/1
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 3/04817 using icons graphical or visual programming using iconic symbols G06F8/34
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/04847 Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 8/51 Source to source
• CPC Class Codes: G06F 8/52 Binary to binary
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/66 of program code stored in read-only memory [ROM]
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/72 Code refactoring
• CPC Class Codes: G06F 8/74 Reverse engineering; Extracting design information from source code
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/448 Execution paradigms, e.g. implementations of programming paradigms
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/02 : Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 41/0803 : Configuration setting
• CPC Class Codes: H04L 41/0806 : for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 47/70 : Admission control; Resource allocation
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 63/104 : Grouping of entities
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/561 : Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]

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.

Claims

1. A method in a computing system for modernizing a menu-based legacy application having a plurality of executable legacy application tasks that are configured to be executable on a host computing system, comprising:

retrieving a plurality of roles, each role comprising a definition of one or more users authorized to use the role to access one or more assigned executable legacy application tasks;

using at least one of the roles to directly access and cause an assigned executable legacy application task to be executed without invoking the menus of the legacy application;

receiving screen output from an the executing legacy application task, wherein the executing legacy application 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 legacy application task accessed through a communication session between the computing system and the host computing system;

determining whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing legacy application 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.

2. The method of claim 1 wherein the criterion is an indication of a type of entity in the received screen output.

3. The method of claim 1 wherein the criterion is an indication of timing.

4. The method of claim 1 wherein the criterion is an indication of geographic location.

5. The method of claim 1, further comprising:

associating a call-back function with the user interface control so that when the user interface control is selected, the call-back function is executed to cause the non-legacy code to execute.

6. The method of claim 1 wherein the non-legacy code is configured to display additional output as an overlay on the displayed received screen output so that the additional output appears an integrated part of the displayed received screen output.

7. The method of claim 1, further comprising:

providing a configuration tool to configure the non-legacy code to be included in the executing legacy task screen output without terminating execution of the executing legacy task.

8. The method of claim 7 wherein the provided configuration tool may be used by an end user without administrator privileges.

9. A computer-readable medium containing instructions that enable a computing system to modernize an existing menu-based legacy application having a plurality of executable legacy application tasks that are configured to be executable on a host computing system, by performing a method comprising:

retrieving a plurality of roles, each role comprising a definition of one or more users authorized to use the role to access one or more assigned executable legacy application tasks;

using at least one of the roles to directly access and cause an assigned executable legacy application task to be executed without invoking the menus of the legacy application;

receiving screen output from the executing legacy application task, wherein the executing legacy application 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 legacy application task accessed through a communication session between the computing system and the host computing system;

determining whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing legacy application 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.

10. The computer-readable medium of claim 9 wherein the criterion is at least one of:

an indication of a type of entity in the received screen output, an indication of timing, or an indication of geographic location.

11. The computer-readable medium of claim 9, wherein the method further comprises:

associating a call-back function with the user interface control so that when the user interface control is selected, the call-back function is executed to cause the non-legacy code to execute.

12. The computer-readable medium of claim 9 wherein the non-legacy code is configured to display additional output as an overlay on the displayed received screen output so that the additional output appears an integrated part of the displayed received screen output.

13. The computer-readable medium of claim 9, wherein the method further comprises:

providing a configuration tool to configure the non-legacy code to be included in the executing legacy task screen output without terminating execution of the executing legacy task.

14. The computer-readable medium of claim 13 wherein the provided configuration tool may be used by an end user without administrator privileges.

15. A computing system comprising:

a memory; and

a module that is stored on the memory and that is configured, when executed, to;

retrieve a plurality of roles, each role comprising a definition of one or more users authorized to use the role to access one or more assigned executable legacy application tasks configured to be executable on a host computing system, the executable legacy application tasks part of a menu-based legacy application;

use at least one of the roles to directly access and cause an assigned executable legacy application task to be executed without invoking the menus of the menu-based legacy application;

receive screen output from the executing legacy application task, wherein the executing legacy application 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 legacy application task accessed through a communication session between the computing system and the host computing system;

determine whether a criterion has been satisfied that indicates a non-legacy code is available to supplement the executing legacy application 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.

16. The computing system of claim 15, wherein the criterion is at least one of an indication of a type of entity in the received screen output, an indication of timing, and/or an indication of geographic location.

17. The computing system of claim 15, wherein the module is further configured to associate a call-back function with the user interface control so that when the user interface control is selected, the call-back function is executed to cause the non-legacy code to execute.

18. The computing system of claim 15, wherein the non-legacy code is configured to display additional output as an overlay on the displayed received screen output so that the additional output appears an integrated part of the displayed received screen output.

19. The computing system of claim 15, wherein the module is further configured to provide a configuration tool to configure the non-legacy code to be included in the executing legacy task screen output without terminating execution of the executing legacy task.

20. A computer-readable medium whose contents enable a computing system to modernize an existing menu-based legacy application having a plurality of executable legacy application tasks that are configured to be executable on a host computing system, 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 the menu-based legacy application, wherein the executing legacy task corresponds to a code module accessible from a single menu or sub-menu item of the menu-based legacy application and executed on a host computing system, the executing legacy task accessed through a communication session between the computing system and the host computing system and invoked without invoking the menus of the menu-based legacy application; and

causing an interface to the non-legacy code module to be provided as a supplement to an interface to the 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.

21. The computer-readable medium of claim 20 wherein the non-legacy code module is a task extension for the legacy task executed on the host computing system.

22. The computer-readable medium of claim 20 wherein the non-legacy code module is a role extension for an associated role, the associated role enabling the non-legacy code module to be accessible to users that have proper authorization as defined by the associated role.

23. The computer-readable medium of claim 20 wherein receiving an indication of one or more conditions includes receiving an indication of a rule for determining when to provide access to the non-legacy code module.

24. The computer-readable medium of claim 23 wherein the rule is configured to identify objects that are present in the data stream received from the legacy application task and that may be enhanced with GUI information.