New Features

  • New Skill / Competency System (optional)

    • Completely replaces the existing Skill / Competency system.

    • Both Skills and Competencies support multiple levels of achievement.

    • New “Requirements” system allows creation of packages of Skills / Competencies representing the skill-mix of job roles.

    • Flexible expiry system including Skill level decay.

    • Specify competency benchmarks on groups to track skills gaps and provide training goals for users.

    • Personal benchmarks allow for customized user goals and mentoring.

    • Catalog allows users and supervisors to browse published Skills / Competencies / requirements.

    • A new task type, Skill Verification, allows supervisors to rate and approve a list of skills for a user. These tasks can be initiated from both the supervisor and learner ends.

    • Requirements can be used to limit who can verify Skills.

    • Verification Builder tool provides a method for building Skill Verification tasks and finding a qualified supervisor with a shopping cart-style interface.

    • Revamped Skills Matrix report with expanded functionality.

    • Note: Existing customers using the legacy skill system will not be automatically upgraded, and will be able to continue using the current system.  We will be encouraging all customers to migrate over time. Please talk to your customer contact to find out more.

  • Locations

    • Xapiapps now supports a new object type called Locations.

    • Locations can be the target of audit checklists.

    • Locations can have designated managers (similar to ‘reports to’), and support Organization Structure.

    • Location visibility in security roles is controlled independently from Person visibility.

  • Audit Tasks

    • Audit tasks are a new type of checklist similar to Observation checklists.

    • The target of an Audit task must be a Location, and cannot be added to a pathway.

  • Bulk User Upload

    • Xapiapps now has a Person upload feature. This allows a CSV of people to be uploaded to add or update people in the system.

  • Task Visibility

    • Changed visibility rules to ensure that the owner (assigned person) of a task can always do the task regardless of their role and organizational unit scope.

    • The assigner of a task must still be able to see both the target (learner / location who the task is about) and owner (who is to do the task) and have the “assigner” or “owner” role (or a custom role with equivalent permissions).

    • Users restricted by organizational structure now have visibility on their direct reports even if they are in a different organizational unit.

  • Task Usage Restrictions

    • Checklist tasks in content authoring can now specify valid usage types.

    • Valid usage types are any of Pathway Step, Standalone Use, or Trigger Use.

    • These settings will be used to limit the list of tasks in various system dialogs to eliminate invalid options and improve clarity.

    • Additionally, for Standalone use, the author can prevent self-assignment of the task.

    • Note: When these flags are changed, the pathways and triggers which are already defined will continue to work.

  • Groups / Roles

    • A new group type, “Role”, has been introduced.  Roles are intended to be used to grant permissions to users.

    • Regular groups no longer confer any permissions to a user, and are to be used for other business rules, such as assignment, skill benchmarks, searchability etc.

    • For backwards compatibility, existing regular groups with roles are still being maintained.

Other New / Updated features

  • Administrative screens now require save / cancel when changes are made.  This prevents accidental changes or partial changes from being committed which can affect multiple users (for example, Skill expiry rules changing).

  • Group Training can now specify a location where the training occurred.  The location is also included in xAPI statements sent to any attached LRS.

  • Standalone tasks can now be unassigned, either administratively or if the person is the assigner of the task (self-assigned tasks).

  • Report Builder reports now allow display of archived result rows in addition to archived people.

  • Report Builder now allows reports to be published using multiple rules, providing more flexibility for publishing scenarios.

  • Task activity reports now include a filter for completion time.

  • Task activity reports now display completion timestamp in the task rows.

  • Task activity reports now allow filtering for expired status.

  • Skill status reports now show expiring and expired dates.

Performance / Misc Changes

  • Improvements to the task sign off process should result in faster response time for users completing tasks.

  • Dashboard Embed (external HTML) widget can now have a title specified.

  • Skills Matrix CSV (original version) generation has been changed to a different method to prevent users having to wait for file generation. In addition, the performance of the report should be improved.

  • Competencies (original version) no longer display expiry settings in the definition interface. These had no effect on competencies.

  • The “User Management” navigation menu item has been renamed to “Organization”.

  • Skill expiry (original version) has been changed so that “expiring” triggers still run if the Skill changes straight from “current” to “expired” as a result of the definition changing.

  • Task activity reports now use last user update timing for default sorting and filtering instead of system update time (which can change without user activity).

  • Task activity report CSV exports now include result status and score information where applicable (ie when assessments are scored and have a pass/fail status).

Bug Fixes / Improvements

 

  • Resolved an issue where assessment tasks could occasionally become stuck during the sign off process (and not complete without manual intervention).

  • Fixed a bug allowing users to enter an invalid Skill expiry notification.

  • Fixed a bug where pathways assigned by a person could not be completed if that person later has the “assign pathway” permission removed.

  • Archived Competencies now expire, so if they are unarchived later, they will display correctly.

  • Fixed a bug causing tasks for archived people to still display in the task view.

  • Fixed an issue causing assignment jobs to sometimes fail if more than ~20 recipients were chosen.

  • It is no longer possible to assign a Competency inside a pathway step (this behaviour was not intended).

  • Fixed expiry and notification period validation in the administrative Skill assignment dialog.

  • Fixed a display issue in assessment results preventing all Metrics from showing correctly.

  • Fixed a checklist bug preventing authors from selecting autofill based on questions within the same assessment.

Related Post

Leave a Reply

Xapiapps

© Training Evidence Systems Services Pty Ltd 2014-2020.

Stirling Business Centre
85 Mount Barker Road, Stirling
SA, Australia 5152