Want to become an #orclapex UX-Designer in 60 minutes? Here is my recorded #ux presentation, now as YouTube video. @APEXAlpeAdria Have fun and let me know what you think!

@crokitta @andre_blu @sir_agnostic @vincentmorneau Ahh, thanks, I knew that this feature was there at some version, but I couldn't find it and still used the old FOS timing Plug-in

@realDonaldTrump That makes my day. Back to common sense ✌️

@elonmusk Agree, paper straws are disgusting

@andre_blu @sir_agnostic @vincentmorneau Well you can stand behind a car and honk that he should disappear or you overtake him right or left and move on. Different life approaches 😊

And to make things really interesting, imagine following #orclapex scenario: Let's say you have pill buttons of the last 3 years and 12 months, easy to click very fast. Every click creates a AJAX call with a partial page refresh. You can easily shoot our 3-5 clicks "at once" and create 5 DB sessions. The more buttons you click the smaller the data pool to filter and the more likely indexes are used. This said. The later clicks come back earlier than the very first click. Long story short the slowest SQL wins and will eventually refresh you IR. Now you have active buttons of a year and 5 months but the result showing you just the whole year (without the months) because it was the slowest SQL that overwrites everything before. Now you make wrong business decisions because your filter shows 5 months but the result set shows the whole year 😉 If you ever hit this problem @askMaxSolutions has a Plug-in for that. Haven't encountered any problem that it technically solvable with web technology but not with APEX.

Back to square one. You have exactly this functionality which creates a nasty overlay focusing on the delay instead of the result. Submits should be the absolute exception. Try everything being stored or partially refreshed by Dynamic Actions to speed things up. If you have to do a submit use the Timer Plug-in from @Plug_ins_Pro which avoids duplicate pressing of buttons.

Let's say your page is back within 2 seconds which is good enough (below 1 second it feels immediate, 1-2 you are not waiting but keep your focus, 3+ seconds, your mind starts wandering and it feels slow). The user hits accidentally the submit button twice, he wouldn't realise it even if the process is running twice because the screen would not change after the first rendering and the user has the performance feeling from the first rendering the second one is not visible. You can always put a debounce on a button that it only reacts once within 2 seconds.

@connor_mc_d I know that urge if you are getting older and need to find the bathroom fast 😅

@sir_agnostic @vincentmorneau @andre_blu Agree with Vincent on this one, even if it is hard for me 😅 You should have a fast submit and a processing overlay would put extra attention to it so it feels slower then 🐌

So, last #orclapex @OracleAPEX Office Hour. After a very rough start I think it's fair to say that it was an impressive 24.2 release. Features for everybody especially for us "external" customers ✌️ All you have to learn now is actually selling it, let me know if you need help 😊

@dgielis Use the #orclapex AI Assistant. It is trained with the new version and API from day 1 ✌️

@MyRISK_AU @OracleAPEX @shakeeb @MikeHichwa This is not what I mean, but something like or Maybe it's stupid to use #orclapex workflow engine for that, but maybe not, it was just an idea 😌

@MyRISK_AU @OracleAPEX @shakeeb @MikeHichwa Sounds interesting, can you elaborate on that? Example for a 12 year old 😊

@McilroyJackie @JaysonHanes @thtechnology @the_saraBgood @monty_latiolais @odtug Who is the girl in the blue shirt? 😌

Jayson, the whole start of this thread was: "I tried the sample app on aoc and it didn't work". So the 20 years expectation of #orclapex customers, once you have the right APEX version, all the features work everywhere is obviously NOT the case anymore. And it would help to point this out to your customers that you need 23ai if you want to use the Oracle Vector DB. is NOT on 23ai yet, so it does NOT work there. The APEX Service? I don't know, nobody answered this question yet, even if I asked twice in the Office Hours. It's not the right answer to say, oh you can always find a workaround with an external Vector DB or an externally hosted model. You all should know this because we mentioned it once in an Office Hour a year ago 😉 But yeah it always comes down to one thing. Do I see the needs of my customers and do I care or not 😉

@elonmusk I can understand the cult around @realDonaldTrump. He just makes the water flow and quench the thirst of the thirsty 😇

I would appreciate it if it were made clear with all the AI features of #orclapex what you need for it. Is this available on OCI only? Does it work with the OCI APEX Service. Does it work on perm, what DB version do you need. Before AI we didn't have this problem 😌 When APEX ran you could use all the features.

@DenesKubicek @patrickwolf aoc still runs on 19c

Warning: Don't watch "The Silo" on @AppleTV besides the regular #DEI crap it's pure propaganda at the end. The sleepers will wave their flag though 😉