This feature is considered classic functionality and is not supported by Deployment Rules. For information on how applicants/registrants can view requirements on one page and be assigned process elements beyond questionnaires and signature documents, see the Deployment Rules article.
Submitting a OneStep Registration
To submit a OneStep Registration, the registrant must be provided with the link to the form, or they should be able to find an access button somewhere on your website. After initiating the registration process, the applicant will be prompted to login and then they will see a OneStep form that resembles the one below:
1. In the colored bar at the top of the OneStep form, the program name will appear.
2. The profile section will display the user's name, email address and field for a cc email address.
3. The information panel will display applicant parameters that were configured for the OneStep form. Internal applicants will not see any SIS-mapped parameters, even if those are configured to be viewable. Only external applicants will see those and be able to edit the information. Any applicant parameters that are required, will be required for the OneStep.
4. Addresses configured for the OneStep are displayed next. SIS-mapped addresses and non-SIS-mapped addresses will display to both integrated and non-integrated users. SIS-mapped addresses will not be editable by integrated users, but will be editable by non-integrated users. Any address that is 'required' will inherit that setting and be required by non-integrated users for the OneStep form.
5. The itinerary panel will appear automatically when using a OneStep form. The user will be prompted to select a location and corresponding travel dates. Then they will click the 'Add to itinerary' button and their itinerary will be built at the top of the panel. Users can enter distinct travel locations and dates, building each leg of their trip. If the location they are looking for is not in the pre-populated list, they will be able to search for that location and add it to the list.
6. Any questionnaires that are configured to apply to the pre-decision phase for the program that is utilizing the OneStep form will appear here. The questionnaires should be deployed in the process map for this app cycle and apply to the term that the OneStep uses.
7. The final part of the OneStep form is the area for signature documents. Any signature document that is configured to apply to the pre-decision phase for the program that is utilizing the OneStep form will appear here. The signature document(s) should be deployed in the process map for this app cycle and apply to the term that the OneStep uses. The registrant will be required to click the 'I agree' box before submitting the OneStep registration. Important note: Identity verification does not apply to signature documents deployed through OneStep forms. This means that an external user under the age of 18 would be permitted to sign the document even if the "Require verification and 18 years of age for signature docs" setting has been enabled in Settings > System Features > Process Options.
2. The profile section will display the user's name, email address and field for a cc email address.
3. The information panel will display applicant parameters that were configured for the OneStep form. Internal applicants will not see any SIS-mapped parameters, even if those are configured to be viewable. Only external applicants will see those and be able to edit the information. Any applicant parameters that are required, will be required for the OneStep.
4. Addresses configured for the OneStep are displayed next. SIS-mapped addresses and non-SIS-mapped addresses will display to both integrated and non-integrated users. SIS-mapped addresses will not be editable by integrated users, but will be editable by non-integrated users. Any address that is 'required' will inherit that setting and be required by non-integrated users for the OneStep form.
5. The itinerary panel will appear automatically when using a OneStep form. The user will be prompted to select a location and corresponding travel dates. Then they will click the 'Add to itinerary' button and their itinerary will be built at the top of the panel. Users can enter distinct travel locations and dates, building each leg of their trip. If the location they are looking for is not in the pre-populated list, they will be able to search for that location and add it to the list.
6. Any questionnaires that are configured to apply to the pre-decision phase for the program that is utilizing the OneStep form will appear here. The questionnaires should be deployed in the process map for this app cycle and apply to the term that the OneStep uses.
7. The final part of the OneStep form is the area for signature documents. Any signature document that is configured to apply to the pre-decision phase for the program that is utilizing the OneStep form will appear here. The signature document(s) should be deployed in the process map for this app cycle and apply to the term that the OneStep uses. The registrant will be required to click the 'I agree' box before submitting the OneStep registration. Important note: Identity verification does not apply to signature documents deployed through OneStep forms. This means that an external user under the age of 18 would be permitted to sign the document even if the "Require verification and 18 years of age for signature docs" setting has been enabled in Settings > System Features > Process Options.
After submitting the OneStep registration
After submitting the OneStep registration, the user will see the following confirmation pop up window:
Then, based on how you have configured the OneStep registration, they will either be logged out of the system and land on your site's homepage, or they will be routed to their applicant homepage. The user will immediately receive a confirmation email with their itinerary details.
From the admin perspective, the registrant will have one distinct application on file for each leg of their journey. In the example above, the traveler has two destinations and will therefore have two 'applications' after submitting this form. This makes it possible for the locator search to always know their current location.