What is the logic in the Application Builder

Question

Hi guys,
What is the logic in the application builder when creating e.g a Report. When we create a static report we go through these four steps:
<ul>
Display Attributes
Source
Report Attributes
Conditional Display </ul>
Starting from the "Source" step we can Click "Create Report", and create the report .....
is there a table for each step... or there is a collection for each step. So, when we click Create Button the collections are inserted into tables, then get emptied. ?????
In my case, i have three real-estate entities: landlords, properties, and marketing. it goes like this:
enter the landlord details, then click create to move to the next page to enter the property details, then click create to move to the next page to enter the marketing details.
i hope that my question is clear..
Best Regards,
Fateh

Answer 1

Fateh wrote:
Hi guys,
What is the logic in the application builder when creating e.g a Report. When we create a static report we go through these four steps:
<ul>
Display Attributes
Source
Report Attributes
Conditional Display </ul>
Starting from the "Source" step we can Click "Create Report", and create the report .....
is there a table for each step... or there is a collection for each step. So, when we click Create Button the collections are inserted into tables, then get emptied. ?????
In my case, i have three real-estate entities: landlords, properties, and marketing. it goes like this:
enter the landlord details, then click create to move to the next page to enter the property details, then click create to move to the next page to enter the marketing details.That would be called a "wizard" in APEX (as frequently used in the Application Builder as you say). There's a "Wizard wizard" as an option when creating a new page that enables you create and link the basic multiple page structure. Themes have "Wizard Progress List" (vertical orientation) and "Wizard Progress List, Horizontal Train" (horizontal) list templates that can be used as stage progress indicators. You have to construct the contents of each page using standard components. Once the "Wizard wizard" is completed there's nothing to indicate that the pages are logically related&mdash;strangely it doesn't even generate a wizard progress list for you.
Use Collections to store the data from intermediate stages before final processing if all of the data is captured in one session. If you want persistence across sessions (e.g. allowing users to enter information over several days) use separate drafting/staging tables instead of/in addition to collections to capture the data before final validation and promotion to the main tables.