Jump to Section:
Frequently Asked Questions
Module Setup Checklist
Payment Configuration
Password Management
Email Content
Instructor Biographies
Filters and Packages
Data and Reporting
Administrative How-To Guide
It's possible to set overall registration to be limited to a certain time period by controlling the visibility of the INNO Apparatus module.
These are forms for participants and their guardians to complete and submit or bring when attending, such as waivers and questionnaires.
Exercise caution when removing files - this action cannot be undone!
To view reports, go to the page with the INNO Apparatus Manager module, and click the Reports tab.
There are a few different ways the membership number can be retrieved.
Note: Passwords are encrypted for security. For this reason, a user's password may never be retrieved! Instead, a password may be reset, either by the user or by an administrator. Additional information is available in the Password Management documentation.
Categories can be used for single-tier or dual-tier program sorting.
It's possible to set support information that is visible to all site visitors, logged in or not. This information is maintained on the profile of the user account set as the Site Administrator / Primary Administrator.
At this time, only administrators can reprint or resend a receipt.
Users can submit feedback on Step 4 of the registration and checkout process. This information is available for review in the Transactions tab.
It's possible to edit various texts on the Apparatus modules by editing the resource files. The editing process is very similar to that of the email content update process - click here for instructions.
This is a basic blueprint for how to configure Apparatus event and management modules on your DotNetNuke 9 website.
Click here to jump to instructions on how to load and modify resource file values. For email templates values you will want to select the 'Email_Templates' or 'InnoRegistration' file.
Important! Caution should be taken when modifying resource files! Back up the file content before making changes.
Click here to jump to instructions on how to load and modify resource file values. For site text values you will want to select the 'InnoApparatus' file.
Methods for users and administrators to reset account passwords.
All users can reset the password from the Login page.
The Apparatus Profile module has a Change Password section. All logged-in users can browse to the Profile page and reset the password here.
When possible, all users should update their account password using one of the self-service methods described above. When these methods fail, administrators may use one of the methods described below to force a password change on behalf of a user.
How and Where to Modify Emails
Each email body and subject line are a different resource name.
This solution is geared for those who are familiar with using resource (*.resx) files.
Use these placeholders to provide variable details such as membership numbers and addresses.
How to Set Up Stripe and Receive Stripe or Paypal Payments
How to Configure Filters for Program Packages (Multiple Selection)
Filters can be used to create packages of programs. For example, to require the enrollment in two or more programs from a collection to create a package deal. Simple (non-package) filters can also be created.
When a program has a filter applied, the item count will be validated before the user can proceed with checkout. If the shopping cart doesn't contain the correct quantity of a program with a package filter applied, the checkout process will not proceed until this is corrected.
How to Set Up Instructors and Link to Instructors in Programs
Existing instructor entries can be edited by clicking the pencil icon next to the name in the list.
Note: Only one instructor can be selected per program.
Tips and best practices for reporting on program data
IMPORTANT: Reports are generated from LIVE data! It's prudent to save copies of transaction and participant reports for programs before any changes are made to the program, because changing program details will change the report data. For example, changing the price of a program will update the price in newly-generated reports for past transactions, which could cause users to appear to have paid an incorrect price for the program.
Ideally, reports should be saved in a secure location on a regular basis for record-keepting purposes. The issue may also be circumvented by creating a new program when program details change - for example, creating a separate program at each price point to differentiate report data for those price points.