Idea Summary
For some reason, Interactive Reports in version 26 do not seem to have the “Go” button. This button is simply refreshing the region, by submitting any search or other modification, a user has already created while using the page. The button is part of what we describe as “Usability”, and thus it is in very bad taste to simply remove it from the face of the universe, even if the APEX team thinks the new features in the Search item are so neat.
I am well aware that hitting “Search” and pressing “Enter” does the same thing, but with all the extra features now visible inside “Search”, users prefer to refresh without using all the features, miss the button.
I am well aware that refreshing the entire page (F5) is possible, but com'on! Specially if there is some message - who wants to do that???
Use Case
A. One user is looking at a report, while guiding another user to make some changes. Then, the report user wants to see the changes - without entering new search criteria.
B. Users activate certain things and wait for results in a report. A scheduler job might take a while to update everything, so the users use the button every few seconds, so they can follow up on the refreshed data.
C. User is a keen developer, and learns that the “Create an application in 5 minutes” option is gone, if we have to start adding JS to add a “Go” button, because it was there, and not it's gone.
D. A person such as myself actually reads your documentation. It says specifically: “The Actions menu appears to the right of the Go button on the Search bar in an interactive report” - don't believe me? Look https://docs.oracle.com/en/database/oracle/apex/26.2/htmdb/customizing-the-interactive-report-actions-menu.html (I'm not sending this as a SR, as Support will just correct the documentation and ask me if the problem is solved!)
E. User is a keen developer, and fears the next elements to be removed in the next edition.
Preferred Solution (Optional)
A. Do NOT remove elements, that developers and users have grown accustomed to.
B. Let us, as a minimum, have a check box in which we declare whether we want the button or not - similar to the “Display Reset Button Automatically” component setting - preferably with per-page override.
C. Mention this in the What's changed documentation !