Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 234 Big Data Appliance
- 1.9K Data Science
- 449.7K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 157 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 387 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
APEX 5.1.1 Bug When Creating Mobile User Interface to Existing Desktop Application

Hi,
Here are the steps to replicate this in https://apex.oracle.com:
1. Create a new Desktop Application, accept all the defaults and "Create Application".
2. Create a Global Page, Page Number 0 (default).
3. Go to Shared Components >> User Interface Attributes >> Add User Interface.
4. Type: Mobile, leave everything else is as default, and "Create".
Two things happen:
1. The "Footer" region for Mobile was created in the Desktop Global Page (and shows as Invalid Position).
2. The default buttons "MENU" and "LOGOUT" are not created under the "Header" region in the Mobile Global Page (999 by default). However, running the Advisor at the application level (not from the page), there are two warnings related to "Inconsistent references between Dynamic Actions and Buttons":
a. Button (MENU) has an 'Action' of 'Defined by Dynamic Action', but there is no corresponding Dynamic Action referencing this button.
b. Button 'Action' is not 'Defined by Dynamic Action', for a button referenced in a Dynamic Action (open panel).
Thank you,
Erick