It's really mistery who is author of that article: "AI" or live man... Rest in peace Joel...

Hello, guys! Would You comment that mysterious part of code? // Something bad happened. error: function( In fact all application's SAVE_NOTE errors goes in section success: function( But what case will use error: function( ? I just guess that it's useless part of code... BTW global error handling function doesnt catch pl-sql exceptions from ajax calls ((

Great and really sorry that doesn't work for lists, menu, breadcrumbs... I mean that APP_COMPONENT_NAME is empty for that.

Appreciate for sharing Your experience! Would You comment "Configuration 3"with using key security.verifySSL = false for terminating htts on proxy (balancer) for further accessing ORDS via http? I mean is this robust too?

Appreciate for Your clear and close to scientific structured article. Just a thoughts concerning decision... Business end users don't care about developer's hard choice 8) They just need IT to work always and forever. So REST remote source must be as robust as local DB tables...

Appreciate for Your answer. Would You clarify, have You checked page with Your dynamic example in APEX Advisor? On my APEX 22.2.0 even code exactly from APEX Help fails in that warning. Yes, code works, but Advisor says "Code Category Error Message Compilation error - ORA-06550" etc.

Jon, i do appreciate for clear view on that great APEX 222 feature! But would You clarify APEX Advisor of that? I mean that Advisor don't like any new Dynamic region... Region Source (Identifies the source of the region, reference Region Source Type) Check Is Valid SQL or PL/SQL Code Category Error Message Compilation error - ORA-06550: line 33, column 3: PLS-00372: In a procedure, RETURN statement cannot contain an expression

Here You are two cents. We can also change (add) /opt/tomcat/webapps/ords/defaults.xml <entry key="error.externalPath">/opt/tomcat/webapps/ords/errorpages/</entry>