Closed dcs619 closed 9 years ago
Per @benwiley the code changes every time. Closing.
@dcs619 What would it take for it not to change? This may be an issue KidSpring really wants to investigate
This would require a rewrite of Workflow/Action/Checkin/SaveAttendance
@dcs619 I concur... do you want me to rewrite it?
This will be determined by how we handle checkout. The code should change if they checkout and then in again.
Researched, it is possible and require rewriting SaveAttendance but core team raised a security issue on SocialCast. They would not want the option in core.
"For example, if you had a custody situation where only one parent was allowed to pick up the child, you wouldn't want any other check-in to use the same code."
Resolution: For now we will depend on the Checked In display to fix mistakes. KidSpring will have to update their process when a parent loses their tag.
If the attendance code DOESN'T change, that benefits us since it is how F1 works now.