Overview

If the instructional design determines that some content should not be delivered after certain conditions are met, the Content Developer has the ability to execute this request by use of Limit Conditions. Limit Conditions can be defined as conditions that specify when an activity will not be delivered. It is based on the activity’s tracking status information. When the conditions are met or exceeded, the activity becomes unavailable for delivery.

Attempt Limit

If the Instructional Designer has determined in the design that the learner will be able to attempt the content only a limited number of times, the Content Developer can implement that request by the use of the Limit Condition Attempt Limit element. This element sets a maximum number of attempts the learner may have on a given activity. If this element is not used, the learner will have unlimited attempts on the content.

There are two aspects to the Attempt Limit element. In the table below are descriptions of the aspects.

Note: Even though this table has two aspects, the Extensible Markup Language (XML) only has one. If a value for Attempt Limit is provided in the XML, the “control” value is True, otherwise it is False. A Content Developer should never be concerned with setting the “control” value, only the Attempt Limit.

Conclusion

The Instructional Designer and Content Developer have the opportunity to limit the number of times the learner can interact with content. By use of Limit Conditions, it is possible to set a maximum number of attempts the learner may have on content. The learning managment system (LMS) determines when the attempt on the activity begins.