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.




Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

It's happening again ... running for the ODTUG Board of Directors 😉

For the third time in a row I'll be running for ODTUG's Board of Directors. But after ending as a runner up twice, I am sure I'm going to make it this time! But not without your help!

My campaign statement this year is:
I have been attending and presenting at Kscope conferences since 2007. This not only resulted in a vast amount of knowledge, but also - and even more important - a huge number of friends from all over the globe.  I want to see ODTUG grow and spread this community feeling even more! 
My experience as an attendee, presenter and content lead has provided the basic foundation to be a director. Next to that, my personality and (global) network will be beneficial to the whole board and organization. 
Since March I have served on the Board of Directors in a limited term for a Director who stepped down due to a career change. This has allowed me to have unique insight of all the things that are going on in and around the ODTUG organization. As the train was already ro…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…