Replying to @moreaux_louis
Hi Louis, APEX may already has you covered. Enable “Enable Dictation” under Shared Components → Security Attributes → Browser Security, and a mic button appears in our AI Assistant and the Interactive Report’s natural-language feature. #orclapex
Replying to @JuergenSchuster @sspendol
Single APEXlang export for pages is already available in 26.1, but to be honest I would always advice to do a full app export so that all your other components are also up-to-date in your file system. Page Designer -> Utilities -> Export
Replying to @swesley_perth
Hi Scott, we can certainly discuss improving the list, for example, by adding usage-based suggestions or re-ordering entries, but in this case, why not simply use the existing Quick Picks feature?
Replying to @andre_blu @OracleCloud
That's triggered by the workspace parameter "Maximum Concurrent Session Requests" (Instance Admin -> Manage Workspaces -> Existing Workspaces -> Workspace Isolation.
Was your question why you even get the error or about where to configure this?
We’ve added a new sample application to our Gallery, demonstrating the power of Vector Search in an APEX app. Huge shoutout to our intern Nicolas for making it happen! 👏🔥 #orclapex
Replying to @Schultz_APEX
In Page Designer when you define an Invoke API process we will setup the process with the params of the first API, but you can update the param names, ... to match with another variation of the API which will then be used at runtime. PD shows a warning if an overload is detected
Replying to @mortenbraten
As mentioned in the thread, the first day of the week is derived from the sessions NLS_TERRITORY setting. Set your primary application language to a sane English-speaking country like "English-Ireland" 😀
Replying to @jeffreykemp
It might be the shortest code, but in a year / other developers will have a hard time understanding this code. Why not just go with the CASE. That's straightforward code and easy to understand. But let's throw in DECODE too if we already on it 😉
Replying to @LinoSchilde
For any other app-level authorization we do expose the flag "Run on Public Pages" where you can control that. But why even set "Must not be public user" if you want to exclude public pages? Just clear "Must not be public user" and you get exactly what you want.














