Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

BUG : APEX 24.x : Working Copy merge of Global Page DA corrupts button positions on other pages

fac5863 days ago — edited 3 days ago

Originally discovered on premises in APEX 24.1

Reproduced in APEX 24.2 on apex.oracle.com

Scenario

Application with 3 pages:

  • 0: Global Page
  • 1: Home
  • 2: Standard page
  1. The Global Page contains a Breadcrumb region in the Breadcrumb Bar slot.
  2. Page 2 contains two buttons positioned in the global Breadcrumb region, one in the Close slot, and one in the Create slot.
  3. A working copy is created.
  4. A dynamic action is added to the Global Page, containing a single Execute JS Code step.
  5. The global page DA change is merged into the main app from the working copy.

Issue

Following the merge, the buttons on page 2 previously positioned in the global Breadcrumb region are assigned to an Invalid Slot [Not Rendered] node in the rendering tree, with their individual slots appearing as CLOSE (invalid) and CREATE (invalid) respectively.

Demo

Example on apex.oracle.com

  • Main app ID: 220872
  • Working copy ID: 224935

Comments

Post Details

Added 3 days ago
0 comments
28 views