Competency Re-issuance Behavior After Status Revocation

Applicable Product:

PeopleFluent Learning

Applicable Release:

V25


Overview

When a competency is revoked due to a program or module status changing back to In Progress, administrators may expect the competency to be automatically re-awarded once the program or module is completed again.

This article explains how the system handles competency revocation when Enable Competency History is active and provides steps to re-award competencies in this scenario.


Technical System Behavior

  • Function of 'Enable Competency History': When the System Configuration setting Enable Competency History is enabled, the LMS retains revoked competencies in the database and allows re-awarding only when completion requirements are fulfilled after the revocation date.

  • Impact of Existing Completion Dates: If a program's completion status is manually reverted to In Progress and then returned to Completed (or processed via the Person Information Processor/PIP) using historical completion records, the system detects that the completion date predates the revocation date. As a result, the competency status remains Revoked.


Step-by-Step Solutions & Workarounds

Depending on your organization's configuration and preferences, use one of the following methods to re-award the competency:

Method 1: Update the Completion Date After Revocation (Recommended)

  1. Ensure the assigned module/program reflects a new completion event that occurs after the revocation timestamp.

  2. Manually complete or update the assigned module/program status back to Completed so the database records a fresh completion date after revocation.

  3. The system will evaluate the new completion date against the revocation date and automatically mark the competency as Completed / re-awarded.

Method 2: Temporary Configuration Adjustment

  1. Navigate to System Configuration.

  2. Temporarily disable Enable Competency History.

  3. Set the assigned module back to In Progress and run the Person Information Processor (PIP).

  4. Re-enable Enable Competency History once the competency status updates.

Was this article helpful?

0 out of 0 found this helpful