| Note |
|---|
Currently, if you run this report with a particular community selected, and you want to run it again without a community selected, you should create a brand new report instead of editing the existing report. This is temporary and will be fixed in a future release. |
The All historical learning plan completions report provides a list of past completions for recurring recurrent learning plans in a particular community. This report You can be used to see when each user last completed a recurring learning plansee a list of each user’s previous completions, including when they last completed it, and when the their next expiry and reset date for each user will occur.
...
Initial completions for recurring learning plans do not have reset dates, which You might generate this report to:
Check that all assigned users have completed a particular learning plan and are therefore compliant
Provide proof that users in your organisation have completed a particular learning plan for compliance purposes
...
Each user’s initial completion for a recurrent learning plans does not have a reset date. This means the Reset Date column in this report will be empty for each user’s initial completion. The initial completion is when the a user completes a recurring recurrent learning plan for the very first time once they’ve been after being assigned.
...
Configuring the report
The All historical learning plan completions report screen contains the following configuration fields:
Field | Description | ||
|---|---|---|---|
Report title (required) | Enter a title for the report. | ||
Select a community | Search for and select the relevant community.
To remove the selected community, click the x on the right side of the field.  | ||
Include deactivated entities | Select the Include deactivated entities checkbox to include content from users who previously existed in the community, but whose accounts have been deactivated. Users are typically deactivated by an organisation when they leave.
| ||
Start date and End date | Select dates from the Start date and End date calendars. For example, you might only include content that was created in the community between two specific dates.  | ||
Select fields to include in the report | Select data you want to include in the report/deselect data you want to omit from the report. For
 | ||
Filter the report (optional) | Narrow down the data displayed in the report by selecting one or more available filters.  | ||
How often would you like to run this report? | Select how often you would like to run the report. Example: You may only want to run the report once, or you might want to run it on a monthly basis to keep track of learning completion for users in the community. From the Run drop down, select one of the following:
Choose to stop the daily, weekly, or monthly creation of the report after a specific number of cycles, by selecting a number from 1-20 in the End after [#] Occurrences dropdown. If you have selected Daily, Weekly, or Monthly, you can choose to stop the daily, weekly, or monthly creation of the report after a specific number of cycles, by selecting a number from 1-20 in the End after [#] Occurrences dropdown. Example: If you set the report to run once per month, and you select 5 from the End after [#] Occurrences dropdown, the report will be created once per month for 5 months only, after which Fuse will stop creating the report. | ||
Who can access this report | In the Who can access this report section, specify the users or groups that will be able to access this report once it has been created. Select one of the following:
 | ||
Forwarding (optional) | Notify selected communities, or community members within those selected communities, once the report is created. Select one of the following:
 |
Report specific fields
The following standard Fuse data can be included or omitted from the report, by selecting or deselecting checkboxes in the Report specific fields section:
Field | Description |
|---|---|
User ID | The ID of the user that has been assigned to the learning plan. For example, a user’s user ID might be 556. |
Learning plan title | The title of the learning plan. |
Community ID | The ID of the community in which the learning plan exists. For example, the ID of a community might be 4793. |
Date course completed | The date the user last completed the learning plan. For example, 2022-07-13 13:07:54 UTC. |
The email address of the user assigned to the learning plan. | |
Family name | The surname of the user assigned to the learning plan, as recorded in their profile. For example, Smith. |
Last login | The most recent date in which the user signed in to Fuse. For example, 12/07/2022 14:28:38. |
Registration date | The date on which the user was assigned to the learning plan. For example, 12/07/2022 13:58:40. |
Learning plan ID | The ID of the learning plan to which the user is assigned. |
Reset Date | The date the learning plan is due to reset. Initial completions for recurring learning plans do not have reset dates, which Each user’s initial completion for a recurrent learning plan does not have a reset date. This means the Reset Date column in this report will be empty for each user’s initial completion. The initial completion is when the a user completes a recurring recurrent learning plan for the very first time once they’ve been after being assigned.   |
Community name | The name of the community in which the learning plan exists. |
Given name | The forename first name of the user assigned to the learning plan, as recorded in their profile. For example, John. |
Username | The username of the user assigned to the learning plan, as recorded in their profile. For example, john.smith. |
Last activity | The date and time the of the user’s last activity in Fuse. For example, this might be a social interaction in Fuse, such as liking or commenting on an item of content. For example, 13/07/2022 15:13:11. |
Terms accepted | Whether or not the user has accepted the terms and conditions when first signing in to Fuse.
|
...