Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Application Express 3.2 - The Essentials and More

You're reading from   Oracle Application Express 3.2 - The Essentials and More Develop Native Oracle database-centric web applications quickly and easily with Oracle APEX

Arrow left icon
Product type Paperback
Published in Jun 2010
Publisher Packt
ISBN-13 9781847194527
Length 644 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (30) Chapters Close

Oracle Application Express 3.2
Credits
About the Authors
About the Reviewers
1. Preface
1. An Introduction to APEX FREE CHAPTER 2. What we need to know to effectively use APEX 3. APEX Basic Concepts 4. The Application Builder Basic Concepts and Building Blocks 5. APEX Items 6. APEX Buttons 7. APEX Computations 8. APEX Validations 9. APEX Processes 10. APEX Branches 11. APEX SQL Workshop 12. APEX Forms 13. APEX Reports 14. Tabular Forms 15. Calendars 16. Interactive Reports 17. AJAX with APEX 18. Globalization and Localization With APEX Applications 19. Right-To-Left Support in APEX 20. Deploying APEX Applications 21. The APEX Runtime Environment 22. Security 23. Application Conversion 24. APEX Best Practices APEX Installation, Upgrade, and Configuration Tips

On Demand processes


As we saw in this chapter, APEX supports on-demand processes at the application and page levels. We saw that we could invoke an on-demand Application Process by using a page level On Demand process. However, there are two more options we can use to invoke on-demand processes.

The first option is to use the f?p URL syntax. We can use the keyword APPLICATION_PROCESS= in the fourth segment (the REQUEST segment) to invoke an on-demand process. The keyword value can be the application process ID or name. As the process ID might change when we deploy the application into a new APEX instance, it seems safer and simpler to use the process name (just remember that the name is case-sensitive). For example, the following will invoke an on-demand application process called check_status:

f?p=&APP_ID.:2:&SESSION.:APPLICATION_PROCESS=check_status

In this case, the page number is meaningless but still mandatory. If, for any reason, the check_status process does not end successfully...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image