Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
titleSummary

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


Additional Behaviors

Actions can be configured to trigger additional Workflow Behaviors as well, which are often used to implement custom business rules

Overview

Primary Behaviors

Actions have a "Primary behavior" that specifies how the Workflow itself is to be modified:

Complete Successfully / Unsuccessfully: Moves to the Workflow to one of the terminal states indicating that it was completed as expected, or not.
Move Next / Move Previous: Moves to the next or previous Workflow Step, in sequence.
Move To Step: Moves to a specific Step, regardless of its place in the sequence.
  • Save: Updates the Workflow Attributes according to the form post or incoming data, but otherwise makes no changes to the Workflow status or step.
  • 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

    Multi-credential LearningBuilder installations may require additional configuration to provide a pleasing user experience.

    In these systems, some Learning Plans 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.

    However, 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 all applications where the user satisfies the "real-life business rules" governing eligibility. 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.

    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:

    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".


    Filter by label (Content by label)
    cqllabel = "workflow-actions"

    Page Properties
    hiddentrue


    Related issues