Daytona State College: Go Falcons!
Showing 3 of 3 Results

Academic Innovation Blog

06/26/2018
profile-icon Bill Harrison

This is the third post in the course personalization series. You may want to review the first two posts:

  1. Part I - Replace Strings
  2. Part II - Release Conditions

This is a long post, so use this menu to access the different topics.

Intelligent Agents can assist instructors, administrators, and students by providing an automated notification when defined activity occurs in a course or when there is a lack of login or course entry. Notifications can be customized using replace strings.

You can access the intelligent agents tool in two locations, the Course Admin screen or the Class Progress screen.

First, you can go to the Course Admin link on the navbar then select Intelligent Agents.

Figure 1 - Accessing Intelligent Agents from the Course Admin page.
Access Intelligent Agents from the Course Admin page

Second, you can select the Class Progress tool from the Tools menu on the navbar or the Course Admin page, then select Use agents to automate feedback.

Figure 2 - Accessing Intelligent Agents from the Class Progress screen.
Access Intelligent Agents from the Class Progress screen

Once you access the Intelligent Agents tool, you will see the Agent List screen with a New button for creating agents and a listing of all previously created agents, if any.

Figure 3 - Access Intelligent Agents settings on the Agent List screen.
Access Intelligent Agent settings on the Agent List screen

As a best practice, you should first change the settings for intelligent agents by selecting the Settings link in the upper right corner of the Agent List screen; then choose Set custom values for this course. Put your name and Daytona State email address in the relevant fields then save this information. You will be returned to the Agent List screen. This setting ensures that any replies to any email messages sent by an agent will return to you. Note that you must update this setting in each course you teach.

Figure 4 - Change Intelligent Agents settings.
Change intelligent agent settings

On the Agent List screen, select the New button. On the New Agent screen, first give the agent a required name and optional description. As a best practice, you should always include a description that includes, at a minimum, the criteria for the agent and anything that will need updating when you copy a course forward, such as schedule, etc. Next, decide if the agent is enabled. If it is not enabled, the agent will not run. Think of this as draft mode. Note that you can save an agent at any point once you have provided a name, and you can come back and edit it at anytime.

Figure 5 - Naming an agent.
Naming an agent

Specify agent criteria
  1. Choose to run the agent against a specific role or all users. In most cases, you should run an agent specifically against the Astudent role.
  2. Choose whether you want to set the agent to run based on:
    • Login activity for Falcon Online (but not course access)
    • Course access activity
    • A set of release conditions
    • You can use a combination of any or all of these criteria.
Figure 6 - Specifying agent criteria.
Setting criteria for an agent

Specify agent actions
  1. Decide how often you want the agent to take action.
    • Only the first time it runs
    • Every time it runs
  2. Decide if the agent should send an email and to whom.
    • Not required. Agent can still run, and you can see the history of who met the criteria. More on this later.
    • Use replace strings to customize and personalize the email.
      • If you want an email to go to the students that meet the criteria, you should use the {InitiatingUser} replace string in the To: field. This will insert the email address for each student that meets the criteria. Note that each student will receive a separate email.
      • As a best practice, insert the {OrgUnitName} string in the subject, which will insert the course name. You can add any additional information after the variable
      • Notice that the email body uses the standard HTML editor. This allows you to include links to relevant course material. For instance, if the agent references a topic the student has yet to access, you can provide a link to that topic in the email.
Figure 7 - Specifying agent actions.
Specify agent actions

Specify agent schedule

This is not required as you can always manually run the agent whether it is set to run on a schedule or not. If you want to set a schedule:

  1. Select the check box for Use Schedule
  2. Select the Update Schedule button
  3. On the Update Agent Schedule popup:
    • Choose whether to repeat daily, weekly, monthly or annually.
    • Depending on what you choose, specify the additional Repeats Every: information.
    • ALWAYS set a start and end date. Note that you may have to scroll down to see the date settings.
    • Select Update and then you will be back on the previous scheduling screen.
Figure 8 - Specifying agent schedule.
Specify agent schedule

Remember to save the agent by using the Save and Close or Save button at the bottom of the New Agent screen. Choosing Save allows you to continue to edit the agent. Choosing Save and Close will put you back on the Agent List screen.

Figure 9 - Saving agent.
Save agent

The Agent List screen will list all previously created agents by name and description as well as a link to the results of the last run, the last run date, and the next run date for each agent. You can also:

  • enable/disable or delete agents in bulk by selecting the checkbox for one or more agents and selecting the relevant link at the top of the list
  • restore deleted agents using the More Actions button at the top
  • edit an agent by selecting its name
  • access the action menu for an agent by selecting the dropdown arrow next to an agent’s name. The access menu allow you to:
    • Edit
    • Copy
    • View history of all runs, not just the last. Includes practice runs.
    • Perform a Practice Run (does not send an email).
    • Manually run the agent, even if it is set to run on a schedule.
    • Delete
Figure 10 - Agent List screen and options. Agent list screen and options

Editing an Agent

If you choose to edit an agent, you will see the Edit Agent screen. This screen is the same as the New Agent showing the properties for the selected agent. You can change any of the properties to update the agent.


Running an Agent

An agent can run three ways:

  1. Practice run from the action menu. This allows you to ensure the agent is running correctly. A practice run doesn't send any notifications but does show in the agent history.
  2. Run now from the action menu. This is a manual run. Each run shows in the history. A manual run will send notifications. When you set an agent to run manually, you will see an indicator manual run iconnext to the agent name on the Agent List screen. When you run an agent manually, it sends a confirmation email to the user that requested or set up the agent. This email contains the following information: org unit code and name, which agent ran, time and date the request was submitted, time and date the request was finished, and whether the agent took action.
  3. Preset schedule. This is the schedule you set when creating the agent. Scheduled agents will run at approximately 8:00 PM (Eastern) on the specified dates. Each run shows in the history. A scheduled run will send notifications. When a scheduled agent runs, it sends a confirmation email to the user that set up the agent. This email contains the following information: org unit code and name, which agent ran, and whether the agent took action.

Viewing an Agent's History

You can view an agent's history three ways:

  1. select the link for the last run on the Agent Listscreen
  2. select View History from an agent's action menu dropdown which will show each time an agent has run
  3. select the View History button on the Edit Agent screen which will also show each time an agent has run

The agents history shows the date and time of each run, a link to the results for each run, the type of run and who initiated the run.

Figure 11 - Agent Run History
agent run history

Select an individual result to see a list of users that matched the agent's criteria and any action taken. You can select an individual action for details.

Figure 12 - Agent run details
agent run details

Select the link for an individual action to see a copy of the email sent to that student.

Figure 13 - Email sent by agent
email sent by agent

There are numerous ways to use intelligent agents in your course. A couple are listed here. Use the previous screenshots to create either of these examples.


Example 1 - Lack of course entry/access
  • Why: To see which students are not "attending" class.
  • When: Daily, or at least a couple of times a week.
  • How: Set to check for NO course access over the past 5 to 7 days.
  • What: Send an email directly to the student when they haven't accessed the course during that time period. Or choose to have the agent run but not send an email. Then you can review the run history and decide whether an email is warranted. If you choose to not have the agent send the email automatically, ignore steps 8 - 11 below.

Here are the properties to set for this agent.

  1. Name: Lack of Course Entry
  2. Description: This IA will check to see which students have not entered this course during the designated time period.
    1. Current time period = no entry for 5 days.
    2. This IA is run automatically every Monday, Wednesday, and Friday, through the final class date.
    3. This IA sends an email to the student or this IA does not send an email but runs so the instructor can review the run history.
  3. Status: Agent is enabled
  4. Role in classlist: Astudent
  5. Agent Criteria: User has not accessed course for at least 5 days
  6. Action repetition: Take action every time the agent is evaluated and the agent's criteria are satisfied for a user
  7. Schedule: Evaluated every 1 weeks on Monday, Wednesday, Friday starting Monday, August 26, 2018 until Saturday, December 18, 2018
  8. Email Format: HTML
  9. To: {InitiatingUser}
  10. Email Subject: Absent from {OrgUnitName}
  11. Message: Hello {InitiatingUserFirstName}, You have not entered the {OrgUnitName} course shell during the past five days. Let me know if you need any assistance.

Example 2 - Successful completion of module activities
  • Why: To reassure students that they have completed all the class expectations for a module.
  • When: When the student has completed the activities.
  • How: Use release conditions for the required items, triggering IA when all conditions are met.
  • What: Send an email to the student (CC yourself, if desired) encouraging them to keep up the good work.

Here are the properties to set for this agent.

  1. Name: Successful Completion of 1st Module Activities
  2. Description: This IA will send an email to the student (CC Instructor) to assure them that they have completed all the required first module activities for the course.
    • Edit this agent if the required activities change in a future term.
  3. To access this item, users must satisfy: All conditions must be met
  4. Visits the content topic: Course Syllabus
  5. Receives equal to 100.00 % on the quiz: Syllabus Quiz
  6. Adds 1 threads to discussion topic: General Course Info/Course Introductions
  7. Email Format: HTML
  8. To: {InitiatingUser}
  9. CC: instructor@college.edu (instructor's email would go here)
  10. Email Subject: {OrgUnitName} First Week Activities Completed!
  11. Message: Congratulations {InitiatingUserFirstName}!
    • You have completed all of the required activities for the first module of {OrgUnitName}. My records indicate that you have:
      • Visited the Course Syllabus in Content
      • Scored 100% on the Syllabus Quiz
      • Posted your course introduction in a new thread on the Discussion Board
    • All indications are that you are off to a good start for this course. Now that you have completed those activities, you should see the next content module and you can begin work on that now, if you like. There are a couple of deadlines next week, so pay attention to all the requirements, just as you did in week one.
    • Keep up the good work.
      Professor Bink

Other examples include but are not limited to:

  • sending an email reminder to students that haven't completed an activity such a discussion post or assignment submission
  • sending an email to students that may have performed below a certain threshold on an assignment or quiz with recommendations on what they might do to improve on the next
  • sending an email to students congratulating them on performing well on an activity

While Intelligent Agents are a great tool, there are a few recommended best practices and possible pitfalls to consider.

Best Practices
  • Sanity check - Use Intelligent Agents when there isn't a better way of communicating:
    • Can a D2L Notification work better?
    • Can a News Announcement work better?
    • Can a personally crafted email work better?
    • Would a discussion board posting work better?
  • Use Intelligent Agents sparingly
    • Too many repetitive emails may lose their effectiveness
    • Reserve use for the most important items
  • Should the agent send an email? There are various examples of when you might want to NOT automatically send an email to the students.
    • By having an agent run and you review the history, you have one more chance to determine whether that email to the student might be warranted.
    • Maybe the student told you in advance that they would be out of the country and disconnected for 10 days. Do you really want to send that student an automatic email asking them to submit an assignment?
  • Mix it up between Automatic and Manual. Carefully consider the implications of Manual versus Automatic running of Intelligent Agents:
    • Automatic Agents will run once a day, or less often, as scheduled.
    • You should set starts and stop dates to automatic agents.
    • Manually triggering the Agent allows you to determine when the timing is right.
    • Manual run also executes immediately when you select it, rather than waiting until the designated time of day for automatic runs. NOTE: Automatic agents run at 8:00PM Eastern.
    • Names and descriptions are your friends. Use the Agent name and description fields to your own benefit:
      • Name your Agent well to easily pick it from the list.
      • Describe what the Agent is intended to do and when it will be used.
      • Add a reminder to yourself in the description about info that needs to be changed from term to term (due dates, office hours, etc.).

Potential Pitfalls
  • Replace strings (or Replacement Strings) are great, but..
    • Ensure that your replace strings are properly formed. No one wants to see this in their email: Hi {Initaiting UserrFirst Mane}!
    • Use "name" strings sparingly, as you would when speaking with the student. Every other sentence is a bit unnatural.
    • Also, the replace strings can only use the names that are recorded in the D2L database. If a student only wants to be called by a nickname, the FirstName Replace String will only pick up the name in the database.
  • Copying a course from term to term
    • Intelligent Agents will copy but they will be disabled in the new course, which is a good thing. You don't want agents running before you are ready! Remember to update properties and re-enable agents in the new course.

For more information, consult the Falcon Online Intelligent Agents help or view these videos. This is a playlist of five videos. They will play through automatically once you start them or you can access the individual videos by using the hamburger icon in the upper left corner of the video.

I encourage you to subscribe to this blog to receive notifications of future posts and give us your comments or contact us in the Faculty Innovation Center.

Photo of Bill Harrison

Bill Harrison
Senior Instructional Designer/Instructional Technologist
william.harrison@daytonastate.edu | 386.506.4306

No Subjects
06/11/2018
Unknown Author

We at the Faculty Innovation Center always strive to make technology available we feel would benefit faculty. Whether it's adding more services or acquiring new equipment, aiding you in achieving your goals as instructors and members of the Daytona State community is our top priority.

Recently, we purchased a conference cam for use in the FIC. What does this mean for you? Have you ever dialed into a meeting, sat in your office or at home listening and wondered who was speaking or not truly felt like a part of that meeting?

This Logitech Conference Cam will enable you to attend meetings remotely and actually SEE who is speaking and who you are speaking to. It will help you feel like you're more of a participant in the meeting instead of just a bystander.

We have already tested out the camera and are pleased with its capability to make meetings a more participatory experience for all attendees instead of just those who are present in the room.

If you want to see for yourself or have any questions regarding this exciting new addition, please feel free to stop by the FIC and we'll give you a demonstration!

Pam Ortiz
Administrative Specialist, Division of Online Studies
pamela.ortiz@daytonastate.edu | 386.506.3638pam ortiz

No Subjects
06/04/2018
profile-icon Bill Harrison

This blog is part II in a series for personalizing your course in Falcon Online.

Read Part I – Replace strings
Read Part III - Intelligent Agents

This is a lengthy post, so you can use this table of contents to access specific sections.

  1. What are release conditions?
  2. Where can I use release conditions?
  3. Types of release conditions
  4. Creating release conditions
  5. Best practices
  6. Video Demos

What are release conditions?

Release conditions are conditional requirements that restrict access or visibility to specific content, resources or areas within the Brightspace Learning Environment. Users must satisfy the conditions before the restrictions are removed. They allow you to create a custom learning path through the materials in your course. Here are few examples of usages for release 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. You could also release an announcement personalized with replace strings to users pointing them to this additional content or congratulating those that achieved 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. Alternatively release content based on students performing a required activity such as posting to a discussion or submitting an assignment.
  • 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 submissions folder. 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 submissions folder. We will cover intelligent agents in a following blog post.

IMPORTANT REMINDER: Release conditions are separate from availability dates. When you assign dates to an item, students will still see the item in the course and will be able to access the item based on the date settings. However, items with release conditions do not appear in the student view of the course until the condition is met. You can assign both to an item. For example, you can set a release condition on an assignment folder requiring that a student first access a specific content topic. You can also assign availability dates to the assignment folder. Until a student satisfies the release condition, the assignment folder will not appear in the course. Once the release condition is satisfied, it will appear. However, no submission will be allowed until the assigned start date is met.

Back to Top

Where can I use release conditions?

 Release conditions are supported throughout Falcon Online. They can be used in the following tools:

  • Checklist
  • Content modules and topics
  • Custom widgets
  • Discussion forums and topics
  • Assignments
  • Grade items and categories
  • Intelligent Agents
  • Announcements items
  • Quizzes
  • Surveys

Back to Top

Types of release conditions

The following table lists the types of release conditions available.

Condition Type

Description

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:

  • be enrolled as a specific role
  • not be enrolled as a specific role

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.

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.

Discussions - Posts authored in topic

The user must author a specified number and type of posts in a designated module or topic in order to fulfill the release condition.

Discussions - No posts authored in topic

The user must not author any number or type of post in a designated module or topic in order to fulfill the release condition.

Discussions - Score on associated rubric

The user must achieve a specified Score and Threshold level on a discussion module or topic, based on an associated rubric, in order to fulfill the release condition.

Assignments - Submission to Assignment submission folder

The user must make a submission to a specified assignment submissions folder in order to fulfill the release condition.

Assignments - No submission to Assignment submission folder

The user must not make a submission to a specified assignment submissions folder 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 submissions folder 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 submissions folder 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 - 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.

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.

 

Back to Top

Creating release conditions

  • To access release conditions for a discussion forum or topic, checklist, assignment submissions folder, grade item, quiz, survey or custom widget, access the edit screen and select the Restrictions tab. This screenshot shows accessing release conditions for a discussion topic. Accessing Discussion Topic Release Condition Tool
  • To access release conditions for an Announcements item, scroll to the Additional Release Conditions at the bottom of the edit screen.
    Release Conditions Tool for Announcements
  • To access release conditions for a content module, select the module and then “Add dates and restrictions."
    Access Release Conditions for Content Module
  • To access release conditions for a content topic, select the dropdown arrow next to a topic name and then “Edit properties in place."
    Access Release Conditionn Tool for Content Topic


    On the next screen select “Add dates and restrictions”
    Access Release Condtions for Content Topic part 2

Once you access the release conditions tool, you will see two buttons. These buttons will be labeled differently depending on how you access release conditions. They will be labeled Create and Attach or Create, which allows you to create a new release condition, and Attach Existing or Browse, which allows you to reuse a previously created release condition.

Different labels on buttons for creating release conditions

Choose Create and Attach or Create to create a new release condition.

  1. Choose a type for the new release condition.
  2. Based on the type you choose, you will need to set additional conditions. Then select the create button.
    Setting condition type and conditions
  3. Since you can set multiple release condition on an item, you can choose whether any or all conditions must be met. The default is all.
    User satisy all or any condition.

Once you set up release conditions on an item you will see those indicated similar to this. Notice the icon.

Release conditions indicator

If you want to remove a release condition you previously assigned, access the release condition tool for the item and then select the trash can icon to delete all release conditions or the “x” next to a specific release condition to delete them individually.

 

IMPORTANT REMINDER: Release conditions are not editable. If you need to change a release condition for an item, you must remove the current release condition, then create and assign the correct release condition.

Deleting release conditions

 Back to Top

Best practices

  • 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 Learning Environment 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 submissions folder 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 submissions folder. For the assignment submissions folder, 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 submissions folder.
  • 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 submissions folder and then set a condition that they must submit a file to the assignment submissions folder 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 submissions folder 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.
  • Copying release conditions – Release conditions can be copied from one course shell to another. If you copy all components, everything will still work as before, but if you choose to copy individual course components, including release conditions, you must remember to copy the items to which the release conditions are applied.
  • Clearly communicate to students – Students do not see items that are conditionally released. Ensure you communicate to students that new content will appear based on release conditions. This can be included in your syllabus, course schedule, announcements, etc.

Review these videos on creating release conditions.

Attach a release condition

Create custom learning paths with release conditions

I encourage you to subscribe to this blog to receive notifications of future posts and give us your comments or contact us in the Faculty Innovation Center.

Photo of Bill Harrison

Bill Harrison
Senior Instructional Designer/Instructional Technologist
william.harrison@daytonastate.edu | 386.506.4306

No Subjects