Skip to main content

How to reset an APEX process

While I was setting up a demo the other day, I ran into the following issue: My main start page contains a list of customers and that list is created by a call to a (remote) web service. Due to the nature of this service, it takes a few seconds to get a result back - not very slow but slow enough to annoy me. So I looked at ways of caching the web service results as I noticed that in the process definition I could choose for either "Run every page visit" (default) or "Once per session or When reset". And I would like to reset the results when I entered a new customer - so it would show up after a new web service call. So the only thing I had to do is "reset the process". But wherever I looked - especially in the apex_util package - nothing that would do that trick. Searching the OTN Forum or old fashioned Googling neither added to a solution. A "cry for help" on Twitter resulted in a work around - "accidentally" the same one I had thought off: Add a copy of that process to that page and fire that on request only.
But after a day Patrick replied, unveiling there is an (undocumented) procedure apex_application.reset_page_process (with the internal Process ID as the parameter) or apex_application.reset_page_processes (with the Page ID as a parameter). So I tried the second one - because it's easier to figure out what page ID I need than the process ID - and that worked flawless.
So maybe you can use this more fine-grained caching mechanism in your application as well - but be warned: it's undocumented so it can change in a future version!
Another alternative solution would have been: enable caching of the page and programmatically reset it using the apex_util.clear_page_cache procedure.




Comments

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…