/
Pathways - Configuration Warnings

Pathways - Configuration Warnings

Owned by Seth Petry-Johnson
Last updated: Sept 23, 2023
3 min read

The Application Pathways page works best when LearningBuilder is configured according to a specific set of conventions. It will still work if your system does not meet these conventions, although some functions may be disabled and/or you may notice cosmetic issues.

Warning message

Explanation

Impact / How to fix

Warning message

Explanation

Impact / How to fix

“<Credential> is associated with more than one Role”

The Pathways page assumes that every Discipline represents a single, earnable Credential which is indicated by granting a specific Role.

This warning indicates that the Learning Plans within that Discipline have more than one “Required Role”, which may result in unwanted cosmetic issues on the Pathways page.

Impact

The Pathways page may show redundant Credential headers, especially if any of the related Credentials are featured in the sidebar. This is a cosmetic issue only; the page will be functional, but may look confusing.

How to fix

Reconfigure the Learning Plans within this Discipline so that they all use a a single Role

“<Learning Plan> has a Minimum Units requirement”

The Pathways page does not support Learning Plan Minimum Units when determining if the Practitioner has met submission requirements

Impact

Using these features will hide the Complete Learning Plan Workflow button from the Practitioner. The system will otherwise work as expected.

If you leave the legacy configuration in place, the Practitioner will need to view the full Learning Plan in order to submit the application workflow. This is consistent with how the legacy Learning Plan List page works.

If you reconfigure the system to use only the Requirements Model, then the Pathways page can display the Workflow button and Practitioners will be able to submit a completed application directly from the list.

How to fix

Convert the Learning Plan and Task Group level requirements into Requirements Model implementations instead using minimum units or minimum activities set to match the task group group setting and count activity types/activites that are allowed in the task group.

Convert Required Tasks into a Requirements Model implementation where there is a count of 1 required activity and only count actiivies that match the Activity ID of the required task.

“<Task Group> has a Required Units requirement”

The Pathways page does not support Task Group level requirements when determining if the Practitioner has met submission requirements.

“<Task Group> has a Complete Any requirement”

“<Task Group> has a Required Task”

The Pathways page does not support Required Tasks when determining if the Practitioner has met submission requirements.

 

Related content