A A year ago I have shared a tip how to use the same mechanism for closing modal dialogs . Today, I would like to share few more tips about levaraging the Global page. When you have a button on page and the action behind is a bit slow or if you have users who are constantly double clicking on everything, you might want to disable clicked button. You can easily fix this with a simple dynamic action. But instead of repeating this DA on each button, you can define it on the Global page. The trick is to use the jQuery selector and CSS class on each of these buttons. So go to your Global page. Create DA called SUBMIT_AND_DISABLE_BUTTON on Click event. Set Selection Type to jQuery Selector Set value to "button.SUBMIT_DISABLE" Switch the default true action to Execute JavaScript code Define the action code: var button_id = this.triggeringElement.getAttribute('id'); console.log('SUBMIT_AND_DISABLE_BUTTON:', button_id, this); docum...
T Today, I will show you how to easily check if your authorization schemes set on pages match the schemes set in the navigation. In my custom navigation (including the multicolumn navigation ), I don't have to set it in two places (which is never a good idea). My navigation gets the schemes from the pages. But the default APEX navigation is not like that. That causes a lot of confusion to users when they see a page in navigation, but can't access it. Or when they have some hidden pages, and they are missing the navigation links. Fortunately, if you combine few APEX views, you can find out: SELECT p.application_id, e.list_name, p.page_id, p.page_name, --p.page_alias, --p.page_group, --p.page_mode, p.authorization_scheme AS auth_scheme_page, e.authorization_scheme AS auth_scheme_nav, e.entry_text, e.entry_target -- FROM apex_application_pages p LEFT JOIN apex_application_lists l ON l.application_id = p.application_...