I just gave a talk at the Australian User Group (AUSOUG) about using open source plug-ins in APEX. Ok, my presentation probably sounds a bit like a snooze fest, and I’m not one who enjoys presenting, but with all that said: how did it go? Better than I could have expected. Why? because I felt inspired by the work we have been doing of late.

Some Background First

You have to love the redesign of apex.oracle.com. It looks really nice, they paid a lot of attention to detail, but the most striking thing about the landing page is this statement:

But, Can APEX go even faster?

Yes it can!

How you might ask?

One word: Plug-ins

Of course there are those that might object:

• plug-ins aren’t safe
• we don’t know what they do
• they might stop our app from being upgraded in the future
• we’re not allowed to use them

Those are all fearful statements. What’s the simple answer to them in one word?

Support

You just need someone to support them/you. Someone you can rely on to be there, not just tomorrow but in 1 year, 5 years, 10 years.

It could be one or a handful of rockstar developers in your company. It could be an existing company that you already have a relationship with. But if you don’t have either of those, then we can be that company!

It’s what we do!

We have been building plug-ins since their inception, in business since 2012 and having a team dedicated to their support and the continual building of more. We will be here in 5 years, and we can tackle the most complex problems and love every minute of it. How many companies have their leaders “all in” on APEX and “all in” on APEX plug-ins? I don’t think there’s many….

When we first started our business we started by selling commercial plug-ins. Why? Well, to survive longer than a couple of weeks you need to make money. That’s not an easy game, but we did it, and we have some faithful customers that have been with us from the start and others that have joined along the way. This also made us the black sheep of the community. We were trying to sell you something.

Fast forward to 2020 and we’ve been able to keep building plug-ins this whole time. As a company our entire team is “all in” on APEX. We have to tell our team to not work too much, as it has become one their hobbies too as they really love what they do. We’ve found some real diamonds!

As a team, we’re passionate about filling the gaps in APEX. We do this for the people who fall into these gaps and want to get out. This is why we have released open source APEX plug-ins that are free to use. We want to help as many as possible, and since the work is already done, it’s better that they get used by a lot of people than just a few.

Check out our free APEX plug-ins and free APEX Builder Extension to manage your application and workspace, theme, and plugin files.

Community

There are now 275 plug-ins on apex.world and we’re now contributing 15 of those, with another bunch to come shortly. We also support another 15 or so from other plug-in developers with more to be included in the future. We feel like part of the community again, as we’re not solely trying to sell you something. We want to help you and if you need it? give you our support. We want you to do even more with APEX. It’s the same development tool we love, just like you. We’re on the same team. Let’s build more plug-ins. Let’s build applications faster, let’s do it with APEX, and let’s continue to show the other Oracle developer communities why APEX rules!

In Summary

2020 is winding down, it’s been one for the record books and not for all the right reasons. We’re looking forward to 2021 and we will be bringing out a bunch of new plug-ins in the coming months to make APEX even greater, and we hope there’s a bunch of you doing the same. Tune into apex.world to keep an eye on what’s coming.

See you online or hopefully in person at a conference in 2021!

P.S. If you’re wondering about my choice of blog title, it comes from this “Tropic Thunder” clip (background music). I’m pretty sure I heard “low low low low low low code”

1. Region Splitter
2. Download File(s) Dynamic Action
3. Download File(s) Process
4. Redirect Dynamic Action

Lets have a look each of them in a little more detail:

Region Splitter

Have you ever been tasked with designing a page with many regions that require a specific layout that needs to be responsive? It can be a time consuming and frustrating task especially when you get conflicting feedback on which region should be wider or thinner during user acceptance testing. You might end up writing a bunch of CSS and in the worst cases some Javascript to achieve something everyone is happy with.

If you find yourself in this position then consider using our new splitter plug-in to make things much easier for you. You can even nest splitters within splitters to create some pretty complex responsive layouts.

[This post contains video, click to play]

Zip & Download File(s)

How many times have you found yourself adding some PL/SQL to your application to download a file? What about zipping and downloading multiple files? Or how about a subset of files that the user chooses? If you’re like us, this requirement can popup many times. So we thought we’d make things a little easier for ourselves (and everyone else) by writing 2 plug-ins to do all the work for us. You might find yourself asking why did we create 2 plug-ins instead of just 1? Let us explain…

Process plug-in

Using a process plug-in is very similar to the way we’ve all been downloading files using some PL/SQL that we’ve found in how-to’s etc. on how to do this. In most cases you simply create a blank page and add your process in a “Before Header” point. By following the same approach with the plug-in it makes it easy for replacing existing functionality if you wanted to offload some of your code maintenance.  e.g.

Downloading a File using a Process

Dynamic Action Plug-in

This plug-in allows you to download files in a dynamic action, meaning you can run some actions before and/or after the downloading of file(s). It gives us much more flexibility than a process plug-in and allows us to gracefully handle errors without being redirected to the application error page when a PL/SQL exception is raised. We’ve also included file preview support for images, pdf’s, and text/html files in either a dialog or a new browser window/tab so you can give your end users the option of looking at the file prior to downloading it to their local file system.

[This post contains video, click to play]

Redirect Dynamic Action

How many times have you found yourself wanting to redirect to another page after performing several actions first, and have found yourself having to use “Submit Page” with some branching logic before or after processing. Sometimes submitting a page can cause some unwanted side effects like client side validations firing, or needing to run some PLSQL prior to branching resulting in adding extra conditions to all our validations/computations/processes/branches which can result in a fair amount of work.

We’re introducing a new plug-in to avoid this issue. Inspired by the original Redirect plug-in from Menno (who’s now an official member of the APEX team) we decided to add our own version which has the added bonus of letting you execute some PL/SQL prior to redirecting and allowing you to change the URL at the time of execution.

[This post contains video, click to play]

In Summary

You can see a live demo of all of our FOS plug-ins here in a single application which you can easily download and install in your own environment. Alternatively you can go directly to apex.world or GitHub to download individual plug-ins.

Hopefully you find a use for one of these in your apps at some point in the future, and remember these are supported free plug-ins, so there shouldn’t be an argument why you shouldn’t use them

We recently announced our new company initiative called FOS which is dedicated to everything open source. Part of this initiative is to offer an affordable low-cost commercial support service for plug-ins developed by anyone. We want to encourage the use of plug-ins and we want you to feel safe in the knowledge that you have someone to call on when you need help.

Our team has been building plug-ins since the plug-in architecture was introduced in APEX 4.0. We have built hundreds of plug-ins of all types and sizes. We have a team of APEX plug-in specialists with Javascript expertise. You can count on us to keep them working for the lifetime of your application. We have the skills to support any plug-in of any size written by any author.

In the beginning, we are offering a list of specific apex.world plug-ins that we support. We will work with the existing developer of the plug-in to resolve issues and help with improvements, whilst compensating them for their time & effort. In situations where this is not possible, or it’s a plug-in built by a 3rd party or in-house, we will make the necessary changes & fixes. For open-source plug-ins we can fork the plug-in to provide and issue GitHub pull requests to keep the main plug-in up to date for everyone’s benefit. You can find the initial list of plug-ins we support here.

If you are using other plug-ins that you want support for, contact us, and we can come to a custom support agreement for your situation.

Why offer Open Source Plug-in Support?

APEX open-source plug-ins are great for the reason that they provide missing functionality from APEX which you can install and use just like you would a regular APEX feature without writing the code. They’re free to use and you can get them from apex.world, or in the past from apex-plugin.com, or even Oracle’s website. They are a boon for productivity and in many cases provide the functionality we wouldn’t be able or have the time to create ourselves. However, they are not used in many business applications for a number of reasons.

APEX Plug-in Challenges

There are several drawbacks to using open source plug-ins, the No.1 being who’s going to help me when it breaks after upgrading to a new version of APEX? and who can help me quickly? delays cost money, not being able to upgrade costs even more down the line. It’s a bit of a stretch to believe the plug-in author is going to fix it for you immediately and do so without being paid for it. Some plug-in authors do, but there is no guarantee even from those ones when it comes to the time that “you” need help.

Sadly this issue means that a lot of companies do not use plug-ins or have a very short list of allowed plug-ins. Therefore developers miss out on functionality and productivity benefits. You end up having to write the code yourself, meaning you need the expertise and must also make a time investment into the creation and maintenance of your solution. If you don’t have these skills or the time to invest then you end up forgoing that functionality and the users of your application are the ones that suffer.

As plug-in advocates, this is something we would like to address by offering a support service for open source plug-ins, or plug-ins your company may have developed but no longer have anyone to support it.

What about other plug-ins?

If you would like to have an apex.world specific plug-in added that’s not on the list, simply let us know. We will review the plug-in and reach out to the developer to add it to our list of supported plug-ins. For plug-ins you have built in-house and would like to remain private we can come to an agreement on support costs. For older plug-ins from apex-plugin.com we can also come to an agreement on how to support them for you too.

Are you a plug-in developer?

If you are a plug-in developer and would like to have your plug-in included in our support package please contact us. We will review your plug-in(s) and let you know if we can provide support for them i.e. there are certain criteria your plug-in must meet to be included e.g. security, code quality, type of plug-in, potential usage, etc. We can be the first line of support that enables your plug-in to be used in more applications than it otherwise would be. We will also be able to compensate you for your time when you provide any fixes for a support customer.

In Summary

If you find yourself arguing with your team or management to use a plug-in, or you are using a plug-in and it breaks when upgrading, now you have a stronger case as you can answer “who’s going to support it?” answer: “the FOS team will”. You can find out more here.

Release Schedule

We plan to release a version of FOS plug-ins after every APEX release. The minimum APEX version requirement will be APEX 19.2. The first version of FOS that we released was 20.1, which supports both APEX 19.2 and 20.1. The next scheduled release of APEX is 20.2, therefore we will release version 20.2 of FOS, which we guarantee compatibility for 19.2, 20.1, and 20.2. We will continue to release a version of FOS for every version of APEX.

Free Support

All free support will be done through GitHub. If you encounter a bug or have a problem we kindly ask that you raise a GitHub issue and we will provide a prompt response. For serious issues that affect the ability to use the plug-in, we will address and resolve these immediately. For small issues and minor improvement requests these will most likely wait until the next major release of both APEX & FOS. Free support entitles you to:

1. Create GitHub Issues
2. You can fork the plug-in and provide your own fix and issue a “Pull Request“

Paid Support

For companies that would like a support guarantee and the ability to have direct contact with our FOS team, you can sign up for our annual support subscription for a meagre 1000 EUR/Year. Paid support entitles you to:

1. You will have access to our support portal and access to all patches/hot fixes
2. You can raise a support ticket through our support portal
3. We guarantee a fast response and expedited bug fixes
4. We will prioritise your enhancement and new plug-in requests
5. Your financial contribution will help us grow the number of plug-ins we provide

In Summary

There’s shouldn’t be anything stopping you from using these plug-ins in your application. Whether your application is commercial, closed or open source. They will remain free and you will have support for them for the lifetime of your application. Whilst there’s the old saying “there’s no free lunch”, well there are “free plug-ins” instead

Overview

About

FOS plug-ins are a professional set of commercially supported open source plug-ins for the benefit of the Oracle APEX community. These plug-ins have been built for regular APEX applications and work standalone with no dependencies. You can use one, a handful, or all of them. It’s your choice. The plug-ins have been created to provide missing declarative APEX features or improvements to existing functionality. The plug-ins have been designed to help you improve your development productivity and solution capabilities.

You can head over to fos.world to see them in action, and download.

The APEX builder has improved so much since the release of APEX 5.0. As developers our productivity has increased by orders of magnitude, but for one area  i.e. editing Javascript & CSS files stored under static application files or within the definition of plugins, we have had to rely on external tools, like Sublime or Visual Studio Code. To workaround the pain of deleting and re-uploading of files and minifying them, you might be using APEX Nitro (and Node JS).

These tools combined offer a good workflow, but also depend on having these tools installed on your laptop. Sometimes you might not be on your laptop and need to make a change to a file, or sometimes you company might not allow Node JS to be installed on your laptop, or installing/using APEX Nitro might just be one step too far for you. When this is the case, making changes to these files is quite an arduous task.

The Solution

Since we’re a company that focuses on improving end user productivity through good design, we decided to solve this issue. How you might ask, since this is the APEX builder and we have no control? Well, you actually have more control than you think, thanks to modern browser extensions! We’re introducing a new one for the APEX community that its sole purpose is for APEX Builder improvements for regular APEX applications. It’s called the “APEX Builder Extension by FOS”. If you’re wondering who/what FOS is, well it’s simply an acronym for “FOEX Open Source”.

The extension combines the Visual Studio Code Editor with Javascript and CSS minification, Less compilation with the ability to edit and create new static application or workspace files and plugin files using the existing APEX Builder screens. It has zero dependencies on external resources, apart from the extension itself of course!

Overview

Installation

It’s free to use and open-source, no strings attached! Simply click on the button below to add to your browser. You can also find the project on Github if you want to take a look behind the scenes.

Add to Chrome
Add to Firefox

Dark Mode

Light Mode

Features

Create and edit static application, workspace and plug-in files

Once you’ve installed the extension, on each of these 3 pages you will find a new region, called “Edit Files.” Either choose a file from the dropdown list to open it, or click the “Add File” button to create a new one. You can then edit your file, and click the save icon to save it. No page submit required.

Enjoying editing one file? Try editing 2 files. Although… why stop there?

You can open as many files as you want. What’s more, you can drag and drop a tab to enter split screen mode. Although the most common use case will probably be having a JavaScript file on one side and a CSS file on the other, you can arrange the panels any way you want. Also note that the gutters between panels are actually splitters. So you can resize them as well. Check out this demo for an idea of the behaviour….

Fullscreen mode and keyboard shortcuts

The extension attempts to provide as good of a programming experience as possible, so in order to feel more like editing in a conventional editor, you can enter fullscreen mode. You now have a better, more focused view, and can’t accidentally scroll beyond the editor. Want to exit fullscreen mode? Hit Escape. Another handy shortcut is crtl-s on Windows, or cmd-s on Mac. While having the focus in an editor, hit this shortcut just like you would on a desktop editor, and your changes will be saved.

The editor

As you might have noticed, this extension doesn’t use the Code Mirror editor, like the rest of the APEX Builder. It instead uses Monaco, the same editor as the one behind Visual Studio Code (VS Code). Were you aware that VS Code was written in Javascript and HTML5? Amazing huh, and since it is, we can also use it within APEX! By using Monaco, it means that it comes packed with many of the same great features that VS Code has to offer, such as descriptive error and warning messages, autocomplete, intelli-sense, and much much more.

JavaScript file minification and Less file compilation

The extension also introduces the ability to minify JavaScript files. Just click the “Minify” icon, and your file will be saved and minified. You should then see a .min.js version of your file appear in the select list and in the files report.

There’s also functionality for compiling Less files. This is already possible via the Theme Roller, but we’re bringing this functionality to the static files as well. Just click the “Run” icon and your file will be compiled. You should then see a .css version of your file appear in the select list. In the future we’re looking to include SASS compilation too.

How did we get this to work?

In short, we fetch the file contents by leveraging the already present file download links on the page, and behind the scenes open and submit the Upload File(s) page to save the newly updated content. There’s nothing additional that we do code wise to save the files on the backend, it’s all handled by the APEX engine. It’s really fast too, so you probably won’t even notice it, since we’re doing this without submitting/reloading the page i.e. Single Page Design style, which is how we’ve been designing and building the majority of our APEX applications for years. We know APEX inside and out!

Roadmap, technical details, and more

There’s a number of things we’re looking at doing, you can see the Github page for more details. You can log your own feature requests and report any bugs/issues there too. Stefan Dobre is the lead developer on this project and really passionate about APEX & super talented! You can follow him on twitter and read his APEX ramblings on his blog. We’ve got him working on quite a few interesting things that you might find very helpful in the near future, so keep an eye out for his tweets and posts.

We hope you find this extension useful and are looking forward to your feedback.
#LetsWreckThisTogether

Overview

Perform all your image editing/transformation requirements in the browser on your phone, tablet or desktop. With no additional dependencies, simply make your desired image changes and upload the finished result by simply clicking “Done”! Super quick to install and use, simply “Import -> Add Region -> and Run” in literally minutes with zero coding!

Speed up your development and speed up your users workflow by enabling them to do everything they need with images without resorting to external programs. It’s a win-win and great time saver! Features include:

File Uploading

Image Editing

Image Annotation

File Transformation

Edit Existing Files

Actions

Live Demo

License

This plugin requires a commercial license to use. You can find out more information here

Footnote

As we have focused purely on in browser functionality you may have a requirement to batch process your images or process them server side, similar to Oracle Multimedia. Given that Oracle Multimedia is deprecated / being removed from the database you should consider APEX Media Extension by APEX R&D. If you’re wondering why we are releasing somewhat similar functionality to them is basically, “we didn’t know”. We started work on this project back in June 2019, and development at the end of November.

We can say we were surprised in December when they initially announced “APEX Media Extension”. At the same time we were focusing on browser only functionality without any server dependencies Vs their serverside implementation. We have spoken with APEX R&D and we both see the competition as a good thing, it will benefit the community. We will continue to do our best to serve our customers with the best possible tools to make their job easier, and their application users happier.

Then make sure you’re in Vienna, Austria on the 21st of April. Located at the Oracle office in central Vienna, with a view like this, how could you miss it?

Oracle Office in Vienna

With the AAApeks conference in close proximity in Maribor, we have been fortunate enough to additionally organize both Shakeeb Rahman from the APEX team and an Dan McGhan the Oracle Javascript evangelist, to present at this free half day event. Expect some serious Javascript, CSS, and Design explanations from these experts.

Agenda

13:00 – Start and Intro – Peter Raganitsch (FOEX)

13:15 – Getting Started With JavaScript For APEX Developers – Dan McGhan (Oracle)

14:00 – Break

14:10 – Getting Started With JavaScript For APEX Developers – Dan McGhan (Oracle)

14:55 – Break

15:15 – Universal Theme deep dive – Shakeeb Rahman (Oracle)

16:00 – Break

16:10 – Applying your corporate look and feel to Universal Theme – Shakeeb Rahman (Oracle)

16:55 – Break

17:00 – Q&A

17:30 – End

That’s right folks, we will say it again, it’s free, you just have to register & show up! That should be pretty easy to convince the boss? or have a day off work? shouldn’t it?

P.S. why not make it a week off work and also attend APEX Alpe Adria in Maribor on the 24th of April. A couple of days in Vienna and a couple in Maribor, combine some work & sightseeing & fun at the same time!

In this release we are introducing a new addon to introduce live editing capability of the grid, tree grid, and editable list views using websockets. You will be able to see realtime changes and a realtime visualization of other users modifying data in the same view of data you are viewing. Just like you can with Google spreadsheets.

Grid Demo

[This post contains video, click to play]

Tree Grid Demo

[This post contains video, click to play]

List View Demo

[This post contains video, click to play]

Notify Other Regions Demo

[This post contains video, click to play]

This is achieved using websockets and Node.js. Setup is simple as checking a checkbox under the options within your region attributes. You can configure an unlimited amount of regions within your application as well as broadcast between regions that share similar data.

Simply check the option to enable!

You have several states the live editing can be in i.e. Online, Paused, and Offline

Online, Paused, and Offline states

There are a number of predefined defaults which can be customized as per the following settings:

Websocket Region Settings

You can enable row or cell level locking when users are editing grid records e.g.

Row Level Locking

Cell Level Locking

You can even (optionally) see who also editing the grid and even see their recent change history and what they actually changed e.g.

Active Users

User Change History

PLSQL API

Additionally we provide a PLSQL API to allow you to send messages directly from the database via a REST call. You would want to do this in situations where the data is being changed in some batch processing code, or “Execute PLSQL Code” dynamic actions separate from the region’s CRUD requests & refresh row actions. Simply provide a cursor of the changed records you want to broadcast and they will be sent to the websocket server which will message all users registered on the channel(s) you specify. Remember to make sure that your query columns match the same column aliases as your grid/tree/list SQL query columns. Here’s a basic example:

DECLARE

  l_cursor SYS_REFCURSOR;
  l_oid    FX_T_DEMO_COMPANY.OID%TYPE;

BEGIN

  l_oid := v('P1_OID');

  OPEN l_cursor FOR
    SELECT OID
	 , COMPANY_NAME
	 , STREET_ADDRESS
	 , POSTAL_CODE
	 , CTY_OID
	 , PHONE_NO
	 , EMAIL
      FROM FX_T_DEMO_COMPANY
      WHERE OID = l_oid;

  fx_p_websocket_notify.data_notification
    ( p_static_ids => 'CELL_EDIT_GRID,ROW_EDIT_GRID' -- you can update multiple regions
    , p_cursor	   => l_cursor
    , p_operation  => 'update' -- create, update, delete
    );

END;
/

Performance

FOEX Live Editing has been designed with performance in mind. There is no additional overhead on the database by enabling this functionality. All data relayed over the websocket is done securely by the browsers after the data has returned from the server. For example: when an update is performed on a Grid, the changes are made in the database, the rows are re-queried and sent back to the browser, and then the browser sends this data to the websocket server to be broadcast to all other users listening on the region’s private channel. There are no AJAX calls back to the database to grab any data, even for checksums etc. as this is all provided in the response from the grid update. This applies to all CRUD operations on all region types, forms, grids, tree grids, and editable list views.

For the PLSQL API we use a REST call that allows the database to directly broadcast from one record up to thousands of records in a single call using a SYS_REFCURSOR type.

For the visualization of the changes within the regions, we only apply highlighting to the records the user is currently viewing. We do not apply any highlighting to records that are not in view and must be scrolled to. This maintains optimal browser performance since there’s no point showing any highlighting or animation of changes the user can’t see.

For the websocket server itself we went for a high performance lean implementation using the npm ws package. as opposed to using something heavier like Socket.io. This gives us greater control and flexibility for how we designed the registration & communication system.

Security

You can use SSL mode for both the Websocket and REST endpoint or HTTP during development. We use token based encryption to secure connection to the web sockets and regions register what columns users are allowed to see to ensure that data or parts of data are not broadcast to users who should not see it. Note: the column list is encrypted to avoid any client side tampering.

The encrypted data uses the AES 256-bit algorithm with Cipher Block Chaining and PKCS #5 padding.

In Summary

For some businesses the difference between knowing something now vs in 1 minute from now can have a huge impact. It can save lives, it can give you a competitive advantage, it can make you more money. This is what you get with FOEX Live, seeing your data changes in realtime and being able to immediately respond and make decisions based on these changes.

Debounce & Throttle Dynamic Actions

In this release we are adding additional dynamic actions to provide some missing functionality in APEX, which is the ability to deal with actions that fire too frequently e.g. you probably don’t want your TRUE actions to fire until a keyup event (when the user is typing) until they have stopped typing for say 1 second. These new actions we are adding are Debounce & Throttle.

What’s the difference between Debounce and Throttle?

Debouncing enforces that a function not be called again until a certain amount of time has passed without it being called. As in “execute this action only if 500 milliseconds have passed without it being called.”

Throttling enforces a maximum number of times a function can be called over time. As in “execute this action at most once every 500 milliseconds.”

The interesting thing about these actions is that they only apply to proceeding actions, so you can define actions before them that will fire every time the event fires, thus giving you much more flexibility. Note: the only requirement when using these actions is, you must set “Wait For Result” to “Yes”

Debounce proceeding actions

Inactivity Timeout

We have introduced an improvement to both the Timer and Message Box plugins to allow developers to easily include an inactivity timeout warning. The Timer plugin has a new inactivity timer option which will be triggered when the user has not moved their mouse or pressed a key for X many seconds. Here’s a simple example where we will reload the page after detecting inactivity.

As you can see in the image we provide a progress indicator with a timeout message. The OK button is included to allow the user to prevent the default action from occurring e.g. page reload, session timeout etc. Since the “Message Box” allows you to define PLSQL you can use this setting in conjunction with the application Idle timeout to prevent the APEX session from timing out as well. Or you could use the “No/Cancel/Timeout” PLSQL to log the user out e.g.

apex_authentication.logout(:SESSION, :APP_ID);

APEX 19.2 Support

APEX 19.2 Support

With this release of FOEX we now support APEX 19.2. You will be able to take advantage of all the new features APEX provides e.g.

• Faceted Search
• New Popup List of Values
• REST Enabled Interactive Grid
• New Dark Mode Theme Style
• Team Development Improvements
• Plus many other improvements

Other Improvements

Thanks to the continued use of FOEX from a growing customer base we receive requests for enhancements and improvements. Whilst we can’t implement every request we receive (for different reasons) the following improvements have been introduced in this release:

• New expand/collapse rows functionality for tree/tree grids
• Deselect capability in Single Grid Row Selection
• Allow typing in the grid combo input
• A new declarative option to “Save all Records” in the grid
• New actions to suspend/resume auto save on grids, trees, and lists
• Include changes made to grid rows in the POST Processing Procedure hook
• Define namespaces for caching e.g. for multiple views of the same page
• Auto Size content height in the grid row expander
• Add list support to grid column search menu via the additional config setting:

  "filter":{"type":"list","single":false}

• Triggering Event option to locate rows by e.g. Refresh Rows Action
• Tooltips added to Form navigation buttons without labels
• Plus a number of other minor improvements and bug fixes

You can find more details about the above enhancements in the release notes here.

Please reserve your seat at the event page: https://www.foex.at/aop-training-20191108/

The training will take place on November 8th 2019 and seats are limited !

Join us on this day and learn how easy printing and reporting can be done with APEX and APEX Office Print.