FrogLMS Community

What's new in this release?

MODULES - SECONDARY APPROVAL GROUP

We've introduced an enhancement to the two widgets below that will allow for submissions to be approved either your manager or a specified approval group.

• Task File Submit
• Task Text Submit
   

In addition, it is also possible to have a secondary approval level (group), allowing for a two-step approval process.

After a submission has been initially approved, it will then be passed to the secondary approval group for subsequent approval.

This improvement provides the flexibility to grant subject matter experts, department heads and or Learning &Development teams the ability to verify submissions, if required.

For more information, please contact the Service Desk who can provide the additional document “Modules - Secondary Approval Group”.

TASK APPROVAL WIDGET

The Task Approval widget has been redesigned to enhance the interaction between learners and managers. When submissions are made via the “Task File Submit” or “Task Text Submit” widgets, managers or a specified approval group will see the following changes:

• Feedback Provision - Managers can provide feedback on submissions, which will be visible to the learner.
• Submission Filtering - The Task Approval widget can filter submissions using the following options, with "Awaiting Approval" set as the default view:
  • Awaiting Approval
  • All
  • Approved
  • Rejected
• Search Functionality - A search field has been added, allowing users to search for a user or module based on the selected filter.

BUG FIXES

This release includes the following bug fixes:

Modules

• JIRA# NFC-3075 - When duplicating a module that contains a quiz, the link between the duplicated module and duplicated quiz will be retained, ensuring any learner submissions are correctly reflected when navigating to the Module > Show Quiz Reports.
• JIRA# NFC-3059 - Upon discussions with several LMS customers a change has been made when setting the “Due Date” of a module. When the “Due Date” toggle is set to “ON” the following can be set:
  • Due Date – This will be a fixed date applied to all users allocated the module.
  • Relative Date – This allows the due date to be set based on when the module is allocated to a learner. Previously this was based on a learners start date.
    
    
    
    Any modules that were using this field will have the data migrated accordingly. The feedback from customers was that they wanted to provide learners with the same amount of time to complete a module no matter when their start date within the organisation is. The small change to this setting will now facilitate this scenario.
• JIRA# NFC-3048 - Within a module, when navigating to “Add to Catalogue” if a date is set for the “Until” field, this can now be deleted by clicking into the field and deleting the date if required.
• JIRA# NFC-2833 - Modules that have CPD hours or skills settings configured can now be duplicated successfully.

Reporting Application

• JIRA# NFC-3073 - For the Department Compliance Report, when selecting a department, the report will generate the correlating data as expected.

Sites

• JIRA# NFC-2607 - When the Vimeo widget is placed on a site that is shared as “Public on the web”, the content associated with the Vimeo widget will be displayed.

System Preferences > Training > Notifications

• JIRA# NFC-2841 - Within System Preferences, the Notifications area (within the Training section) now only allows users to set the hour when reminders are sent to users. This is a scheduled background task that can only be run on the hour.

Users Application

• JIRA# NFC-3062 - Within the Users application, when entering a leaving date for a user this will now be saved successfully. This issue only occurred for users whereby their line manager had been archived.