I'm in the process of mocking / designing an application form that consists of many regions that will be broken out across 5 pages (I'm intentionally not using the APEX Wizard Component due to personal choice and given requirements). So I will need to store/persist all the pages' information temporarily, while user fills out the form and reviews and saves the application form on the last page.
Based on a response to a previous question, it seems that apex_collections are the preferred way to do this versus using the values already in session state to persist the information during the session. I've spent a bit of time breaking the application form into logical groups of data that can be mapped to about 8 collections.
Questions:
Is this a correct assumption (using collections vs session state)?
Are there any performance considerations to think of when using APEX_COLLECTIONS?
How is it best to handle both the values in session state along with the the collections? Assuming you utilize the session state values to populate the page items on their associated page's regions, but use the collections for the last page when you save? So you are kind of maintaining the data twice, right?