Nested Applications (Facility Certification with "Key Staff")

Owned by Seth Petry-Johnson
Last updated: Apr 18, 2019

Summary

This is the use case for the Learning Plan Instance data type. It allows one application to be dependent on the status of other applications.

For example, an industrial facility may apply for a certification stating that they meet specific environmental regulations. As part of that application, the facility may need to identity key personnel that fill required roles, each of whom must possess a specific individual credential. This use case describes how the facility's application can be linked to the individual applications and be prevented from moving forward until the key staff have all obtained their required credentials.

User Stories

StoryNotes
As a representative of the facility or Site, I want to visualize my staffing requirements as part of the site's application.

Task Groups, with an Activity Instance representing each staff position that needs to be filled

As a representative of the facility or Site, I want to be able to select Key Staff that do not already have the required individual credential, but are eligible to begin it. I would like the individual's application to be started and linked to the overarching Site application so that I can keep tabs on the staff member's progress.Provided by the Learning Plan Instance attribute on the Complete Activity workflow
As a Program Administrator, I want to be able to prevent the Site from submitting its application until all of the subordinate (linked) individual applications have been completed. (In other words, I want to prevent the site from submitting its application for review until all of the Key Staff have fully earned their required credentials).Can be configured using the /wiki/spaces/DOCS/pages/579829815 on the Learning Plan Definition. 


Technical Design

This use case is comprised of the following features:

  • A Learning Plan Definition representing the credentialing process that the facility (or "Site") must complete.

  • One or more individual Learning Plan Definitions representing the credentialing process that the individual "key staff" must complete as part of the overarching Site application.

  • A Learning Plan Instance Attribute on the Site's application (or on an Activity added to that application) for each Key Staff member that must be identified.

For more information on configuring this use case, see the Learning Plan Instance attribute page.


Prerequisites

  • LearningBuilder 9.7 or later

Known Limitations:

  • The implementation in 9.7 only works for Key Staff that do NOT already have the required credential. It may need minor adjustment before it can support scenarios where the Site is selecting from a list of people that already have the credential.