It would be nice to have the option to automatically enroll a learner in every course that is included in a particularly curriculum. As it is right now, we have to enroll the learner in the curriculum, then each individual course as well, which is quite an administrative burden.
1
Low Probability of Delivery
Neither Trainers or those receiving activity or progress reports should have to use a Quijije board to understand reports out of Absorb. The fact that the development team has decided they don't want to spend time improving the reporting of activities and courses with something more appropriate des not endear us to Absorb. The fact that this "enrollment " issue has been at least two years to get a decision that essentially nothing is going to be done to improve the situation will probably lead to some users leaving Absorb for another LMS.
We use the post-enrollment on enrollment with 0 delay method to accomplish this.
I know this is an older post and its already labeled as unlikely to implement but like Drew Klassen mentioned you basically need to create a Bundle to accomplish what you are asking.
Drew, thank you so much for this suggestion! This is a huge help. This limitation has been a frustration for me and my admins for a long time.
To accomplish this, I set Post Enrollment Rules on my curriculum to enroll in the courses contained within at time of (curriculum) enrollment at 0 days. You can do them individually there, or make a course bundle, and Post Enroll to the one bundle.
When I first started trialing Absorb LMS, I thought it was odd that users basically had to enroll in a course "twice", but Paul's explanation makes total sense.
Clients typically use the variation of completion requirements in Absorb curricula because there is an 'optional' component to the completion such as minimum credits/courses. In those cases enrolling into all content isn't appropriate, and there are other cases like "the Course is also available outside the curriculum", or "the Course is included in multiple curricula" that make matching the expectations on this feature very difficult. It is a good idea, but we have a lot planned for the 2022 roadmap already that makes us unlikely to be able to devote the attention needed to get this one right.