HR application / console-apex
console-apex
The APEX button composes a URL with a signed token (COMPOSE_URL), shows it and calls WEB.SHOW_DOCUMENT.
Three runs from a fresh database gave byte-identical diffs. Behaviour that looks odd in the migrated app but is the original's: faithful to the original and waivers. Files: scenario, golden record, target record, diff (JSON).
Scenario steps
Items are addressed by their Forms name (BLOCK.ITEM[row]), the same name in the
original and, through the mapping, in the migrated app.
| # | Step | Action | Checked on the original |
|---|---|---|---|
| 0 | Open form login | ||
| 1 | Type LOGIN.USERNAME = alice, LOGIN.PASSWORD = alice#123 | ||
| 2 | login | Click LOGIN.LOGIN | |
| 3 | apex | Click CONSOLE.APEX |
Screens, step by step
Left: the original Oracle Forms application, recorded on a virtual display. Right: the migrated application in headless Chromium. Screenshots are evidence only; the comparison works on the recorded values.
Step 0: open login
Step 1: type
Step 2: login
Step 3: apex
Golden record of the original
After each step: the focus, the displayed values that changed, the message line and any alert. The full record (every item of every step, windows, lists of values) is in the JSON file.
| # | Step | Action (by name) | Focus after | Displayed values that changed | Message line | Alert | Expect |
|---|---|---|---|---|---|---|---|
| 0 | Open form login | LOGIN.USERNAME[0] | |||||
| 1 | Type LOGIN.USERNAME = alice, LOGIN.PASSWORD = alice#123 | LOGIN.PASSWORD[0] | LOGIN.PASSWORD[0] = alice#123LOGIN.USERNAME[0] = alice | ||||
| 2 | login | Click LOGIN.LOGIN | CONSOLE.EMPLOYEES[0] | CONSOLE.USERNAME[0] = alice | |||
| 3 | apex | Click CONSOLE.APEX | FWindow/PushButton:OK | APEX URL: http://localhost:8080/ords/r/hr_dev/hr-app/home?request=APEX_AUTHENTICATION=JWT&x01=<any> | FRM-92022: cannot launch URL http://localhost:8080/ords/r/hr_dev/hr-app/home?request=APEX_AUTHENTICATION=JWT&x01=<any> with target _blank. full details: The BROWSE action is not supported on the current platform! |
Database effects
None: the scenario changes no row and draws no sequence value.
Classified diff against the migrated app
Diff: console-apex counts: match 39, tolerated 1, waived 3, defect 0, unmapped 0, harness 0 generated-id pairs (source -> target): none waivers: H1 [proposed] APEX links fail with FRM-92022 instead of opening the page: applied to 3 value(s) H2 [proposed] Department tab keeps the previous department number: applied to 0 value(s) [tolerated] ui.message rule=mask:apex-token x1 [waived] ui.alert rule=waiver:H1 (alert missing in the target) x1 step03.alert: source {"title": "Forms", "message": ["FRM-92022: cannot launch URL http:/... | target null [waived] ui.focus rule=waiver:H1 (expected dialog) x1 step03.focus: source 'FWindow/PushButton:OK' | target 'console.apex[0]' [waived] ui.windows rule=waiver:H1 x1 step03.windows: source [["CONSOLE", "HR APP"], ["alert", "Forms"]] | target [["CONSOLE", "HR APP"]]
Waivers
| Id | Waiver | Values | Reason |
|---|---|---|---|
| H1 | APEX links fail with FRM-92022 instead of opening the page | 3 | The APEX buttons (CONSOLE.APEX, BUTTONS.APEX_BUTTON, the EMPLOYEES.APEX row button) compose a signed APEX URL, show it on the message line and call WEB.SHOW_DOCUMENT(url, '_blank'). On the Forms 14.1.2 client this fails: Forms shows the alert "FRM-92022: cannot launch URL ... The BROWSE action is not supported on the current platform!" and the page never opens, so the source records an alert, alert focus and an extra window, and the user has to dismiss it. The target writes the same message and opens the URL in a new browser tab, which is what the code asks for. Replicating the failure would mean shipping a broken link. The message line (APEX URL with the token) is still compared. |