Programme builder: Troubleshooting guide

Does renaming a user custom field in a programme update the field for the learners currently enrolled on the programme?

Yes, the updates to a custom field via the programme configuration will pull through for every learner on that programme. However please note that it will also apply the change to learners on other programmes if those programmes are using the same custom field.

 

I’ve created an assignment task type component without a completion date via Classic. When I try to mark this component as complete, why does it reverts to a status of "not started.

For an Assignment task type component, a 'Complete By' date must be set when creating this component in Programme Builder via Classic. This date serves as the due date for the task. Without this date, the system cannot auto-create the associated task. The component can only be marked as complete once the task has been created and completed. 

complete by.png

Further details can be found at: Why is an Assignment Task still showing as “Not Started” when evidence has been submitted by the Learner?

 

Why is the Skills Radar in Console displaying as blank for learners even after completing a skill scan?

This issue may arise when there are no competencies configured in the 'Competencies' token of the programme build to which the learner is enrolled.

To resolve this, follow these steps:

  1. Access the programme build in classic interface.
  2. Navigate to the 'Competencies' token.
  3. Begin typing the competency's name in the search box.
  4. Select the required competency and click on the '+Add Competency' button.

sk.png

After updating, check the learner’s profile in Console, and the Skills Radar will now showcase the competencies configured in the programme.

Please be aware that the Skill Radar section only displays competencies associated with the learner's current programme. If you wish to view competencies completed in previous programmes, you must add them to the current programme by following the aforementioned process of adding competencies to a programme.

 

Learners are unable to see a criteria set even when this setting has been enabled in the Programme builder. Why is this?

The attributes of a programme are only applied to a learner when the programme is applied to their record.

If the criteria was not set to be visible for learners at the time of enrolment, then learners currently enrolled will not be able to see the criteria.

Changing the visibility settings after enrolment will not allow the currently enrolled learners to see the criteria as this change will only apply to learners enrolled after the update. However, it is possible to control the visibility of criteria sets at learner level via the Learning Plan in Classic.

show.jpg

 

Changing EPA length in the programme builder (Programme Requirements Token) has updated Apprenticeship End date for all the learners on the programme. Is it possible to do this for new learners only?

Changes at programme level for EPA duration will impact all learners (including existing learners). This is by design.

If you want an EPA duration change to only apply to new learners (certain set of learners), then you will need to create a new programme (we would recommend cloning the existing programme) with required EPA duration set and enrol these learners onto this new programme.

 

How can I remove an incorrect standard or criteria set from a programme?

This depends on whether the programme has live learners enrolled.

If there are live learners on the programme:
You cannot remove a standard or criteria set directly. Raise a support ticket or speak to your Customer Success Manager, who can assist with removing the incorrect standard.

If there are no learners on the programme:
You can remove the standard or criteria set from the programme configuration directly within the Classic interface. Navigate to the programme in Classic and edit the relevant settings.

 

Why am I unable to delete a programme?

If you see an error when trying to delete a programme, it is likely because the programme is currently set as the default programme for one or more groups.

To resolve this:

  1. Navigate to the Groups tile in the Classic interface.

  2. Identify any group where this programme is set as the Default Programme.

  3. Remove the programme from the Default Programme field for each affected group.

  4. Once the programme is no longer set as a default for any group, you will be able to delete it.

Was this article helpful?
0 out of 0 found this helpful