We want to build a case life cycle that is non-linear.
Consider an app that would let you design a car online.
From scratch, the user would select the car first and then in any order, select paint color, or select tires, or select interior, etc. then the user can come back to the car overview.
From an existing car the user already has or started earlier, they can perform the same actions to add/update options.
Once changes/additions are made, the user would continue to a review, then purchase steps.
Should there be a parent case with different child cases like Change Paint, Change Wheels, etc.?
How would the Stage,Processes,Steps be designed so user could jump around?
Thanks for your response. Yes, we will need ability to break down the actions taken during the process, so using child cases for that reason makes sense.
But we are also struggling with how to build the case life cycle, and how to navigate the user as they "jump around". E.g. temporary cases, alternate stages, optional processes/steps, etc. .. And how can we send a user from one of these child cases back to proper stage in the parent case?