I’m still studying Gibbon v17 and I came across what seems to be a little bug.
A new parent is filling a blank student application form accessing it from the login page.
Following this I’m then notified and go into Admissions> Manage Applications and accept the new student application.
Everything seems to go through nicely.
Then later I would like to review some data of the same application form and I can do this using Admissions> Manage Applications again and choose the accepted student application form and click the “Edit” icon.
Please have a look at the family section. It shows the family name without any additional info on adults and relationships.
This doesn’t look right to me.
I also wonder why it even shows this family section instead of the data that has actually been entered to do a more effective review.
Can you reproduce this?
You really have an eye for detail!
Interesting! First thing to note is that once the form has been accepted, there is little point editing it, as the information has already been copied into gibbonPerson, gibbonFamily, etc.
The behaviour you are seeing is what allows multiple applications to be attached to a single family, so that, when the second and subsequent siblings are accepted, you do not get multiple. As such, this is expected behaviour for an accepted form.
I came across this behavior by chance. Some parent data was missing in users and I wanted to check if the needed fields have been entered when the parent filled the form. I then saw the strange behavior in the family section.
The fix is not high on the priority list, I guess, or?
I actually don’t believe there is anything to fix: I believe you are seeing the expected behaviour, which is that once the form is accepted, and the family made, the form is linked to the new family.
@ross can you confirm that this is all as expected? You built this part, and I believe I’m correct, but you’d know better.
The application has a few different modes of acceptance: not logged in, logged in user (no family), and logged in user (with family). Along with this, there’s a sibling application tracker, which aims to connect related applications together so they’re added to the same family when accepted.
In each case, once the application is accepted the student, parent and family records are created and connected together, and the application is updated with the ID of the accounts that were created. This helps track the application and connect it to live data, as well as ensure future sibling applications are added to the same family.
It sounds like what you’re seeing is the end result of the connection between the application and the accounts created for it. As Ross mentioned, this is the expected behaviour. Perhaps to help clarify for users, we could add an alert that says “This application has already been accepted, the following accounts were created during acceptance:” above the section where you’re seeing the family name.
Thanks for this summary!
I’m going to have a closer look at this within the next days.
My wish is that the form shows what has actually been entered allowing some form of cross-check between the data created and data entered.
In my tests, this worked quite well but not always. Maybe this is wishful thinking. I don’t know yet.
I’ll get back to you on this…
I can see the use in doing this. One option, if this is your aim, is to use SQL to export the originally inputted values. You could do this using a MySQL client, or the Query Builder module. If you have a Gibbon Value Added License, then you can use the Applications By DOB query in Query Builder to export what you are looking for. Without the license you can still create your own query.