@JaysonHanes Last year also had an atypical release schedule, so that is two years in a row now 🙂
As @JuergenSchuster said, the issue is not the release date but the lack of communication with the community. APEX grew and shined thanks to the community too, not only Oracle. It used to feel like a two way street, now it feels one way.
@JuergenSchuster@OracleAPEX They tried but couldn’t land it, so they brought Spendolini back to keep the story alive. Meanwhile it’s patchsets and “events” on 24.2. Stock’s up, Larry’s richest — no rush till 26.1 😁
@JuergenSchuster@OracleAPEX Well, it's vacation season, I don't expect it anytime soon. Maybe they'll give it to us as a Christmas gift, and then patchset 1 will become 25.2 just around New Year. 😊
@sumantk49@DustinGHamilton@marcelolima Why can't you imagine future AI interfaces acting as a business analyst, system architect, developer, QA, etc., all in one? So basically, AI will translate an end user's needs into working software all alone. Looking at the current pace of AI advancement, I can see it coming.
@keeganwalker_ No, we are just expanding to BSky, so we can add one more channel of communication beside x, slack, telegram, linkedin, blog posts, etc. The only thing that bothers me is, when I see same post here and on BSky should I reply same to both?
@OliverLemm@ralf_mueller Promising since its announcement at APEX Connect 2024, but the real question remains: when will it actually be available? With AI advancing rapidly, Oracle APEX must deliver to stay relevant. Let’s hope #APEXLang is in production no later than version 25.1. #orclapex#doag2024
Hey #orclapex community! Do you need a filter for elements in Rendering, Layout, DAs, and Processing tabs in Page Designer, like we have for properties? How do you manage without it? Want this in the next APEX release? Check this idea and vote!
👉 https://t.co/6N4Qari6Zx
Anyone else having issues with #orclapex automations and DST? 🌍 We had duplicate reports sent due to lack of timezone settings. Has anyone found a solution? Here’s the idea, which may have been dismissed too quickly: https://t.co/ycF4LrzycK
🔍 Possible #orclapex bug! When using an anchor and success message within Link Builder, the anchor isn't placed at the and of URL but in the middle, between request parameters and success message. As a result, the page doesn't scroll to the anchored position. Any help?
@alexnuijten@OracleAPEX I had the same problem. It turned out that job_queue_processes was set to 0, it seems like WC compare and merge are dependent on jobs.