User Onboarding feature design question

[solid wren]

Writing a java/spring/jsp webapp.

I'm asking the user to give me about 3 forms worth of information before finally persisting their account information on the 4th form and associating it w/ the records created on forms 1-3. something like this:

• page 1: forms for details of their request
• page 2: further additional detail (based on input from p1)
• page 3: supporting documentation
• page 4: finalize account creation

Creating a 'request object' (this is what i call the instance of the class that represents the user data) on page 1 and sending it to the subsequent forms but I need a way to make sure another user can not either by accident or ill intent get to another user's data before the account association has taken place.

My current plan is to associate ip and web session data w/ forms 1-3 until the user completes the process and I have an actual account to associate their data with. Is this foolish?

[neon glacier]

<@&1004656351647117403> please have a look, thanks.

[neon glacier]

While you are waiting for getting help, here are some tips to improve your experience:

Code is much easier to read if posted with syntax highlighting and proper formatting.

If nobody is calling back, that usually means that your question was not well asked and hence nobody feels confident enough answering. Try to use your time to elaborate, provide details, context, more code, examples and maybe some screenshots. With enough info, someone knows the answer for sure.

Don't forget to close your thread using the command </help-thread close:1027500463647621170> when your question has been answered, thanks.