You can put release conditions on the following items; Checklist, Resources modules and topics, Custom widgets, Discussion forums and topics, Assignment folders, Grade items and categories, News items, Quizzes and Surveys.
Note: Wherever you can see the Restrictions tab, you can create and apply a release condition.
Once a student meets a release condition, the condition is cleared for that student and cannot be reset. For example, you attach a release condition to a discussion topic requiring student to achieve more than 60% on a quiz before they can access that topic; one of your participants receives 72% on the quiz but you adjust their grade to 55%. The students will be able to access the topic because they met the requirement at some point.
Best practices for creating release conditions
Create all of your unit materials and set up your release conditions before the unit opens to students. This gives you a chance to check for mistakes in the conditions or for circular, contradictory or unnecessary conditions. If you add new release conditions after users have accessed the unit, students might be confused by resources disappearing. Since conditions cannot be reset, you also risk having students meet conditions before your resources are ready (e.g. accessing a topic before it is finished).
Scenario 1: Release tools or resources to student of a particular enrolment type
You can target the delivery of resources or a tool to students according to their enrolment.
Scenario 2: Use a checklist to organise activities
Create a checklist that lists the activities students should complete throughout the unit. For example, a checklist for the first week might include reading the unit’s introductory, posting a message to an introductory discussion topic, and submitting a list of learning goals to an assignment folder. You can set release conditions based on users checking off items from their checklist. For example, you might release a news item on your unit’s homepage once users check off that they have completed the first week’s activities.
Scenario 3: Release topics in stages
Reveal topics to students only after they have read prior topic by attaching release conditions on the later topics or modules that require users to view earlier topics. This can provide a clear path through the material and prevent students from becoming overwhelmed by a large list of resources at the start of the unit.
Scenario 4: Customise resources for groups within a unit
Create separate topics or modules for each project and attach release conditions based on group enrolment, particularly if your unit has group projects and you want to provide different instructions or resources for each group. Group members working on a project will see materials related to their work, without being distracted by unrelated materials.
Scenario 5: Restrict access to assessments based on performance
Put a release condition on a assignment folder which restricts students from submitting part 2 of a project until they have a passing grade on part 1 or until they have read your feedback on part 1.
Scenario 6: Using the NOT release conditions in Intelligent Agents and News item
On top of the existing release conditions, you can use the NOT operator in:
- Not completed checklist, checklist item
- Not achieved competency, learning objective
- Not visited content topic
- Not threads added/replies to topic/forum
- Not submitted assignment
- Not grade item
- Not completed quizzes
- Not completed survey
The Unit Chair can setup an Intelligent Agents to send emails to students who:
- did not submit an assignment
- did not post to a certain topics in Discussions
- did not view a certain topic in Resources.
The Unit Chair can setup news item that only release to students who:
- did not view a certain topic in Resources
- have completed a quiz but did not view the related topic in Resources.