Custom Widgets and release conditions

Christina.T.727
Christina.T.727 Posts: 41 🧭
in Corporate

Hi All,

I have a custom widget that I have created and want to set up the release condition to be based on the role that the user is enrolled on within the course offering that the widget is displayed on; not there overaching higher org level release condition.

So I've set my widget up that the release condition is

Enrolled in current org unit as Learner

I've then added the widget to a homepage which is available to one of my course offerings.

Enrolled a user as a Learner on that course offering, they have a different role at top "Organisation" level however

Impersonate my learner on that course and they can't see the widget. It seems like the widget is only responding to their Organisational level role, rather than their "Current Org unit" role.

Anyone got any advice on how I can correct this? Release conditions like this work no issue for actual topics within the module and the user can see them based on their "Current Org Unit role"

Is there a way I can create a custom widget at course offering level rather than organisational level?

Tagged:
· Share on Twitter

Answers

  • Stefanie.B.518
    Stefanie.B.518 Posts: 609 admin

    @Christina.T.727
    Is there any chance that you have a few versions of that custom widget?
    I ask because I'm wondering if the release condition has been placed on the widget- but perhaps it's not that specific widget that's been placed on the homepage. If you double check, and you're sure the right release condition has been applied, and the right role for the user- I think it's worthwhile to add this as a case in the Support Portal. That will help us to assign a Support Agent that will have permission to review the user and course details in your environment.

    I've just done a test for the same use case in a sandbox where the user has a different role at org than in the course. I've added the release condition to my custom widget to only be visible to those enrolled in the current org unit as the role: "D2Ler Course Builder." I can see the widget when I view the page as a super admin, and that the release condition has been set.

    When I impersonate the test user, I can see the widget.

    When I impersonate a user without the role super admin, or "D2Ler Course Builder" I can't see the widget.

    · Share on Twitter
  • Christina.T.727
    Christina.T.727 Posts: 41 🧭

    @Stefanie.B.518 - so it looks like the only way you can get it to work, is if you create the widget within a specific course offering, rather than at top org level.

    Which means that I have to create that widget 9 times…. and have 9 different homepages for those modules that need to use this widget for it to work. As you can't create a widget at course level, and then make it available to other courses.

    Which seems crazy. We like to create our homepages at top level, and then roll them down to the courses that use that homepage. Bascially so that we have as much standardization as possible; and as many courses using the same homepages as possible.

    · Share on Twitter
  • Stefanie.B.518
    Stefanie.B.518 Posts: 609 admin
    edited May 14

    @Christina.T.727I think what you're trying to do makes sense and is still possible.

    When you share your homepage from the org level, do you see an option to share the homepage with the whole organization, and then add "All descendants of type: Course Offering" ?

    I gave that a try and it allowed me to have the release condition respected in the unique courses for the users with the expected role in that course.

    The option to Make a homepage available to other org units includes radio button options for which level of the org structure to share the homepage to ex. all descendants of type course offering
    · Share on Twitter
  • Christina.T.727
    Christina.T.727 Posts: 41 🧭

    @Stefanie.B.518 - thanks, spoken to support they don't believe what I am trying to do is possible, and that the release conditions will always pick up based on the org that the widget was created in, which seems an odd approach.

    These were my steps though.

    1. Select cog. Homepage management

    2. Select widgets

    3. Create new widget (so this is at organisation level)

    4. Set release conditions

    image.png

    5. selected the org units I wanted to make the widget available too, save and close

    6. Click homepages (So still at organisational level)

    7. created my homepage, added the new custom widget to this homepage

    8. Under make homepage available to entered the org units I wanted to have access to this new homepage.

    9. Navigated to my course offering. Selected "Manage Hompages"

    10. under active homepage selected the homepage I just created. Clicked "apply"

    11. Go to classlist impersonated a user with the role in this course offering that matched the Learner 110 role as per release conditions, but their organisational role is a different role (they are a learner on some courses a mentor on others)

    12. Go to homepage, and the new widget doesn't display, only the widgets based on their organisational role are available.

    · Share on Twitter

Categories