Civica Learning Release - 8th March 2023

Attempts support for events

The Event content type has been enhanced to support implicit attempts. With the new support for attempts, it is now possible for a user to attend an event multiple times, with each attempt being included in reports, and the rolled up session level status reflecting the status for the current attempt. 

In each new attempt, a user is required to attend another session to mark the event as Attended. This enables you to support scenarios where a user must attend an in person/online course each year, for example for compliance training. 

As part of this support, the following changes have been made in the Administration portal:

• When configuring the content within a curriculum, you can now select Start New Attempt for an Event content item included within a curriculum. When this is selected, a new attempt will be started on the Event, whenever a new attempt is started on the curriculum.
  
• When configuring renewal for a certification, you can now select an Event as the renewing item. When a user begins renewal of a certification, a new attempt will be started on the Event (where the Event is currently Attended).
  
• The Users > {User} > Content page content dialog, has been updated for Event items to display the user's attempts. 
  
  The Current attempt tab shows the users current status, as is displayed to the user in the learner portals. A user who has previously attended a session for the event can be in the Not started state, where they have not yet attended a session within their current attempt. 
  
  
  
  The Attempt history tab, shows all of the user's Attempt history for the Event, with the date/times the user has completed previous sessions. As an administrator, you can also start a new attempt for the user, or clear all of their attempt history, from this page.
  
  
  
  

Bulk user import enhancements

The bulk user import feature has been enhanced to better support importing user records with line managers or approvers specified in the import. 

Previously, it was necessary for a line manager or approver to have been added to the system, before they could be specified in an import as the line manager or approver for another user. Where both the line manager and/or approver were being added in the same file as their associated user, an error was generated, indicating that the specified line manager and/or approver does not exist. A work around for this involved first importing the users without including their line manager and approver properties, and subsequently importing the users with line manager and approvers in second import, to add the additional information. 

This update removes this requirement. The check that a user specified as a team leader or approver exists, now validates both against existing users on the system, and against users who are being added as part of the current import. This update also handles scenarios where the username for a team leader or approver is also being changed in an import. 

User administrator role enhancement

The User Administrator role has been enhanced to enable User Administrators to change the username of a user. Previously, only Global Administrators could change usernames for existing users. 

The ability for a User Administrator to modify a user's username is controlled by a new option Allow user administrators to rename users on the Settings > Advanced page, in the Administration portal. Global Administrators can configure this option for their organisation. By default, the editing of usernames by User Administrators is disabled, so there is no change to existing functionality/role restrictions, unless you choose to enable this feature. 

Bug fixes

Various bug fixes.