Stream LXP

Author: 

Jon Brydges
Senior Product Manager
[email protected]

Introduction

We have been busy working on more features that allow Stream to deliver a combination of self-guided, dynamically personalised learning journeys, alongside administrator assigned learning.

The new Learning Experience Due Date functionality, and new visibility controls for badges both provide administrators with more options to automate the delivery of learning in ways that suit their organisation, whilst also improving the overall experience for your learners. 

Enrolment Due Dates

What it is:

• The Learning Experience Due Dates functionality allows administrators to set a date for learners to complete their Learning Experience enrolment by.
• Administrations can set rules to assign Due Dates automatically based on the learner’s enrolment date, i.e. ‘N’ days after enrolment.
• The Due Date can be viewed in various locations throughout Stream.

Why we have done this:

• Previous Due Date functionality was not a fully developed concept within Stream. The only way for an Administrator to set a type of Due Date was to set the expiry date on the enrolment. This would result in the learner losing access to the Learning Experience instead of having an overdue status.
• We wanted to give Stream Administrators more control over how long a user had to complete a Learning Experience, but without restricting access to the Learning Experience.

How it works:

A Due Date can now be configured for all enrolments to a Learning Experience. There are a number of places that relate to this setting:

1. The Due After setting when creating a Learning Experience: 
   1. Create ‘New Learning Experience’ > Advanced Settings > Due After (days)
   2. The user’s enrollment due date is then set automatically by Stream based on when the learner is enrolled. 
   3. This date will be visible on the LX tiles on the front-end.
      1. Learner’s can optionally adjust the LX tile due date to move it closer to the present day, but this does not change the actual due date set on their enrolment.
      2. A learner cannot set a personal due date that is after the enrollment due date that an admin has set for them, or after the close date of a Learning Experience.
2. The Due After setting when editing the Learning Experience:
   1. Learning Experience > Settings > Display Options > Due After (days)
   2. As with creation of a Learning Experience, using this option will set a due date for all new enrolments based on when they were enrolled.
   3. Existing enrolments remain unchanged, so the Due Date must be altered on an individual enrolment via the enrolments table.
3. Setting multiple learners’ due dates on the Enrolments Table
   1. If a specific cohort of people need the same due date for a Learning Experience, using the search function and selecting multiple people is more efficient than completing this on an individual basis.
   2. Learning > Enrolments > View All > Set Due Date 
      1. Select one or more enrolments using the check box beside the user’s last name
      2. Click on the ‘Set Due Date’ button
      3. Enter a due date (this will overwrite any existing due dates for the selected enrolments)
      4. This date will be visible to learners on their Learning Experience tiles
      5. Learners can adjust their personal due date on the Learning Experience tile to bring it closer to the present day, but this does not affect the actual Enrollment due date set here.
4. Bulk Edits via CSV
   1. Learning Experience > Enrolments > Import > Upload
      1. Download the user import template file so that you have the latest version and use the Enrolment Due Date column to set due dates for individuals, using the format of YYYY-MM-DD
5. Editing an Individual enrolment
   1. Learning Experience > Enrolments > View All > Edit (under ‘Actions’) > Due Date
      1. Click on the ‘Edit’ icon under the ‘Actions’ heading in the enrolment row
      2. Enter due date (this will overwrite any existing due dates for the selected enrolments)

Viewing Enrolment Due Dates

When a “Due Date” is set by an Admin by any of the ways outlined above, the date will display in a number of places for Admins and Learners including the ‘Enrolments > View All’ table, the admin ‘Leaderboard’ for each Learning Experience, and the Learning Experience tiles in the front-end. 

1. The Enrolments Table
   1. If the Due Date is in the past, and the Learning Experience is not complete, the date will display in red with a warning icon
2. The Learning Experience Tile
   1. When a Learning Experience Due Date is in the past and it is not complete, the Due Date will display as overdue and in red on the tile
   2. A Learner can set their own personal Due Date on the tile as per existing functionality
   3. If an enrollment Due Date is set by an Admin, the Learner can set a personal Due Date that is before the given date, but not later.
   4. The personal Due Date set by the Learner is only displayed on their Learning Experience tile and does not change the actual enrollment Due Date set by the Admin in any of the reports outlined above.

Front-end Badge visibility options

What it is:

• Administrators can now control whether a badge can be seen by learners on the front-end, or not. This can be based upon the status of the badges for the learner.

Why we have done this:

• Badges have started to be used more widely by our clients, but in a number of different ways. These new visibility options give administrators the option of using badges solely for internal reporting that is not visible to the learners, as gamification tools that only appear once the badge is achieved, or as an accreditation mechanism.
• Because badges can be used as criteria for other badges, and also as criteria for upcoming dynamic rules for groups, it is possible to create adaptive learner journeys using a combination of hidden and visible badges where progress across a number of learning experiences and events (e.g. comments, completing objects, completing badges) are ‘rolled up’ to achieve a badge, or to trigger membership of a group that assigns or recommends nea learning, or even all of the above.

How it works:

When creating a new badge (‘Settings > Badges > Add Badge) an administrator has the following visibility options:

• Always – the badge will always display for all learners in the Org (as per current functionality) 
• When ‘In Progress’ or ‘Complete’ – the badge will not display if no progress has been made (i.e. no criteria met)

This is not the default option

• When Complete – the badge will only display for all learners in the Org that have fulfilled all criteria and have been awarded the badge
• Never – the badge will never show to any learner in the Org regardless of fulfilling the criteria. The badge is visible to admins in the admin portal only.

This is particularly useful for reporting, or for ‘rolling up’ progress across various badges.

Rapids Enhancement

What it is:

• The option to disable the completion message surfaced to learners once they have completed Rapids Resources.

Why we have done this:

• Based on feedback from our users, they indicated they would like to have control of this setting. We wanted to give administrators more input over the user experience, particularly in these scenarios:
  • When the Rapids content is short, the completion message surfaces almost immediately after opening the object, causing a hindrance 
  • When the content does not suit the concept of being ‘complete’

How it works:

• Create/Edit Rapids content from the Resource Library > Settings (cog icon) with the page settings. From here the new setting for ‘Disable Completion Message’ is visible. Tick the checkbox to switch the completion message off.

Bug Fixes:

• Rapids – Content will only be marked as complete when the learner has viewed the entire page and completed any interactive widgets
• LXP-4717 – RTL languages displaying correctly on the UI
• LXP-5071 – Awards: Assigned badges are now being added for users when an LX is complete
• LXP-5048 – Resources: Now allows files to begin with underscore
• LXP-4797 – Impersonating user footer bar no longer covers elements
• LXP-4810 – Time Zones: Add America/Kentucky/Louisville as a supported timezone
• LXP-5268 – Update Rapids to 1.0.9
• LXP-5157 – Changing LX images no longer breaks any duplicate LX images
• LXP-5057 – Resources: The ability to copy a resource URL has been added
  • This link provides learners with direct access to the resource, rather than having to launch the resource from inside an object. This allows you to surface a static link to the resource from anywhere inside Stream. E.g. if you have different versions of content in various languages, you could provide links to all of the versions in one object rather than having to create multiple objects. Using xAPI completion, the object can be marked complete regardless of which resource was chosen by the learner.
  • Note: The link must be copied from org you intend to use it in. If you are logged into a parent org and are administering a child org, the subdomain in the link you copy will be incorrect.

• LXP-4726 – Mandatory LX: Mandatory Learning Experience tiles are now surfaced in the ‘Mandatory’ stream even if Focus Area that assigned them to the users has been deleted
• LXP-4933 – Duplicated FAs: Large groups no longer causing Focus Areas to be duplicated
• LXP-4281 – Focus Areas: When Admin adds to LXs to a linear Focus Area at the same time, the second one is no longer surfaced as unlocked in the front-end
• LXP-5103 – Users: Leaderboard Opt Out default is now applying for new users