ORMIT™-Open Java's Automated Migration from Oracle Forms to Angular or React changes everything!

How is key mapping managed in Oracle Forms?

In Oracle Forms, key mapping is controlled via the FRMWEB.res file. This file defines the key bindings for various functionalities, such as navigation, commit, and form interaction. Each functionality is mapped to a corresponding key or key combination.

For example:

• Next Field -> TAB
• Previous Field -> SHIFT + TAB
• Commit -> F10
• Previous Block -> CTRL + UP

How is key mapping handled in ORMIT™-OpenJava?

After migrating to ORMIT™-OpenJava, key mappings are defined in a file called key_mappings.mjs. This file serves a similar purpose as FRMWEB.res but is more structured and allows for better readability and customization. 

By default, ORMIT™-OpenJava maintains the same key mappings as Oracle Forms to ensure a seamless transition for end users. This eliminates the need for change management and allows users to continue using familiar key combinations. However, the key mappings are fully customizable and can be adapted to meet new requirements if needed.

How does Oracle Forms key mapping compare to ORMIT™-OpenJava’s?

While Oracle Forms relies on functionality equivalents, ORMIT™-OpenJava (OOJ) introduces a more direct mapping between triggers and keys. This provides better control and understanding of how specific actions are executed and how they relate to their corresponding trigger in the code.

Example of Key Mapping in OOJ

 

Functionality	Key Mapping: Oracle Forms (FRMWEB.res) same as ORMIT™-OpenJava	ORMIT™-OpenJava (Trigger)
Previous Block	CTRL + UP	triggers.key_prvblk
Next Field	TAB	triggers.key_nextfld
Previous Record	Up Arrow	triggers.key_up
Commit	F10	triggers.key_commit

 

 

 

 

 

 

What are the advantages of ORMIT™-OpenJava's key mapping approach?

• Improved Readability: The mappings explicitly define which triggers correspond to each key action.

• Better Customization: Developers can easily modify or extend key mappings in key_mappings.mjs.

• More Precise Control: Each functionality is mapped to a specific trigger, ensuring consistency across the application.

• Seamless User Experience: Default mappings match Oracle Forms, preventing disruption and reducing training efforts.

 

Can I customize key mappings in ORMIT™-OpenJava?

Yes! The key_mappings.mjs file is fully customizable, allowing developers to assign different keys to triggers as needed. This makes it easy to adapt the system to specific user preferences or enterprise standards.

 

How do I modify the key mappings in ORMIT™-OpenJava?

To change a key mapping, simply update the key_mappings.mjs file with the desired key-to-trigger associations.

Example (Screenshot):

After making changes, the application will automatically apply the new mappings upon the next startup.

 

Do I need to reconfigure key mappings manually after migration?

No, ORMIT™-OpenJava automatically generates a default key_mappings.mjs file during the migration process, preserving most of the commonly used key mappings from Oracle Forms. Since the default mappings remain the same as in Oracle Forms, no change management is required for end users. However, developers can review and adjust the mappings as needed.

 

Have more technical questions about ORMIT™-OpenJava? Contact RENAPS to schedule a deep dive session with our experts.