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!
https://t.co/zNiKh9tKSq
@JuergenSchuster Exactly. You can directly ask in Claude, Codex, etc. something like "spawn a sub-agent to review your work". Basically 4 eyes principle also applies to LLMs.
@JuergenSchuster Same question in my team right now. Curious where you're landing: review every .apx diff, or lean on tests and review only the security-relevant parts?
How are you dealing with the #orclapex conundrum that AI generates very well working #APEXlang apps, but would you deploy it on PROD?
You still want to have a manual review process which kind of neglects the AI speed advantage. And AI develops stuff not the best way, you would have done.
How are you doing it with the AppBuilder Development? @sspendol
@JuergenSchuster Additionally playwright E2E tests. But important let another context write the tests. Same as with humans, another person than the dev finds more flaws.
@JuergenSchuster For my stuff I will definitely look over it. In my experience I often need iterations to come to a solution I deem worthy.
Also was the same when developing manually. Not often is the first solution the best.
@OracleAPEX #orclapex
1. Are you developing new features for the App-Builder with APEXlang?
2. Can you tell us exactly how you do it, what tools, skills, guardrails, etc. you use?
3. Is there a manual review process, before you take it to production?
Share with us, what you do, so we don't have to invent the wheel by ourselves.
🚨 Attention APEXlang users! 🚨
If you've recently upgraded from APEX 26.1 to 26.2, and you're using APEXlang, you'll want to check out this blog & video by Steve Muench.
Details here:
https://t.co/v0HAaWvIvF
#orclapex
@sspendol It's the other way around! @Oracle hit the Jackpot when they finally realized what treasure they had with #orclapex for 20 years before they figured it out #LetsWreckThisTogether 😉
We built impressive #orclapex apps that look and work exactly in our company style based on a generated "template app" which are just typical pages from different apps.
It's hard for me to admit it 😅 but this whole APEXlang approach is 100% working 😳👏👏👏
@JuergenSchuster Skills are always going to be APEX version specific.
Latest version has a router that will re-direct to 26.1 or .2 depending on the version of the app. Simple + elegant.
Most new work will always be on latest version.
#orclapex
Hi Scott,
we are wondering regarding APEX app generation based on a requirement definition file, would it be much better to do it with 26.2 instead of .1?
And should we only use the new skills für 26.2 or also upgrade them if we are on .1, if there are components in the skills which only apply to 26.2?
So in general, should we rather not use skills that are meant for a new APEX version?
@sspendol@askMaxSolutions