The All content report allows lets you to create a report containing user completion data for learning plans that exist generate a list of content created in a community over a specific period of time. For example, you might want to see how many users in the community have completed a particular learning plan, as well as the date and time they completed it. retrieve a list of all the content created in a particular community between the 1st January 2019 - 1st January 2021.
Below is an example of the Learning plans completion report All content report:
Warning |
---|
We do not advise using the Learning plans completion report in the legacy Reporting screen. Currently, the data displayed in the Learning Plan progress score, Status of a Learning Plan (Not Started, In Progress, Completed), and Completion date(s) columns do not display accurate data. Instead, we strongly advise that you use one of the following:
|
This section includes:
Table of Contents |
---|
Configuring the report
The Learning plans completion report All content report screen contains the following configuration fields:
Field | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Report title (required) | Enter the title of the report. | ||||||||
Select a community | Search for and select the community containing the relevant learning plan(s)relevant community.
To search for and select a community:
| ||||||||
Select the 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, however the learning plan data associated with that user is retained.
| |||||||||
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.
The Select fields to include in the report section is divided into the following categories:
| ||||||||
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.
From the Run drop down, select one of the following:
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 thethe End after [#] Occurrences dropdown.
| ||||||||
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:
|
When you have finished selecting the options for the report, click Submit in in the top-right corner of the screen and the report is created.
Report specific fields
The following standard Fuse user data can be included or omitted from Learning plans completion report:from the report:
Info |
---|
The Date column, which shows the item of content's creation date, cannot be omitted from this report. |
Field | Description | ||
---|---|---|---|
The ID of the learning planitem of content. | |||
Content name | The ID name of the useritem of content. | ||
Content type | The user's given namecontent type. For example, John, Article, Question, Uploaded file, Video, or Scorm Course. | ||
The user 's Fuse username, used when logging in to Fuse. | |||
The date and time the user last interacted with the learning plan, such as viewing a module within the learning plan. For example, 2020-06-02 15:27:34. | |||
If the user has accepted the terms and conditions when first logging in to Fuse. | |||
The percentage of the learning plan completed by the user. For example, if the user has completed 50% of the learning plan, 50 will be displayed. | |||
The title of the learning plan. | |||
The email address associated with the user's Fuse account. | |||
The user's family name. For example, Smith. | |||
The last date and time the user logged in to Fuse. For example, 2020-05-06 09:09:56. | |||
The date the user was assigned to the learning plan or it was made available to them. | |||
Whether or not the user has completed the learning plan. One of the following statuses will be displayed:
| |||
For example: 2019-07-05 10:00:50. This column will be empty if the user is not currently at 100% completion. Examples:
| |||
Learning plan completenesses | Displays all dates/times the user has reached 100% completion. If the user has successfully completed 100% of the learning plan twice, two dates/times will be displayed, separated by a comma.ID of the Fuse user who currently owns the item of content. | ||
Views count | The number of times the item of content has been viewed in Fuse. If a single user has viewed the item of content multiple times, each view is counted. | ||
Likes count | The number of times the item of content has been liked. | ||
Shares count | The number of times the item of content has been shared. | ||
Comments count | The number of comments that appear underneath the item of content in Fuse. | ||
Unique views count | The number of unique user views the item of content has. For example, if you have 100 users in the community and all 100 users have viewed the item of content, the count would be 100. | ||
Time | The time at which the item of content was created.
| ||
Community ID | The ID of the community where the content was created. | ||
URL of content | The URL of the content, rendered as a clickable link. | ||
Owner name | The first and last names of the Fuse user who currently owns the item of content. | ||
Owner email | The email address of the Fuse user who currently owns the item of content. | ||
Owner username | The username of the Fuse user who currently owns the item of content. |