Could sombody give me a quick outline of how to set up a multi-part registration form. Basically what I want to do is allow the user to register with the basic credentials. I then want the user to have the option of an advanced registration with more questions to answer if they choose too.  I just started to use this product so I am still figuring it all out so cut me a little slack if this is really basic.

Thanks

William

William,

Hi. this isn't an easy question and even for questions when you have an answer right in front of you sometimes a quick 'how to' provides a better understanding. There are a few ways of handling this request so lets review some of the options...

The way to create multi page forms within both Dynamic Forms and Dynamic Registration is to use the feature within each field settings to 'Pass field via querystring' or 'Pass field via session variable'. In the 3.2 beta which we are working on there is also an option to pass fields via a cookie value. Then on the 2nd page you can setup a hidden field to 'Retrieve value from querystring' or 'Retreive values from session variable'. Just make sure that the short field name for both pages is set to the same.

With Dynamic Registration you might not even need this option though, just remember that in Dynamic Registration you MUST have a UserName, Password, and Confirm Password setup on the form for it to function properly. What you can do though is setup the initial form to include these fields and lets say a few others such as contact information, phone number, email address, etc... Then lets assume at the bottom of the registration page you can have a field such as 'Are you a Job Seeker or an Employer' with a dropdownlist or radio button with the two options. In this scenerio you could.

1. Setup the initial page as described above

2. Create a redirection completion event, specify that if the user chooses 'Job Seeker' you could redirect them to 'Page ABC' which will be another registration page you can setup specific for Job Seeker.

3. Create another redirection completion event, specify that if the user chooses 'Employer' you could redirect to 'Page XYZ'

4. Then you can go and specify seperate registration pages (as the 2nd page) for both the job seeker and the employer page. Remember for these pages you still have to setup a username, password, and confirm password field but under Module Configuration, DNN Core Integration, Advanced Integration options, you can enable the feature to 'Hide UserID for registration updates' and 'Hide Password for registration updates'. This is how you can achieve the ability to hide or not show the username and password fields for basically any other registration/profile page you would want. Keep in mind you can have as many as you would want.

A few other things to keep in mind...

You can setup as many 'extended field profile properties' within the core. This is under Admin, User Accounts, Manage Profile Properties. I would add one for each dynamic field you create within Dynamic Registration. This can be used as a 'central storage' area so that both Dynamic Registration can post/pull from these fields and also other 3rd party modules can also access them and not Dynamic Registration custom tables etc... After you setup these fields go into the advanced field settings and specify that the dynamic field 'links' to which core field. The advantage here? Lets say both Job Seeker and Employer had a 'Biography' field. You could add the field to both registration pages and have them both post/pull from the core BIO field if you had them linked properly. This also helps down the road as you might want to use fields and field data in other modules such as our Dynamic User Directory or other Dynamic Registration profile pages.

Another user recently setup a multiple page registration pages. You can find this on www.betasprings.com under John's E-Mail/Password only registration. This example demonstrates many features such as setting up multiple registration pages, using email and password only to initially set up the user, allow the user to change their username, allow the user on a seperate page to change their password, etc... You have to sign in or create an account before you can see the multiple pages. Also, you can sign in using username and password of host/dnnhost.

Hope you find all of this useful!

-Chad

Chad,

Fabulous answer and just what I was looking for. It sent me in the right direction and I think I got it.

Thanks,
William

Hi Chad,

As you mentioned in forum

"The way to create multi page forms within both Dynamic Forms and Dynamic Registration is to use the feature within each field settings to 'Pass field via querystring' or 'Pass field via session variable'".

My Question 1:

It seems that if we create multi page in Dynamic Registration then without coding we can move from one page to other. Is it correct or we need to modify the source code of Dynamic Registration?

My Question 2:

I have created two different page, First page is as below. In which I kept  four fields, I want to do on click  of "Update Registration" link, It should save data and move to  next  page. I have tried with "Registration Completion Events" but in "Select Event" link respective option is not display. Please let us know how I will redirect to other page.

As you can see below image "Update Registraion" link is not display in Combo.

So please help me to find out, what steps I need to follow to navigate from first page to second page, right now i am facing problem that page remain on first page if I click user Registration,.

Thanks,

Sandeep

Hi Chad

We are days away from a go live and both myself and my guys are struggling to get DR to play ball after many hours (days) . I have set up a demo on betasprings in the hope you can point us in the right direction. It's a 3 step registration:

1. Adams Multiple Registration  (DR Module which should redirect to ->)
2. Register Page 2 (DR Module  which should redirect to ->)
3. Thank You (Text / HTML)

This will only be used to sign up new users.

Identified problems:

1. If i turn on session variables for password/confirm password the 1st page does not redirect, not a big problem but just want to raise the fact these impact redirection.
2. Option A - turn session variables OFF for password/confirm password and just pass through the email and username in session then click update and you get through to page 2 but:
   1. trying to update this screen displays - "Your registration is not complete, please review the field validation and check and verify your username."  - Is there any way to have the second page take all the info and process the sign up?
   2. Note: "Do not sign user in after registration" = checked
3. Option B - as above but "Do not sign user in after registration" = unchecked you go through to page 2 but:
   1. On-click of Update Registration no redirection occurs to the 3 page - thank you
   2. A blank is displayed for the username in the skin token
4. Smaller issue - Setting the max password to 6 chars has no impact, validation still requires 7
5. Smaller issue - Test mode doesn't process redirections so you can't test a multi-page form

Are you able to suggest where we have gone wrong?

Thanks

Adam

Chad,

Thanks for the reply, ok all noted and understood. Regarding the required fields on point 3, yes we are well across this. 4 - it might be worth noting in the manual.

In hindsight i should have more throughly tested the basic capabilities of DR before committing to customise, although it did seem to behave as expected in the basic prelim testing we did. However i made the call last night to roll our own module and all going well that will be working tonight.

The other major drawback for what we are trying to achieve was inconstant validation messages for all fields such as check boxes so have used Peter Blum controls for this.

Anyway thanks for taking the time to investigate and i may switch back to using DR once it can be customised to the level we require.

One other thought with Test mode, if it simply processed all events such as validation, redirects and session variables and without registering users then you would have a better method of testing your forms from go to whoa and could use it as the step one as opposed to Dynamic Forms.

Adam

I have some questions regarding the querystring being sent a multipart on different pages.

So I have default questions on the first page and then I radio button going to different categories of user types.

When I go to a new page to lie transfer every question on that default page to the next page through that querystring.  Or what do I send to the page?

Now on the second page when the user hits the registration button can I tell which security role they will go into?

Also if I go back and one to upgrade a user from what say Basic User security role to let say Legislator security role.  Do I just un-hide some questions that go to a second page?  Is it possible to take that upgraded person all would of The Basic Registration security role add into the other?

For those second pages I just add the module to another page and everything will work fine?