Skip to Main Content
Feature Request FR-2063
Product Area Developer Experience
Status ROADMAP

38 Voters

Support run page for modal dialogs

gabriel.diaz.arias Public · Oct 13 2021

Idea Summary
When you want to run a modal dialog from the page designer, it doesn't allow you to do so. I understand that you need a parent page for modal dialogs, but when you are just debugging or designing the page components, is quite frustrating having to open the app and navigate to that modal dialog.

Use Case
Avoid unnecessary clicks for running modal dialogs, better development experience.

Preferred Solution (Optional)
When you run a modal dialog page, it could load over a blank temporary page with the standard theme page template instead of not allowing it.

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

Known Duplicates

Known duplicates

FR-2529
FR-2529 Add a "Run Application" button to the Page Designer.
FR-2619
FR-2619 Redirect to Current Page when clicking Play button on page 0
FR-3612
FR-3612 A way to run drawer or dialog pages directly from Page Designer
FR-3614
FR-3614 A way to launch the application from within Page Builder

Comments

Comments

  • fac586 OP 3.6 years ago

    This has been a long term irritation to me as well. The issue also applies to running apps from their global page.

    When you run a modal dialog page, it could load over a blank temporary page with the standard theme page template instead of not allowing it.

    The problem there is that modal dialog pages are normally dependent on session state values that won't exist when the page is run directly from Page Designer. What if the page is step 3 in a 5 stage wizard?

    I can see three potential implementations of such a feature:

    1. Enable developers to set the runtime context for the modal page: Clicking the run button on a modal page opens a dialog with a list of the modal page items so you can set them with suitable values, and an extendable list of name/value pairs enabling session state values from other pages and application items to be entered. These values would be retained in the Application Builder and used as the launch page defaults until changed.
    2. Enable developers to select which page to launch: Clicking the run button on a modal or global page opens a dialog where the developer can select or enter a standard page to start from. This value is retained in the Application Builder and used as the default until it is changed.
    3. Run the application home page: Clicking the run button on modal or global pages runs the application from the default home page.

    Option 1 would be required to make effective use of your preferred solution. This is very complicated for Oracle to develop, and requires a lot of effort from the developer to set the required application context, which doesn't enhance productivity. Admittedly, once done it would provide a good baseline for iterative development of the modal page.

    Personally I would be delighted with option 2, and happy just to get option 3 in the short term.

  • mark stewart OP 3 years ago

    To suggest another approach to the comments by fac586, would APEX be able to figure out what the possible parent is for the modal page, and display that? If more than one “parent” allow the developer to pick which page?  Similar for a wizard page, go to the parent of the first modal page of the wizard?

  • oliver.lemm OP 2.7 years ago

    Lets make it an easy solution. Just define the parent page when click run on the modal page. Afterwards run always this parent page

    Optional you can click the wrench to change parent page.

  • phillip.grimshaw OP 1.4 years ago

    having item overrides would allow us to define what we are passing in and hence would allow us to run from the developer window.