Understanding Page ID, Page Loading, and Page Caching Properties
This topic describes the following layout page properties:
Page ID.
Page Loading.
Page Caching.
Page ID
A page ID uniquely defines a page in a layout and is included in the URL for the page.
In addition, depending on your requirements you may need to reference the page ID as you develop PeopleCode, JavaScript, jQuery events and Ajax events for your application pages.
The system sequentially assigns a default page ID to all pages, assigning the default page ID value of the first page in a layout page1, the second page in the layout being page2, and so on.
You can change the default page ID value, however you are responsible for ensuring that page IDs remain unique throughout a layout, as the system does not perform page ID validation.
If you change the default page ID when a page is defined as an internal page, a warning message appears to alert you that changing the ID may invalidate URLs/links to the page from other pages in the layout. If you have created links to a page and later change the page ID, navigate to the page or pages that have button elements that call the URL, access the button properties and rebuild the links using the new page ID.
Page Loading and Caching
The Mobile Application Platform framework provides several page properties to assist with memory management.
|
Field or Control |
Definition |
|---|---|
| Page Pre-Load |
The framework provides a cache pre-load option that allows you to specify that any external pages referenced on a page to be cached even before they a users links to the pages and before they are displayed in the browser. Each pre-loaded page creates additional HTTP requests, and there for uses more bandwidth. Therefore, it is important to use the pre-load option only when you think visitors are likely to view the page. |
| Page Caching |
The framework provides an option to cache pages in the Document Object Model (DOM) using the jQuery framework, instead of browser caching. |