Content Controller V3.2.66


New Features

Folder Access Controls

Folders in the Content section now have an “Access Controls” heading in their detail panel. From there, users can now be given read-only or read-write access to folders, much like with accounts. Users with read-only access to a folder can see it and its contents, share its content with accounts, and do sandbox launches. Users with read-write access can also add, remove, and configure content in the folder. In order to make managing ACLs easier, administrators can create teams of users in the Admin section.


Share with Multiple Accounts

This is a workflow improvement for users who need to add new content to multiple accounts. Historically, they’d have to visit each account individually, then find the new content. Now, they can select the new content in the Content section, then click a “Share” button to add it to one or more accounts.


Account-Level Course Configuration

Let’s say that you almost always want your courses to launch in a frame, but you have one customer who needs all of their courses to launch in a new window. Prior to CC v3.2, you’d either have to individually configure every course in that customer’s account, or use the API to automate the process. Now, you can set a default launch type in an account’s “Advanced” tab, and apply the new setting to all content that gets added to that account.


xAPI Context Additions

Users can add custom information to their xAPI-based (cmi5 & Tin Can) or media file courses in CC, and also to their accounts. That information is then included in any xAPI statements that are forwarded from CC to reporting systems such as Watershed. CC customers can use this to add additional context that is meaningful in their environment, such as “program codes” for related courses, or organization IDs for accounts.


Potentially Breaking Changes:

The improvements that we've made with this release required us to make a few potentially backward-incompatible changes:

  • The format for datetimes in exported CSVs has been normalized. They should now all use the same YYYY-MM-DD HH:mm:ss.S format. If you have automated processes parsing these values, make sure they are updated to expect this new format.

  • Names of the files shared from CC will change slightly. Characters with diacritics will have them removed to make it easier to import the files into LMS's that don't allow Unicode file names. Unicode characters without an obvious ASCII parallel will be unaffected.

  • We fixed a long-standing bug with how learner licenses worked. Previously, if a learner launched a course on one license then launched the same course after a new license had been applied, the learner count on the second license would not increment. This has been resolved, and the learner will now count towards both licenses once. If you have a lot of learners launching the same content over multiple licenses, you may see an increase in the learner count on the second license that you didn't notice before.

Note to self-hosted customers:

Content Controller is built around its sister product, Rustici Engine. If you're upgrading to 3.2.xx from CC 2.2 or earlier, then we need to also upgrade Engine's database schema. To do this, just add the argument -e engine_upgrade=true to the command for running your playbooks. This flag tells Ansible that this particular deployment requires the Engine upgrade. You won't be required to use this flag when moving from any 3.1.xx release, or when moving between maintenance releases (e.g. 3.2.66 -> 3.2.74) unless specified in the release notes.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk