Closed frankduncan closed 6 years ago
Alright, I've revamped this and I believe it's in line with what you're thinking. I decided against the code generation from data path because the code got too complex and error prone, and just went with a simple database table for the codes.
This adds an entry point to the intake/impact surveys without logging in. To do this, it creates an effectively unique id based on the name of the person, the session, and a salt. This was chosen over maintaining a GUID list somewhere in the database for ease of development and maintenance.
Test by logging in, going to a program with someone who doesn't have an intake or impact survey, and clicking on the link next to the lack of survey. Then log out and refresh link. Enter survey, and link should no longer work.
Merge against 220 because these were done in order to save rebase time for testing purposes.