en-USnl-NL
Goal:
Handling the registration of non-registered anonymus portal guests.
As stated in the case description: "A member is not necessarily registered in your portal, but they can see the activities that are planned." There has to be a mechanism to handle guest users of the application.
(see: Tutorial)

General:
Normally a guest user of DotNetNuke portals can only view certain pages. They rarely are able to modyfy any information that is stored in the database. For that they have to register in the portal and the webmaster have to grant them the rights to do anything an a database.
But in this case we want to let any guestuser to be able to sign-in on an event, even when there is no portal registration. Therefore we have to get past the standard DNN safety measures to circumvent the registration that normally is required for users to handle any data in the portal database.

In this special case we also need to inform the guest about the status of his sign-in on a perticular event he wants to attend.
So when the guest has choosen the event and filled in his personal data and the number of attendee's, he must be informed because the event registration is personal, and therefore invisible for any other portal guest.
The registration will get a code attatched to is that will serve as the sectert entrycode for this guest. This code will be mailed to the guest user's mailadress.

Execution:
Step 1:
Determine the construction of the secure entry code for every event registration.
Building this securitycode is in essence the contraction of SQL datafields that exist in the table record.
For this code we will use two fields: the zip-code and the house number and put the result in a SQL dtatafield that has to be present in the datarecord as well.
These are the fieldnames: ZipCode, Number and Clientid.


These are the fieldextentions:
_KEY to determine the securty field and _ZKN to hold the combination of the codefields that are involved; in this case ZipCode and Number.
_ZKN to determine the SQL field that has to hold the combined codefields.
_SB to determine the building SQL fields that have to go into the security field.

So the SQL field Clientid has two extentions that work together: the _KEY and the _ZKN extention. The combination of these two extentions will trigger the ApplicationBuilder to generate code that will handle the anonimus guest sign-in.

Step 2:
Determine the recordfields that have to deliver the content that you want to show in the confirmation mail.
Now we have to assure that the portal guest gets his sign-in notification in hies mailbox.
This is the SQL field to use: MAdress.


These are the extentions to use:
_MAIL to determine the guest user's mailadress.
_MPM to determine the SQL fieldnames that are needed to place the guest's data and security code in the response mail.

That's it!

You're done with this lesson.


Continue on: Anonimus GuestUser Mailing
Continue on: Anonimus GuestUser Sign-in



---->> Lesson 16: PayPal integration