This functionality is available to districts who have purchased Online Registration as an add-on service. For more information, contact the appropriate Client Relationship Manager.
This document provides an overview of the changes coming in the Online Registration version 6.0 update, coming Fall/Winter 2021. Currently, the update is available for Beta users only.
System Configuration by Year
The largest change with Online Registration version 6.0 is that most system configuration is now done per year, instead of global configurations.
- Years are now referred to as Configurations in the UI.
- New configurations are created by copying an existing configuration.
- There is a maximum of one configuration per year at this time.
- The year on applications cannot be modified anymore, as all configuration information is tied to the year.
Schema Changes
Action Required
Modify queries to reflect the following schema changes to avoid broken queries.
Numerous schema changes were made to represent configurations and to standardize the OLR schema.
- Views in the OLR schema; i.e., [olr].v_api_student, with names starting with v_api_ were created to make querying data easier. We can support these long term much easier than direct table access; so, please use them when writing queries. If you have feedback on these views or feel there is other data you need to be made available in them, please let us know. These exist in OLR 5.3; so, be sure to update any queries or reports before moving to 6.0.
- Data that could be assumed to be unique previously may not be unique anymore. Specifically, many config tables now require unique values per config, not globally.
- Olr_application no longer has an endYear column. You will need to join to olr_configGroup on olr_configGroupID and use the endYear on olr_configGroup.
- Many nullable columns are no longer nullable. This is mostly bit fields enforcing 0/1 as the only values instead of allowing null/0/1.
- Many unused columns were removed.
- Many foreign key constraints were added to both enforce better data integrity and to make figuring relationships out easier.
- A number of columns that were referencing olr_personID, but were not named olr_personID (usually olr_studentPersonID or olr_parentPersonID) were renamed to olr_personID and now have the above mentioned constraints.
- For the table dbo.olr_person, the calendarID and enrollmentID columns are now called qualificationCalendarID and qualificationEnrollmentID to better denote their meaning.
- Lots of data that was stored in the olr_studentOther table and olr_parentOther table was moved to olr_customStudentSave and olr_customParentSave.
Customizations No Longer Supported
Action Required
Remove customizations prior to taking the version 6.0 update if possible. Customization issues display as warning messages in the OLR Information Center.
Customizations are no longer supported. This includes changes provided by Campus in the past. This does not include anything you are able to build via the UI. We have reached out to all districts we believe this applies to. Many customizations can be recreated using the existing OLR toolset.
New UI
Many of the Online Registration administrative tools have been updated with the new look and feel of Campus. See the Online Registration Overview and Tool Rights document for a list of all tools available in the Online Registration toolset.
Workflow and Literals Changes
Suggested: review literals after taking the update. See the OLR Literals Bank documentation for additional information. Multiple literals have been added and may require translation.
The initial user flow for email applications, kiosk applications, and portal applications has been updated.
Literals in the updated areas are more restrictive about valid HTML. Only valid HTML is allowed. Script tags, style attributes, and anything the angular framework feels is unsafe are not allowed.
