All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.

• Requirements
• RMS Server version 3.3 or later.
• CollegeNET API version 1.8 or later.
• Features
• Initial Release
• Known Issues
• Recurring event instances in R25 are handled as individual appointment reservations in RMS.
• RMS does not obtain the organizer email address from R25 events and thus cannot deliver email notifications to the R25 event organizer.
• When events reservations are modified in R25, R25 internally creates new reservation booking records with new events reservation identifiers, thus RMS detects these as new event reservations and then deletes the previous event reservation from the RMS database. Consequently, this also deletes any RMS associated data configured on the previous event reservation record.
• Reservations that are Ended or Extended from the RMS touch panel are handled as modified R25 events and thus exhibits the same behavior as outline in #3 above.
• R25 does not support modifying start and end times on individual recurring event instances, thus RMS cannot extend or end recurring event instances.
• R25 does not support modifying start and end times on event that contain multiple reservations, thus RMS cannot extend or end multiple reservation event instances.