Here is my case in APEX 24.2.2
I have 2 staffs working in the same APEX page. for example
-
staff A and staff B working in page101. so we create 2 working copies for each (let's say copyA and copyB)
-
A works on changes 1,2,3 in page 101 while B works on changes 4,5,6.
-
A completes the changes quickly and catched up the first publish milestone (let's say pub1).
-
while B only finishes 4,5, so the 4,5,6 are planed to publish in next milestone (let's say pub2).
-
we merge copyA into main to publish A's work in pub1. the page after pub1 will have the page with change 1,2,3.
-
after that B completes the 4,5,6. we will publish B's work in pub2. The expected result is that after pub2, the page will be with the change 1,2,3,4,5,6.
BUT
-
if we merge copyB into main directly after pub1. the change 1,2,3 in page101 are flushed (disappear）.
-
if we do the refresh to copyB after pub1, 4, 5 which are completed and saved before pub1 are flushed. we only get the change of 1,2,3,6 after pub2.
Does APEX have the timestamp to record the chage of working copy, so when refresh the working copy, it will compare timestamp to keep the change that we need (like 4,5 in example above).
@steve-muench-oracle