T Third time the charm. I love this conference, love the atmosphere, love the people. This year I have really enjoyed the networking and made few new friends. Sadly, Peter's minions were not present again, and this time nor was Peter. The APEX team was a bit more secretive than usual, but it here are some statements: APEX 24.1 will be a bit late (no news) It might and it might not bring us the 5 features promised on last Kscope (you could actually made and deliver a baby during this waiting) Oracle has build 41 thousands of bespoke internal APEX applications Cloud starting prices for APEX service were dramatically reduced And I have done it. I finally stepped up and presented something on a conference for the first time, in front of a real audience with 70+ people. And that something was a bit controversial topic. Huge thanks to the people supporting me, also huge thanks to all guys who made this conference happen. I have enjoyed it more than ever befor
O One of my colleagues (lets name him Max) prepared a surprise for me. I had no idea where is the JavaScript code being placed on page. Turned out, there is an API for injecting JavaScript code from PL/SQL and you can do the same with CSS. That is not just an excellent hiding place, but it can be used if you need to attach these on page dynamically. Checkout the APEX_JAVASCRIPT api, especially the ADD_ONLOAD_CODE procedure. For example you can set the JavaScript variable from the PL/SQL. BEGIN APEX_JAVASCRIPT.ADD_ONLOAD_CODE ( p_code => 'variable_name = new_value;' ); END; / Better version would be to escape the value using ADD_VALUE (which is an equivalent of APEX_EXEC.ENQUOTE_LITERAL but for JavaScript) or APEX_JAVASCRIPT.ESCAPE function: BEGIN APEX_JAVASCRIPT.ADD_ONLOAD_CODE ( p_code => 'variable_name = ' || APEX_JAVASCRIPT.ADD_VALUE('new_value', p_add_comma => FALSE) || ';' ); END; /