en-USnl-NL
Goal:
Let any anonimus guest on your portal sign-in for an event.

General:
There are two situations possible.
1: The guest has no subscription yet.
2: The guest has a subscription and wants to review it.
In the first situation the guest has to click the "New!" button to enter the registration page for the event selection.
In the second situation the guest needs his security code that he received by mail to select and enter his existing sign-in.

Execution:
Your guests will be presented with the Sign-In module screen.


Observe the "Register & Login" message in the upper part of the screen. This is a JumpStart standard message that is displayed when any user who is not regularly registered on your portal enters a page.

First situation 1: A Guest wants to sign-in for an event.
He has to click the "New!" button to get to the sign-in page.
 

As you can see there is a dropdownbox that contains the acivities that can be selected.
Further there are the normal personal data fields such as name, mail and home adress.
And there is the Clientid field that holds the security code for this event.
Notice that this field can not be edited. It will be filled by the application on Updating this screen.
 

The guest selects his event and fills in the rest of the required data.
Then clicks on "Update" to confirm his registration.



After the update the guest comes back on the sign-in page, where a message is presented that an e-mail is send to him for confirmation. 



Now situation 2: A Guest wants to review an event.
The guest has to enter his security code in the entrybox.


Then click the "GO!" button to retreive the sign-in record.


When the guest clicks the "Select" button he gets the "view" screen and when the guest clicks the "Edit" button on the far rightend of the record, he enters his sign-in data screen.

When the guest clicks the "Select" button he gets the "view" screen and when the guest clicks the "Edit" button on the far rightend of the record, he enters his sign-in data screen. The data in the "Edit" screen can be updated. When the guest clicks "Update" he will again receive a comfirmation e-mail.


 
   

Now, what happens when a guest want also to participate in another event, let's say Camping?
Well, it's simple: just click the "New!" button and select the "Camping" event in the dropbox. Enter the rest of the data and update the sign-in.
A new record will be generated in the activities table.

A remark on the security function.
By choosing a clever combination of SQL fields you will make it possible to show records in a table exactly as you want.
In this case the securitycode is build up from the zipcode and home number. It may be expected that when a guest signs in for a second (or even more) event(s), he will use the same zipcode and homenumber again, because these wont's change.
Because the SQL is build upon these two fieds the retreived records have the same Clientid. It's not unique.
In this way your guest will retreive all his event records al long as he uses the same zipcode and homenumber combination.



How would you create a truely unique security code per table record?
Answer: Add an unique SQL  field in the Clientid. This unique SQL field will typically the recordnumber. So when you add the _SB extention to the first recordfield in the DatabaseBuilder, you will get an unique security code for every table record.
Just type in _SB behind the ID in the cell D5 in the DatabaseBuilder.


This will force the ApplicationBuilder to insert the record-id in front of the security code. The SQL will now find only the record with this record-id in the security code.

You're done with this lesson.

---->> Lesson 16: PayPal integration