A round-up of all improvements and changes to the Buzz platform in version v3.0.113 available on May 16, 2019.
Fixed issues
In this release, we:
- Fixed an issue where students who had withdrawn would still appear in the group assignment members list in the Grade Editor screen.
- Fixed an issue where you could not assign a score to a student for a group activity if the student was not in a group.
- Fixed an issue where the Score History screen was showing NaNms instead of 0ms for time spent.
- Fixed an issue in several admin lists (like Course Enrollments, User Enrollments, Subscribers, and Announcements) to ignore extra space characters that surround text in the filter field.
APIs
Updates in version 2019.05.10.3802.
-
PutTeacherResponseandPutTeacherResponses: Fixed an issue where a withdrawn enrollment could receive a grade when a group was graded for an activity. -
UPDATE: On May 30, the
GetUserGradebook2API will begin to have an API Rate Limit enforced. The API Rate Limit will be 50 requests per 5 minutes. See GetUserGradebook2 documentation for more information.
Comments (3)
Hey Jeremy:
Over the last 2 weeks, I don't see any requests from from CP for this API. Are you sure (1) that it is still running and (2) using this API?
We have a question about the new limits for GetUserGradebook2.
We use that command to process our CP 2.0 orientation courses, and it is called once per student during the nightly sync process. That involves about 3500 students. So that's going to be a lot more than 50 times in 5 minutes.
The SDS developers want to know if you recommend that we use another call instead of "GetUserGradebook2"?
They indicate that we also use "GetEntityGradebook2" in a loop. Is that function also affected? Or likely to be?
Thanks,
Jeremy
As far as recommendations, it depends upon the type of data you are trying to recover. We have been working one-on-one with our customers that are impacted by this change and have made different recommendations in each case.
If you would like to get a personal recommendation, I would suggest creating a ticket and identifying your current use-case and what data (which fields exactly) you are trying to extract.
Thanks!