Significant impact to administrators due to new role permissions and configuration variables. The ability to run Brightspace Data Sets is controlled by data set-specific permissions. From Tools > Roles and Permissions > Brightspace Data Sets, grant the permissions that correspond to the data set you want the user to be able to run. For example, to run the User Enrollments data set, grant the Can execute User Enrollments permission at the org level. Brightspace Data Sets use the following configuration variables for performance tuning, visible only to D2L: (Org) - Batch size to use for the Brightspace Data Sets queries. The default is 100,000. d2l.Tools.BrightspaceDataSets.RowLimit (Org) - Maximum number of rows that any Brightspace Data Set outputs to a file. The default is 150,000,000. (Org) - Limit of how many characters are exported for fields with no maximum length from the Brightspace Data Sets. The default is 1,000. 1. Ensure that the Data Hub tool is enabled. 2. From the Admin Tools menu, select Roles and Permissions, and grant the following Brightspace Data Sets permissions at the org level: Can Access Brightspace Data Sets Can Execute <data set name>. For example, to run the User Enrollments data set, grant the Can Execute User Enrollments permission. For detailed information about Brightspace Data Sets, refer to the new Data Hub - Administrator Guide when it is released. Document Conversion Service | New To improve the document viewing experience for users, this release introduces the Document Conversion Service. When documents are uploaded to the Content tool, Assignments tool, Brightspace Learning Repository, or Brightspace ePortfolio, the documents are converted to PDFs, which display inline in the tool or product. Previously, the DocumentBuilderService rendered documents as images at different zoom levels. Global Change System Requirement Change Impact of Change Technical Details Next
Awards PRB0054307 When a user updates the expiry date of an award, the new date does not propagate to awards that were already issued to users. The message that displays suggests it may propagate to awards that have already been issued, but it does not for expiry dates. Found in Brightspace Learning Environment 10.5.2. To reproduce this issue: Access an instance of Brightspace Learning Environment that has Awards enabled and the necessary permissions granted, for example, that learners can receive awards. In a course, go to the Awards tool and click Course Awards. Click Add Award To Course. Click Create Award. Enter a name and a description, and set the Award Type to Badge. In the Availability section, ensure that the Make this award available to all of my courses radio button is selected. Under Expiry, select Fixed Date, and then enter a date in the future. Add an image for the award and click Save. For the award you just created, click Edit Properties. Create a simple release condition such as Classlist: Role in current org unit and Enrolled as: Student. Ensure there is at least one learner (Student role) enrolled in the course. Go to Classlist Awards and verify that the learner in the course received the award you created. Click the badge icon for the learner and take note of the expiry date (the one you set previously). Return to Course Awards and click Edit Award for the award you created. Notice that the pop-up message reads, "Changes made will propagate to all instances of this award including those who have already earned this item." Ok. Edit the expiry date to be something different from the existing date. Save and notice the warning message that includes a similar message about the change being propagated to all awards, including those that have already been issued. Go to Classlist Awards. Click the badge for the learner who was issued the award previously. Observe that the expiry date remains as it was before you changed it.