This page has been deprecated. Please refer to the updated documentation here: Starting a new Learning Plan

Summary

This page describes the rules that govern a Practitioner's ability to start a new Learning Plan.

See also: Eligibility Queue

Overview

The Practitioner's Learning Plan List page displays a list of all Learning Plans that the current user is eligible to begin, has already begun, or has completed.

Eligibility Prerequisites

In order to get to the Learning Plan List page, a user must have at least one granted Role that contains the "Practitioner Area Access" permission. (This only affects the user's ability to get to the list page in the UI; features that start eligible Learning Plans programmatically do not consider this permission)
Learning Plans can only be started when they are published and have an active "Complete Learning Plan" Workflow

Scenario 1 - User is explicitly eligible

Learning Plan definitions state a Role and Role Status that make a Practitioner eligible to begin an instance. Any user that has a granted instance of that Role and Role Status is "explicitly eligible" to begin that Learning Plan and will see a "Begin" button on the Learning Plan List page.

In single-credential LearningBuilder installations this often results in an acceptable UX because all of the Learning Plans for that credential are made available to the global "Practitioner" Role (see sidebar). Thus, as long as the user has the ability to get to the Learning Plan List page, she will see a list of all available applications with a "Begin" button.

(Note: as of LearningBuilder 9.7, the "Begin" button can be hidden from users that are explicitly eligible to begin a Learning Plan. This is useful if you want specific applications to be created only via other system features, such as the "Auto Start Learning Plans" automation or the Learning Plan Instance workflow attribute.)

Scenario 2 - User is implicitly eligible

In some scenarios, Learning Plans may require a Role other than the global "Practitioner" role (see sidebar), but it's not always desirable (or feasible) to automatically grant those additional Roles to all users that qualify for them. For instance, NEED EXAMPLE HERE.

In these cases, users may satisfy the "real-life business rules" governing eligibility but not be explicitly eligible to start the Learning Plan according to the LearningBuilder configuration.

Since the Learning Plan List page is the default landing page for a newly logged-in front-end user, it often is desirable to include "Begin" buttons on that page for those applications. Users should not have to hunt through the system performing complex processes just to start those applications.

As of LearningBuilder 9.0, Learning Plan definitions can be configured to display a "Begin" button to users that are "implicitly eligible" to begin them. Users are "implicitly eligible" when they do not possess the Learning Plan's required Role, but they are able to begin a "Grant Role" Workflow that would provide that Role, and the Role's default Role Status satisfies the Learning Plan configuration.

Or in other words, users are implicitly eligible to begin a Learning Plan when they are not explicitly eligible to start it, but they are able to begin the process for becoming eligible.

When configured in this manner, the "Begin" button will be displayed on the Learning Plan List page. Clicking it launches the "Grant Role" Workflow popup. Once the user completes the Workflow, the Learning Plan Instance is created and the user is automatically redirected to the View Learning Plan page.

Known issue with the "Everyone" Role

A "Grant Role" Workflow that is configured to be started by the "Everyone" Role will NOT satisfy the "implicit eligibility" rules. However, a user with no explicit Roles other than the implicit "Everyone" Role cannot access the Learning Plan List page to begin with, so this is a non-supported configuration.

To work around this issue, configure the "Grant Role" Workflows to be started by the global baseline Role that you are using to grant access to the Practitioner area of the site (see sidebar).

LB-547 - Getting issue details... STATUS

Using a global "Practitioner" Role

Since a granted Role is required to get to the Learning Plan List page, most LearningBuilder installations include a "global" Role (often called "Practitioner") that all registered users of the system are given. This Role indicates that someone is a user of the system, but does not indicate the possession of any specific credential or license.

This Role is granted to users in different ways:

Via single sign on
Via /wiki/spaces/DOCS/pages/521306131 that automatically launch a "Grant Role" Workflow after registration is complete

Learning Plans that can logically be started by any user of the system are configured to require the "Practitioner" role.

Learning Plans that represent specialty designations or that only certain types of people are eligible to begin are configured to require those specialty Roles instead of "Practitioner".

Related articles

Page:
Learning Plan Eligibility (deprecated) (LearningBuilder Documentation)
- learning-plan-eligibility
- learning-plans
Page:
Learning Plan Instance Attribute (LearningBuilder Documentation)
Page:
API/LearningPlanInstance/GetOrCreate (LearningBuilder Documentation)
Page:
Update Cycle and Reporting Dates for Learning Plan Instance (LearningBuilder Documentation)
- workflow-behaviors
- learning-plans
Page:
Learning Plans a.k.a., Applications (LearningBuilder Documentation)
- learning-plans
- major-concept

Browser not supported