Testing APEX 26.1 Interactive Reports New Features

Search for a command to run...

No comments yet. Be the first to comment.
Context is one of the most important things when working with AI. That's kind of the agent "memory" during the session. A key part of the context giving the agent instructions on what to use for speci

A new Data Source was included in this release, you can see it when including a new component, it's called "Sample Data" Some components like maps, charts and Calendar have this source type now, that

This is a great combination for something the used to take some effort on writing some functions to execute actions on specific rows of an IR, like using a hidden page item, assigning the PK value of

Creation of a parallel translated app is no longer the only way to handle multiple languages in APEX. Now under Globalization Attributes, we can select "Text Message-Based" as Translation Method. On

Recently, I created an APP using APEXlang, (check here). I asked the agent to create a lookup table including columns to store colors and icons, useful to work with status for example. The agent no only created the table, but filled with values for the lookups, fa icons and color palette clases.
I'd like to take advantage of this to test some of the new features on Interactive Reports delivered in APEX 26.1, using one of the IR automatically generated:
First, I'm going to include those columns in the query report query
then I just need to go into the status column properties, and use the new "CSS Classes" option to include the name of the column holding the class.
And that's it. That saves us from a lot of JavaScript we used to develop to get the same behavior.
There is a way now to invoque IR options from the Actions menu. Let's say I create a button to download the content on the report. Right clicking the button displays now "Create Triggered Action"
Inside that action properties, we can select under Identification the Action "Invoke Interactive Report Dialog".
Then under Settings there is a second Action, where we can select the option from Actions Menu. In this case, I'll pick "Download"
As result, when the button is clicked, the download options is displayed as if we selected Actions -> Download from the menu.
Small changes but for sure will make our lives easier during development and improve delivered apps User Experience by reducing the number of steps to execute an action.