Prolydian Integration

Overview

LearningBuilder can integrate seamlessly with Prolydian to:

• Establish eligibility for a candidate to sit for an exam

• Obtain exam results from Prolydian 

• Dynamically update the candidate's application based on those results

The integration is enabled via a Workflow Behavior. It supports these Workflow types:

• Create Activity

Data Flow

1. When the Behavior is configured, administrator selects a Queue Template that controls the eligibility API payload sent to Prolydian, and an xAPI Event Handler which specifies what happens when results are received.
   

   

   
   
   

2. When a Workflow Action triggers the Behavior, the Message Queue is used to call the Atlas eligibility API. Prolydian is notified of:

   1. The Candidate Id, a unqiue identifier for the candidate themselves, and

   2. The Eligibility Id, a unique identifier which represents the authorization to sit for a specific exam administration. The Eligibility Id is determined by the Activity Instance. 
      
      

3. At some point in the future, after the candidate has actually taken the exam, Prolydian calls the xAPI API endpoint and provides an xAPI document representing the exam results. The configured handler is executed which parses the document, extracts the document, and maps its values to the Activity Instance as configured. (Note: technically, Prolydian calls an endpoint in the Integration Hub, which then forwards the request to LearningBuilder. This prevents exam results from being dropped if LearningBuilder is down for maintenance. The integration hub plugin is NOT client-specific)

   1. Workflow Attributes are updated with relevant pieces of the result data, per the Behavior configuration

   2. The appropriate Workflow Action is executed depending on the exam grade. (This typically moves the Workflow forward into the next step)
      
      
      

How to set up Prolydian integration for a new customer

Please complete for each customer. This will become a template so we can create one for each project with minimal hand-off between Implementation and Integration Support.

We need the following (Christopher made up this stuff, so someone needs to make it real (like Steve Ross, Scott Reed, or Mallory Bucell)

Configuration

Configure the Prolydian integration as follows ( Steve Ross needs to provide details):

1. Create a short text PTI ID on the Member Role, Learning Plan Instance, and the Exam Activity Instance.

2. If the issue where the Feature does not handle new vs existing candidates is not yet addressed, also add a picklist Yes/No attribute called PTI Existing to the Member Role, Learning Plan Instance and the Exam Activity.

3. Create a Template field call PTI - Computed on the Member Role with logic similar to

   @( Model.MemberRole.GetText("PTI ID").IsNotNullOrEmpty()
   ? Model.MemberRole.GetText("PTI ID")
   : "PTINIGPCPP8" + ("000000000" + Model.MemberRole.GetText("Unique Identifier")).Right(9)
   )

The prefix “PTINIGPCCP8” will be changed to whatever the PTI tells us it needs to be for the client. In this example the template also support PTI IDs assigned prior to launching in LearningBuilder and thus will not overwrite an existing value.

3. Include an Update Workflow Instace Attribute behavior on the Role Grant Workflow or an Update Member Role for Learning Plan behavior on the LPI workflow to set the PTI ID prior to exam eligibility.

4. Include a series of behaviors on the LPI prior to scheduling similar to below:

See  LB-2712 - Getting issue details... STATUS