Next Catalog improvement: Bulk Purchases and Enrollments
The Catalog Team spent the beginning of the year tweaking and fine-tuning the Shopping Cart and improving receipts. The team has also started building a new feature: Bulk Purchases and Enrollments. This feature enables individuals to purchase multiple seats in a single listing and distribute those seats by inviting students to enroll in that listing for free. This feature can also be used to enroll multiple students in free listings Users can view historical payments and enrollments by accessing the Purchases and Enrollments page from the Catalog menu.
Similar to the Shopping Cart feature rollout, the Bulk Purchases and Enrollments feature will be released in multiple phases to Beta, but in one batch to Production.
A new button will soon be added to the Details (Listing) page to allow institutions ample time to adjust their custom CSS/JS code. In the beginning, the button will not work and I apologize for this limitation, but we would like to make sure that institutions have time to adjust any customizations, if necessary. Our goal is to have this new feature finished by the end of Q1 2022 and have the first Beta release next week.
Please stay tuned, I will update this thread after each Beta release.
UPDATE: We will need a little bit more time to complete all the requirements for bulk purchase and enrollment so it's not going to be finished by the end of Q1. I will keep this post up-to-date and let you know about the upcoming Beta release dates.
UPDATE2: May 23 we released another major part of bulk purchase and enrollment to Beta. We are going to have a few more Beta releases before releasing the new functionality to Production.
When our customers file support cases that get triaged as bug tickets, some are fixed while others are “shelved”, hoping engineering can get to them later. We’re refining our processes to make clear decisions more quickly and keep you informed about the status of your bug reports.
The survey results are in, and you’ve told us you’re looking for an easier way to see what’s changing in Canvas. Our engineering teams are working on an initiative to simplify on their end, but until then, we’re making a change on September 17 to streamline the Community experience.
Fixed bugs have been included in the deploy notes since, well—the creation of the deploy notes. And for the last few years, the “Known Issues” board in the Community has only included notable bugs, which didn’t always align with the bugs posted in the deploy notes.
It’s time to evolve our process for greater clarity, and this time we’re putting our focus into our Known Issues board to give you more timely updates when you need them.
[UPDATE 18 MARCH 2021—The content in this post has been adjusted from user feedback (thank you!) Stay tuned for revisions being implemented in the 2021-04-17 Canvas Release Notes, which will be published on March 22.]
Effective March 22, we are changing how release notes comments are managed to provide a better experience for everyone.
Our teams have several projects still in progress related to our COVID-19 response. These features may continue to be released weekly when available through May 2020. If no features are ready to be released on a given weekend, no Ready Release will take place.
Way back in 2014—which in Canvas time feels like an eon ago—product and engineering devised the idea of a feature option, which was a way to help each Canvas admin manage larger features that may disrupt the workflow if included as part of a regular release cycle. In the Account Settings and Course Settings pages, this new concept was given its own tab where most included features could be managed at any time. Depending on functionality, features may be able to be allowed or turned on at the account, sub-account, course, and user levels.
Last November we posted a proposal for Canvas release changes in 2019. Our proposal intends to improve the quality of Canvas releases, resolve bugs more quickly, and create more predictable releases with a more manageable pace. Community feedback proved highly supportive, and our engineering teams have continued to make progress with necessary adjustments. Thanks for your patience as we’ve been working out the specifics to share with you.
Last week we made a change in the Canvas Community to update all Arc references to Canvas Studio. Some of you have already seen this change. A more official announcement is being unveiled by our marketing team in a few weeks. Although we can't formallysteal their thunder, we can share with you what's coming!
Every day, we come to work with one purpose in mind: we want to help you achieve your goals and find success within the life-changing field that is education. Canvas is the LMS that makes teaching and learning easier. And every day we want to give you our very best, no matter what it takes.
Over the last few years, we’ve been making constant modifications to improve the release notes for Instructure products. Recently some of you may have participated in the Canvas Community health check—a survey that helps the Community team gauge your experiences with the Canvas Community. For better or worse, we use that survey to help us find ways to make your experience with the Canvas Community even better!