Snippets and Thoughts of One Oracle Developer

D Did you ever wanted to customize user messages? To make them intuitive? Green as success, red as error, yellow as warning? Oh yes, lets add a third message type. Not everything can fit into success or error. To achieve this, I am passing a JSON object as a message and catching this message on page before showing it to users. This allows me to pass the message type or even a unique color, icon and other things (like a DA name to fire after the message). You can modify it however you need. To simplify this and make it more readable, I have created 3 JavaScript functions: show_success show_warning show_error const show_success = function(msg) { apex.message.showPageSuccess(JSON.stringify(get_message(msg, 'SUCCESS'))); }; // const show_warning = function(msg) { apex.message.clearErrors(); apex.message.showErrors([{ type: apex.message.TYPE.ERROR, // sadly no warning supported location: ['page'], message

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