APEX Training

Tuesday, 16 September 2014

XML Parsing Error: no element found Location: ...

I am just working on an application which is supposed to be exposed to public users. I created a simple ajax process there which gets a value of an application element and does something based on the value. While calling the on demand process I am getting this error while not authenticated:

XML Parsing Error: no element found Location: moz-nullprincipal:{6492ed13-2b81-4989-938c-7c19121f419a} Line Number 1, Column 1:



After searching for this error in combination with APEX I found my old thread from 2012 which basically wasn't answered:

https://community.oracle.com/thread/2444115?start=0&tstart=0

After investigating what is happening there I noticed that the on demand process I created is set to "must not be public user" in the authorization section. Obviously APEX does that by default for the on demand processes. Running the ajax call would not find the "element" which is the actual process.

Saturday, 13 September 2014

Mein APEX Vortrag bei Orbit in Bonn

Am 05.11.2014 halte ich einen Vortrag über Rapid Application Development bei Orbit in Bonn. Dabei wird auch noch mein Freund und Kollege Tobias Arnhold sein. Er wird über die Themen Plugins und Reporting sprechen. Anschließend zeigt Frank Weyher (der ebenso ein guter Kollege und Freund ist :)), wie man APEX mit Office integrieren kann.

Die Themen sind sicherlich interessant und eine Anmeldung lohnt sich sicherlich. Der Link zu der Veranstaltung finden Sie hier.

Wednesday, 10 September 2014

APEX - Default Branch on Submit

Yesterday I spent two hours on debugging one of my applications and searching for an answer. Of course, the problem was caused by myself. Here is what happened:

I copied a page and deleted the region including buttons and items using the Cascade to Delete Buttons option.



Then I created a form and had there a process on submit to upload files in my table. Everything was working fine except the fact that after the process the page would show up empty having the funny

wwv_flow.accept

message.



Looking at the page I couldn't see anything what would point to the actual problem. The process was there and it was running and the branch was there. Only after a while I looked into the branching and saw there that it was conditional - firing when the deleted button was pressed.



Then it came to my mind that this wasn't the first time I had this problem. I think this is a bug and it has to do with the file browse item. I expected the page to redirect after submit since this feature is there since 4.0. However, it didn't. This issue seems to be fixed in 5.0.

And one more thing to add: It does make sense to create conditional branches but it doesn't make sense to create unconditional ones. The feature of creating unconditional branches to the actual page, where the branch resides, should be removed completely.

You can see it in "action" here

Wednesday, 3 September 2014

APEX 5.0 New Features Schulung

Unsere nächste Schulung hat APEX 5.0 New Features im Fokus. Diese findet im Dezember am 08. und am 09. in Bensheim statt. Wenn Sie auf diesen Link klicken, können Sie die Details anschauen und sich ggf. anmelden. Dieses Thema is sehr spannend und viele neue Features bzw. Änderungen kommen auf uns zu. Wir denken, dass Dezember der richtige Zeitpunkt dafür ist, damit anzufangen.