§
http:// – the protocol, can be http or https
§
apex.oracle.com – your domain/host/server, whatever you
want to call it. Can also be localhost.
§
/pls – indicates that you are using Oracle
HTTP Server with mod_plsql. If you are using APEX Listener or Embedded PL/SQL
Gateway this part is obsolete/missing.
§
/apex – the entry from your dads.conf file
(this a file on your application-server or EPG where the target database is
configured) – in case of EPG its just one entry pointing to localhost, in case
of an OAS you can have multiple entries, each pointing to an other database
§
/f?p= – procedure “f” is called and parameter
“p” is set to the complete rest of the string. Remember: APEX uses mod_plsql.
“f” is a public procedure, this is the main entrypoint for APEX. Or you could
say: “f” is APEX.
§
AppId – the number or the Alias of the Application
§
:PageId – the number or the Alias of the Page
§
:Session – unique Session ID, can be 0 for Public Pages or empty (then
APEX creates a new Session)
§
:Request – a Request Keyword. This is basically
free text, just a string you can specify to react in a process or region
condition on. e.g. you could pass the keyword “CREATE” and have a condition on
the delete button of your page saying “dont’t display this button if request is
CREATE”.
In other words: use the REQUEST to control the behaviour of your page.
When pressing a button, the button sets the REQUEST to the button-value (e.g.
SAVE), so that you can control the processes in the page processing (Submit)
phase.
§
:Debug – set to YES (uppercase!) switches on
the Debug-Mode which renders debug-messages and timestamps in your Browser
window. This helps to detect wrong behaviour of your page or performance issues
and everything else. Every other value then YES turns the Debug-Mode off
§
:ClearCache – you can put a page id or a list of
page ids here (comma-separated) to clear the cache for these pages (set session
state to null, …). But there is more: RP resets the pagination of reports on
the page(s), a collection name deletes the collection, APP clears all pages and
application-items, SESSION does the same as APP but for all applications the
session-id has been used in.
§
:Parameters – comma seperated list of page-item
names. Good practice is to set only those page-items which are on the page you
are going to. Accepts page-items as well as application-items.
§
:ParamValues – comma separated list of values. Each
value is assigned to the corresponding Parameter provided in ParamNameList
(first value assigned to first parameter, second value assigned to second
parameter, and so on…).
The trick here is not having values which contain either a comma “,” or a colon
“:”. Both would lead to side-effects and errors, as APEX gets confused when
parsing the URL. Using a comma works, if enclosed by slashes: e.g. \123,89\.
§
:PrinterFriendly – set to YES (uppercase!) switches the
page into PrinterFriendly-Mode, uses the Printerfriendly template to render the
Page. You can also hide regions or other elements in PrinterFriendly-Mode using
the PRINTER_FRIENDLY variable in a condition.
Download PDF
.png)
