< Previous | Contents | Next >
A content developer can define limit conditions that describe conditions under which an activity is not allowed to be delivered. Limit conditions can be associated with activities and are conditional based on an activity’s tracking status information (refer to Section 4.2: Tracking Model). When a limit condition is met or exceeded, the activity becomes unavailable for delivery.
SCORM only requires the support for the Limit Condition Attempt Limit element. SCORM does not require the evaluation of any time-based limit conditions. Therefore, LMSs are not required to manage data for or honor the evaluation of any of the optional portions of the Limit Conditions Check Process (refer to Appendix C: UP.1).