RFGen Screen Mapping

1. RFGen Screen Mapping

2. One Product - Many Solutions: Screen Mapping Screen Mapping • Work with any vt100, 3270 or 5250 host screen • Create applications that run on all barcode terminals • Enhance customer applications without changing anything on their host system

3. RFGen Screen Mapping • All applications are hardware independent • All telnet capable terminals supported • All Windows based terminals supported • All ODBC databases supported • 3270/5250 transaction mapping supported • Double-byte languages supported

4. RFGen Screen Mapping RFgen Isn’t Just For ODBC Anymore

5. RFgen Sales Strategy Solution Oriented Selling • Differentiate offering from other vendors • Provide a “single source” solution • Let customers “try before they buy” • Listen and respond quickly to customer needs • Focus on and Sell the right solution

6. RFGen Screen Mapping

7. RFGen Screen Mapping

8. Making The Connection In Programmers Assistant, click on ‘Configure’. Select ‘Add New Screen Mapping Connection. The ‘Configure Screen Mapping Connection’ dialog box appears… This is where you specify the host connection information, enter the downtime schedule for this host, and choose settings for the other system defaults…

9. Advantages of Screen Mapping

10. Displaying the Environment To bring up the emulation window, simply “double-click” on the Host icon in the RFGen status bar, and the selected session window will appear. Double Click - Screen Mapping Session Window appears

11. Using the Environment RFGen uses a standard “point-and-click” interface to allows users to interact with the host session as well as the built-in Screen Mapping features… Session – This allows the user to control various elements of the session. Hot Keys – This allows the user to send IBM specific keys to the host system. Macros – This allows access to the RFGen Screen Mapping system.

12. The Pop-Up Window RFGen also includes pop-up window to simplify the macro recording process. From this window, users can quickly insert timing and other commands into the script they are recording. To access this pop-up, just right-click on the screen.

13. Three Levels of Integration RFGen provides three levels of integration capability for the user. They are as follows… Basic Also known as “Traditional Screen Mapping”, the user has complete control over the host session. All interaction is written and maintained by the user. Simplified This method takes a “System” approach to Screen Mapping by providing built-in capabilities to navigate host menus and update host screens. Embedded This method builds upon Simplified Screen Mapping by embedding fields directly into RFGen forms.

14. VBA Language Extensions • To support the “Basic” Screen Mapping model, RFGen provides a number of VBA Language extensions. • Users Benefit from these extensions in the following ways… • Optimized for Specific Tasks • Coding and Operational Efficiency • Fully Documented with Examples • Guaranteed Backwards Compatibility

15. Connection Availability Before attempting to send a series of commands to a Screen Mapping connection, it might be prudent to determine if the host is available. RFGen provides the following command to test the state of the connection to a host system… ConnAvailable This command returns ‘True’ if the host connection is available. Example: If Not ConnAvailable(“CICS”) Then vRsp = RFMsgBox(“Host is off-line, proceed with batch?”, vbYesNo) . . End If

16. Session Startup and Shutdown RFGen Screen Mapping is designed to simplify the entire process of interacting with Legacy Host systems. Accordingly, RFGen allows users to specify initial startup and shutdown macros to login and logout of the host system properly. While these macros are called automatically at session startup and shutdown, users can execute these macros whenever they require…

17. Multiple Host Support RFGen Screen Mapping allows users to connect to multiple host systems. At system startup, RFGen will select the first defined host system to be the default host. All Screen Mapping commands will then be directed to that host.

18. Transaction Bracketing Transaction Bracketing is used with Pooled Screen Mapping Connections. It allows users to do the following… • Retrieve a specific connection to the host system. • Execute a series of commands against a specific session. • Return the connection to the pool when they’re finished. Note: Transaction Bracketing is performed automatically when you use the RFGen Macro commands.

19. Host Screen Navigation RFGen Host Screen Navigation is used to simplify the process of moving between different host applications. RFGen Host Screen Navigation allows users to do the following… • Easily move from screen to screen in the host system. • Recover from failed navigation or system input errors. • Significantly reduce the complexity of Screen Mapping.

20. Host Screen Navigation RFGen introduces the concept of a base screen or “main menu”. The base screen is used as a point-of-reference when moving between different host applications. The methodology is as follows… • A “main menu” is linked to a specific RFGen host session. • Application Screens are then linked to this “main menu”. • Screen requests that are linked to this “main menu” will be automatically routed to this session.

21. Transaction Macros RFGen uses a concept called Transaction Mapping to interact with Legacy Host systems. Transaction Mapping works as follows… • The user identifies all important data fields and screen regions. • The user enters a sample transaction which is recorded and converted into a series of VBA commands. • The user can then call the macro, passing it the variable data fields and have the transaction update on the host system. • Optionally, the user can “paint” a RFGen form and have it execute directly against the macro once all input fields have been accessed. Any returning data will then be displayed in the appropriate linked fields. Note: Unlike “Screen Scraping” solutions, RFGen transactions can be used while the host is off-line. These transactions can also comprise multiple host systems or even access ODBC databases.

22. Main Menu Steps Defined To create a “main menu”, simply follow these 5 easy steps… • Logon to Main Menu – This records all the keystrokes necessary to log onto the main menu. • Identify the Main Menu – Select the areas of the screen that will uniquely identify this as the main menu. • Return from Navigation Error – This records the keystrokes necessary to recover from an unexpected scripting error. • Logoff from the Main Menu – This records the keystrokes necessary to log off from the system. • Test Macros – This allows users to quickly test their macros.

23. The Application Screen “Application Screens” are where the actual user input will normally take place. These screens are usually linked to macros to send and receive data from the host system. All “Application Screens” contain two basic functions… • Link to Main Menu • Go to Application Screen Script • Return to Main Menu Script

24. Application Screen Steps Defined To create an “Application Screen”, simply follow these 5 easy steps… • Go to the Application Screen – This records all the keystrokes necessary to move from the main menu to the application screen. • Identify the Application Screen – Select the areas of the screen that will uniquely identify this as the application screen (page 1). • Identify Multiple Screen Pages – Select the areas of the screen that will uniquely identify this as an additional page of the application screen. • Return to the Main Menu– This records the keystrokes necessary to move from the application screen back to the main menu. • Test Macros – This allows users to quickly test their macros.

25. The Data Entry Transaction “Transaction Macros” are where the actual data entry into the host system will take place. All “Transaction Macros” contain the following elements… • Link to Application Screen • Screen Input Fields • Screen Output Fields • Transaction Script

26. Data Entry Transaction Steps Defined To create an “Transaction Macro”, simply follow these 4 easy steps… • Go to the Linked Application Screen – This step tests the code required to navigate to the linked Application Screen. • Mark All Significant Data Fields – Select the input fields/areas of the screen that you are interested in sending data to/receiving data from. • Enter a Sample Transaction – This starts recording the keystrokes required to input this type of transaction. A fully editable VBA script will then be created based upon the input captured. • Test Transaction – This allows users to quickly test their transaction macros.

27. Embedded Screen Mapping Embedded Screen Mapping builds on the ‘Simplified’ approach to create the user interface for the wireless device. Using these methods, Screen Mapping applications can be created based entirely on “point-and-click” techniques.

28. Summary • With the RFGen Screen Mapping Module, you can • Connect to “ANY” Legacy Host • Connect with “ANY” DOS or CE RF Device • Customize with Ease • Rapid Application Development • Use a Proven Product – Over 1,000 Installations • Double-Byte Compliant • WITHOUT MODIFYING THE HOST APPLICATION