Idea Summary
Enhance Popup LOV "Manual Entry" with Declarative Resolution on Lost Focus
(Oracle Forms-like Experience)
Use Case
High-Speed Keyboard Data Entry in Financial & ERP Systems
In professional accounting and ERP applications (especially those migrating from Oracle Forms), speed is the top priority. Accountants memorize "Account Codes" (Return Values) and expect a "Keyboard-only" workflow.
The Problem: Currently, the Popup LOV forces users to break their flow. They must either use the mouse to open a modal search window or enable "Manual Entry." However, with "Manual Entry" enabled, typing a code like 181 (the Return Value) and pressing Tab (Lost Focus) does not visually resolve the name (the Display Value). The user gets no visual confirmation, and the developer is currently forced to write redundant Dynamic Actions for every single item to fetch the Display Value manually.
Preferred Solution (Optional)
Implement a Declarative "Resolve on Lost Focus" Property:
We propose enhancing the Popup LOV by adding a built-in setting that mimics the Post-Text-Item trigger logic from Oracle Forms:
Auto-Mapping (On Blur): When a user types a value manually and leaves the field (Lost Focus / Blur), the component should automatically perform a background lookup against the Return Value of the associated Shared Component LOV.
Instant Visual Confirmation: If a single match is found, the UI should immediately update to show the Display Value (e.g., "181 - Main Bank Account") while maintaining the Return Value (181) in the session state.
Smart Fallback: If the entered value is not found, the system should either show a validation error or automatically open the Popup search dialog for the user to pick the correct record.
Business Value:
This feature eliminates the need for modal windows and removes the burden of manual coding (Workarounds) from the developer. It provides the high-efficiency, reliable data entry experience required for complex financial systems, making APEX the ideal destination for Oracle Forms migrations