Sprint 86 was released on Wednesday, 3/29/17 and included the following enhancements and new features:

NEW

  • Multiple Rate Categories: An organization may now have x number of rate categories instead of the previous limit of 2.
  • Globalization: Groundwork has been laid for globalization and page language versions. Coming Soon!

ENHANCEMENTS

  • Manual Assignments and Search Learners by Location: Finding and selecting learners for manual assignments or for managing learners can now be done using location. Country, state and province have been added to the existing search criteria.
  • Dropbox and Discussion Submission History: Dropbox Submission history is now available on the Section Roster whether or not a submission has been graded or rejected.
  • Modal Windows for Content Packages: A new option has been added for Content Packages to allow them to open in a Modal Window as opposed to a new window.
  • Revoked status on Enrollment for Export Clients: AICC HACP Learner enrollments are no longer marked "Failed" when they receive a new enrollment in the same product as a previous enrollment. The enrollment is mark "Revoked" instead.
  • Assignment Detail Report and Learner Fields: Assignment Detail report now includes Learner Lookup fields, and the column headers use your organization's custom field labels.
  • Learner Profile and Credit Category Preferences: Credit Category preferences are no longer shown if there is one or no Credit Categories.

Feel free to leave questions or comments about this sprint!

Start a New Discussion
latest participants
Jump to:
  • Matt Kamen

    Sara, regarding the modal windows for content packages, we tested this with a couple of our packages and found some inconsistent behavior. Can the team provide some insight into whether these can be addressed at the LC-level or confirm if it requires changing technical requirements with our course developers?

    (1) Modal window size has a max-width of 900px. Is this a technical limitation? We had anticipated the modal would respect the window dimensions set on the specific activity. Reduced to 900px, some of our packages (originally optimized at 1024 or 1280) are not a good visual experience.
    (2) Is there any possibility of adding a full-screen toggle option?
    (3) "Exit" button behavior within packages is inconsistent. We have one package (AICC -- developed by LearnSomething) where the exit button closes the content, but leaves the modal window open in the background. For another package (SCORM -- off-the-shelf authoring tool), the exit button closes entire LC course page.

  • Brian Legg99

    Hi Matt, you are correct that the different package types can be inconsistent. With SCORM only the content can make calls into the API. So, if the user closes the modal with the X button the LMS can't call into the API. The content must be able to detect that the modal is navigating away or closing and then it must initiate the proper calls to commit the data. We are having success with this listening to the following event:

    window.onbeforeunload = function()
    {
    // perform commits or anything else needed before closing the window
    }

    This will work with the exit button and with the modal X button. AICC and TinCan are similar to SCORM in that the content makes calls to the API but unlike SCORM the exit buttons within the content cannot be monitored by the LMS. This means that an exit button within the content can't properly close the modal window. With AICC and TinCan we recommend using modal windows for content without close/exit buttons.

  • Brian Legg99

    Addressing your other points:

    (1) - 900px is not necessarily a technical limitation, but it is currently not a configurable option.
    (2) - A full-screen toggle is a good idea and something we will consider for future enhancements.

    Thanks Matt,

Jump to:
Log In to add a new post.