Simply put, in your database, a Problem must have some sort of relationship to a Solution (or perhaps even a list of Solutions) that answer/solve that particular Problem. In this way, you can (regardless of the user interface you come up with) match a Problem with its Solution.
There are many many different ways you might structure these objects, depending upon what this feature you’re building is.
Regardless, I’d recommend creating a Problem as its own datatype and, at a minimum, it would look like this:
Note that once I built the index page, I just cloned that and added a couple of features to make an “Admin” type page. Note that in a real deployment, such a page would only be for logged in Users who are Administrators, of course.
Thanks so much for showing me this, it’s really helpful.
Can I check my understanding of the 2nd & 3rd workflows?
I’m trying to wrap my head around the sentence below, particularly the use of ‘Selected’ state:
The trigger says, “Only when RepeatingGroups Problem’s Selected is [not] Current cell’s Problem”
I see that the ‘Selected’ state for the RG basically has ‘Problem’ as its type. I’m not sure what this really means and how it actually links with the event?
I’m a bit confused about States in general.
Transitions
I can’t figure out how you got the group to auto expand and do so with a gradual movement?