Issues with Java Checkbox (Oracle Forms)

Help Activities
, , ,
1

image
image695×722 111 KB

Hello everyone,

I’m having trouble finding a “bulletproof” way to interact with a checkbox in a legacy Java application (Oracle Forms).

The problem:
A regular click (modern and classic) sometimes appears to work visually, but the back-end action is not triggered correctly.

Click simulation is not supported for these elements.

Using Type Into (sending a space) to trigger the checkbox also fails to provide consistent results.

The automation works on the first iteration, but fails on subsequent operations (even after restarting the application to avoid screen freezes).

What I’ve tried so far:

Modern and classic click activities (default, window messages).

Type Into sending " " (space) to trigger the state.

Using the Get property to check the current state (checked/selected).

If condition to decide if activation is needed.

Using Activate before each interaction.

Despite these steps, the behavior is inconsistent. Sometimes the robot detects the ‘panel’ instead of the checkbox itself.

Environment:

UiPath Studio 2025.10 (Modern)

UIAutomation Packages: 25.10.28

Java extension installed.

Does anyone have experience with these types of Java checkboxes? Is there a specific feature I should monitor, or a specific input mode that works best to get them to work without a hitch.

Any advice would be appreciated!

2

Hello @Shoshana_Amrusi,

I’ve seen similar issues with Oracle Forms — often it’s not the click itself, but element identification.

  • First, ensure Java Extension/Bridge is properly loaded. UiPath confirms Oracle Forms works via Java extension, and selectors should contain <java ...> (not <ctrl role="client">).
  • If UI Explorer selects the whole window, Java is not hooked correctly.
  • Also, a common issue: overlapping forms. Sometimes UiPath picks elements from a form behind the active one, so the click looks like it worked, but the backend doesn’t trigger.

What helped:

  • Move the active Oracle form aside
  • Ensure no other form is behind it
  • Re-indicate the checkbox

This is usually an Oracle Forms + Java identification issue, not a click method issue.

Thanks,
Karthik

3

image

Hi Karthik,
Thanks for the insights! However, the problem is not with the element recognition. As you can see in the selector I attached, the Java extension works perfectly and recognizes the checkbox correctly.

The real problem
On the first iteration, the robot clicks the checkbox, the “V” appears, and the system correctly switches from the default (“End of subscription”) to “Pension coverage”.

On subsequent iterations, the robot clicks the checkbox and the “V” appears visually, but the backend system does not register the change. It remains stuck on the default “End of subscription” as if no click occurred.

It seems that the click is “visual only” and does not trigger the internal Java event/listener required to change the document type.

I have already tried:

Modern and classic clicks (default and window messages).

Typing in [space] after activating the element.

Restarting the application between runs (this still only works for the first record).

Why would it only work for the first record and then only do a “visual” click for the rest? Could this be a targeting issue or something specific to how Oracle Forms handles state changes?

4

Use hardware clicks. Make sure the control is visible and on top. Other input methods are unstable as described above when automating Java forms / applets.

5

Hello @Shoshana_Amrusi,

did you tried check/uncheck activity instead of click activity?

Thanks,
Karthik

6

These use simulate-like technology. It will have the same negative effect.
I built many bots on java apps. Using hardware all the way through is the only stable option.

7

I tried this but same result

9

I emphasize that this is only a problem with ANNETENDEDD running from Orchestrator, the studio run works fine.

10

Hello @Shoshana_Amrusi,

This gives more clarity on the issue. On your unattended machine, the Java bridge is likely not installed.
Install Java bridge using CLI when studio is not installed.
Please refer to: Java Extension for Unattended Robot ( No Uipath Studio )

Thanks,
Karthik