Release conditions allow you to create a custom learning path through the materials in your course. When you attach a release condition to an item, users cannot see that item until they meet the associated condition. For example, you could attach a release condition to the second topic in your course’s content area that would hide that topic until users viewed the topic before it. Or you could create a condition that required users to view a content topic before gaining access to a quiz, or one that required them to post to a discussion topic before they could see a content module.
If you attach multiple conditions to an item, users must meet all conditions before they can access the item. For example, you could require users to visit the first three content topics in a unit before gaining access to an associated quiz.
Note: Once a user meets a release condition, the condition is cleared for that user and cannot be reset. For example, if you attach a release condition to a discussion topic requiring users to achieve more than 60% on a quiz before they can access that topic, and one of your participants receives 72% on the quiz but you adjust their grade to 55% they will be able to access the topic because they did meet the requirement at some point
Requirements
To see and use release conditions, you must have the required permissions in the associated tools applied to your role. These permissions can only be accessed by your organization administrator.
Tools that support release conditions
You can access release conditions for any of the following course items:
- Awards
- Checklist
- Content modules and topics
- Custom widgets
- Discussion forums and topics
- Assignments
- Grade items and categories
- Intelligent Agents
- Announcements items
- Quizzes
- Surveys
Best practices for creating release conditions
The following are the best practices for setting up release conditions:
- Set up conditions before users access the course: Create all of your course materials and set up your release conditions before the course opens to users. 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 course, users might be confused by resources disappearing. Since conditions cannot be reset, you also risk having users meet conditions before your resources are ready (for example, accessing a content topic before it is finished).
- Avoid unnecessary conditions: Each condition you associate with a tool takes additional time for Brightspace to process. Using as few conditions as possible to set up a learning path minimizes the amount of time that users spend waiting for pages to load. For example, you set up a content topic, a quiz, and an assignment for the second week of class. You want users to read the topic before taking the quiz, and you want them to read the topic and attempt the quiz before submitting the week’s work to the assignment. For the assignment, you only need to attach the condition that users attempt the quiz. Since users must read the content topic before they can take the quiz, it is not necessary to add this condition to the assignment.
- Avoid circular references: A circular reference makes it impossible for users to satisfy a set of conditions. For example, if you set the condition that users must view a content topic before they can access an assignment, and then set a condition that they must submit a file to the assignment before they can access the content topic, you have a circular reference. Users can’t satisfy either condition without satisfying the other one first. Circular references are more likely to occur with long chains of conditions. For example, a content topic that depends on a quiz that depends on an assignment that depends on a checklist that depends on the content topic.
- Avoid impossible conditions: Ensure that your conditions are not impossible for users to satisfy. For example, a condition that users must achieve greater than 100% on a grade item would be impossible (unless the grade item is set to Can Exceed). If users are unable to satisfy a condition, they are unable to access the content or tools to which the condition is attached.
- Avoid contradictory conditions: Contradictory conditions occur when two or more conditions that cancel each other out are associated with an item. For example, the conditions User must achieve greater than 49.9% on Grade Item 1 and User must achieve less than 50% on Grade Item 1 are contradictory. Users cannot satisfy both conditions at the same time; they would not be able to see the item associated with these conditions.
- Release content based on learning ability and course performance: Include additional content in your course specifically for users who need extra help and release this content to users who score below a specified threshold on a quiz or grade item. Alternately, release a special survey to users who attain a high score.
- Release content in stages: To reveal content topics to users only after they have read prior content, attach release conditions on the subsequent topics or modules that require users to view earlier topics. This can provide a clear path through the material and prevent users from becoming overwhelmed by a large table of contents at the start of the course.
- Release content based on enrollment date: If your course has rolling enrollment, you can set course materials and assessments to become available relative to a users' enrollment date. This allows you to provide a structured path through the course for every user regardless of their enrollment date. For learners who have been enrolled more than once in the course, you can choose whether you use the first time or the last time they were enrolled.
- Customize content for groups within a course: If your course has group projects and you want to provide different instructions or resources for each group, you can create separate content topics or modules for each project and attach release conditions based on group enrollment. Group members working on one project will see content related to their work without being distracted by content not relevant to them.
- Use a checklist to organize activities: You can create a checklist that lists the activities users should complete throughout the course. For example, a checklist for the first week might include reading the course’s introductory content, posting to an introductory discussion topic, and submitting a list of learning goals to assignment. You can set release conditions based on users checking off items from their checklist. For example, you might release an Announcements item on your course’s homepage once users check off that they have completed the first week’s activities.
- Use intelligent agents to monitor user activity or non-activity: You can set up intelligent agents with release conditions using the not operator to intervene with students who have not completed course work. For example, create an intelligent agent that sends a reminder email to users who have not yet completed a quiz attempt or submitted an assignment to an assignment.
Release condition types
Condition Type |
Description |
---|---|
Awards - Awards |
The user must have earned a specific award in order to fulfill the release condition |
Checklist - Completed checklist |
The user must complete all items on the selected checklist in order to fulfill the release condition |
Checklist - Incomplete checklist |
The user must not complete one or more items on the selected checklist in order to fulfill the release condition |
Checklist - Completed checklist item |
The user must complete a specific item on the selected checklist in order to fulfill the release condition |
Checklist - Incomplete checklist item |
The user must not complete the specific item on the selected checklist to fulfill the release condition |
Classlist - Group enrollment |
The user must be enrolled in a specific group in order to fulfill the release condition |
Classlist - Org unit enrollment |
The user must be enrolled in a specific org unit in order to fulfill the release condition |
Classlist - Section enrollment |
The user must be enrolled in a specific section in order to fulfill the release condition |
Classlist - Role in current org unit |
The user must either:
in order to fulfill the release condition |
Classlist - Date of enrollment in current org unit |
The user must be enrolled in the current org unit for a specified number of days in order to fulfill the release condition. The release condition includes the following options:
|
Competencies - Competency achieved |
The user must complete a specific competency in order to fulfill the release condition |
Competencies - Competency not yet achieved |
The user must not complete a specific competency in order to fulfill the release condition |
Competencies - Learning objective achieved |
The user must complete a specific learning objective in order to fulfill the release condition |
Competencies - Learning objective not yet achieved |
The user must not complete a specific learning objective in order to fulfill the release conditions |
Competencies - Score on associated rubric |
The user must achieve a specified Score and Threshold level on a learning objective, based on an associated rubric, in order to fulfill the release condition |
Content - visited content topic |
The user must visit a specific content topic in order to fulfill the release condition |
Content - Not visited content topic |
The user must not visit the specified content topic in order to fulfill the release condition. Depending on your organization's security configurations, especially if the d2l.Tools.ManageFiles.UseContentRestrictedSecurity configuration variable is set to ON, users may not be able to access specified content topics at all when this release condition is set |
Content - Visited all content topics |
The user must visit all content topics in the course offering in order to fulfill the release condition |
Content - Completed content topic |
The user completes a content topic. The method of completing the topic depends on the type, such as viewing a file or submitting an assignment. This release condition ignores exemptions, meaning that if the learner completes the activity, the release condition can be met, regardless of the activity being required, optional, or exempt. |
Discussions - Posts authored in topic |
The user must author a specified number and type of posts in a designated forum or topic to fulfill the release condition. This can specify either No Threads, No Replies, or No Threads or Replies. |
Discussions - No posts authored in topic |
The user must not author any number or type of post in a designated forum or topic to fulfill the release condition. This can specify either No Threads, No Replies, or No Threads or Replies. |
Discussions - Score on associated rubric |
The user must achieve a specified Score and Threshold level on a discussion forum or topic, based on an associated rubric, in order to fulfill the release condition |
Assignments - Submission to Assignment |
The user must make a submission to a specified assignment in order to fulfill the release condition |
Assignments - No submission to Assignment |
The user must not make a submission to a specified assignment in order to fulfill the release condition |
Assignments - Receive feedback on Assignment submission |
The user must receive feedback on a submission to a specified assignment in order to fulfill the release condition |
Assignments - Score on associated rubric |
The user must achieve a specified Score and Threshold level on an assignment submission, based on an associated rubric, in order to fulfill the release condition |
Grades - Grade value on a grade item |
The user must achieve a specified grade value on a grade item in order to fulfill the release condition |
Grades - No grade received |
The user must not receive a specified grade value on a grade item in order to fulfill the release condition |
Grades - Released final grade score |
The user must have their final grade score set to released, or set to released plus the final grade meeting a defined threshold, in order to fulfill the release condition. Note: This release condition is evaluated beginning from the first time the grade is released, and cannot be revoked once it is fulfilled. Therefore, if your grade book is set up to release final grades throughout a course, and/or drop ungraded items, the release condition may be fulfilled sooner than expected (i.e. before the end of the course). D2L recommends using this release condition in combination with other release conditions or intelligent agents to ensure that the event or content triggered by the released final grade score occurs at the anticipated time. |
Grades - Score on associated rubric |
The user must achieve a specified Score and Threshold level on a grade item, based on an associated rubric, in order to fulfill the release condition |
Quizzes - Score on a quiz |
The user must achieve a specified score on a quiz in order to fulfill the release condition. Score on a quiz is triggered by publishing a score on a quiz attempt or manually overriding a quiz score via Grades. |
Quizzes - Completed quiz attempt |
The user must achieve a specified number of attempts of a quiz in order to fulfill the release condition |
Quizzes - Score on selected questions |
When a quiz has a learning objective with associated questions and an assessment method attached to it, the user must achieve a specified grade value on the learning objective in order to fulfill the release condition |
Quizzes - Score on associated rubric |
The user must achieve a specified Score and Threshold level on a quiz, based on an associated rubric, in order to fulfill the release condition |
Quizzes - No completed quiz attempt |
The user must not complete any attempt on a quiz in order to fulfill the release condition |
Surveys - Completed survey attempt |
The user must achieve a specified number of attempts of a survey in order to fulfill the release condition |
Surveys - No completed survey attempt |
The user must not complete any attempt on a survey in order to fulfill the release condition |