Skip to Main Content
Feature Request FR-4892
Product Area Page Components
Status ROADMAP

13 Voters

Use Button-Style Edit Links by Default in Interactive Reports

parthiban Public · May 19 2026

Idea Summary

In Oracle APEX Interactive Reports, when creating a link to an edit form, the default link text is typically a small edit icon:

<span role="img" aria-label="Edit" class="fa fa-edit" title="Edit"></span>

While this icon is visually clean, it can be difficult for users to click because the clickable area is very small. This is especially challenging for users working on touch devices or for those who need larger targets for easier navigation.

I suggest that Oracle APEX automatically apply a button-style CSS class to edit form links when a new Interactive Report link is created. This would make the edit action more visible and provide a larger clickable area by default.

For example, the link could use Universal Theme button classes such as:

  • t-Button t-Button--icon t-Button--small t-Button--simple

This would display the edit icon as a proper button, improving usability while still allowing developers to customize or remove the styling as needed.

Use Case

  • Interactive Reports with edit form links
  • ERP and enterprise applications with frequent record updates
  • Touch-screen and mobile users
  • Improved accessibility and user experience
  • Reduced misclicks and easier navigation

Preferred Solution (Optional)

When a developer creates a form link from an Interactive Report, Oracle APEX could automatically populate the Link Attributes property with a default button style, such as:

class="t-Button t-Button--icon t-Button--small t-Button--simple"

Developers would still have full control to modify or remove the default classes based on their application's design requirements.

This enhancement would provide a more user-friendly default experience and make edit actions easier to identify and click.

 

This is currently on the roadmap for a future release of Oracle APEX.

Comments

Comments

  • karthisachin50 OP 2 months ago

    Useful

  • gokul b OP 2 months ago

    This will be more effective to the end users.

  • abishek OP 2 months ago

    This is a useful feature. Using button-style edit links in Interactive Reports improves usability, accessibility, and user experience by providing a larger clickable area compared to the default small edit icon.

  • lakshmi mathiyalagan OP 2 months ago

    This enhancement More visible and easier to click in Interactive Reports.

  • sathya jayasri s OP 2 months ago

    Useful feature. This will improve usability and make edit actions easier to click for users.

  • sakfresa08 OP 2 months ago

    Good feature request. Larger clickable edit buttons will help both desktop and mobile users.

  • karthikeyanshan27 OP 2 months ago

    Very useful enhancement. Button-style edit links would improve usability, accessibility, and mobile friendliness in Interactive Reports while still keeping full developer flexibility. Fully support this idea.

  • badhvaryu OP 2 months ago

    Really useful and good enhancement for end user perspective.

  • vinodhkannanb OP 8 weeks ago

    This is a great suggestion and will be quite handy for the end users. I strongly recommend Oracle team to consider this idea

  • fac586 OP 8 weeks ago

    Firstly, in the absence of the ability to configure defaults for all components, I wouldn't want to see novel and unsystematic customisation of wizard-generated components, as in many instances the developer will have to undo them immediately for compatibility reasons. The 24.2 changes to generated classic report template options are a case in point: the resulting appearance is not that historically used by most organisations.

    Secondly, the introduction in 26.1 of the Actions theme component and row-level  Dynamic Actions will result in much less use of the built-in IRR column, as Actions columns enable exactly this kind of link button to be created declaratively, with the  ability to present all other row-level operations as additional buttons or menu options in one column.

    If I was trying to make IRR links a better target, then I would use custom theme roller CSS so that it was consistently applied to all IRRs by code specified in one place.