Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

You can download data related to events and event participation from the Events tab, in the form of reports

The following reports can be downloaded:

All Events report

A list of events created in Fuse, including each user's approval status for the event, the total number of available seats, total number of approved users, total number of users attending, and the total number of users who applied. 

The following information is included: 

HeaderDescription
Event IdThe unique identifier of the event. 
Event NameThe name of the event. 
Occurrence Id

The unique identifier of one of the specific event occurrences created for that event. 

Example: An event called "Company update" might have a different occurrence for each regional office (London, San Francisco, Tokyo), with agendas specifically tailored to each one. In this case, the event organiser could add a unique description for each regional occurrence outlining the agenda. 

Occurrence NameThe name of one of the specific event occurrences created for that event. 

Example: An event called "Company update" might have an occurrence for each regional office (London, San Francisco, Tokyo), with agendas specifically tailored to each one. In this case, the event organiser could add a unique description for each regional occurrence outlining the agenda. 
LocationThe location of the event. This might be a physical location such as a street address, or a link to a virtual meeting room, such as in Google Hangouts, Zoom, or Microsoft Teams.
Date (Start)The date the event starts. 
Date (End)The date the event ends.
Community IdThe unique identifier of the community where the event was created. 
User IDThe unique identifier of the user attending the event. 
Prerequisite Learning Completed 

Has the user completed the prerequisite learning, required before attending the event?  In some cases, the event creator may require users to study something prior to attending the event. 

The following can be displayed: 

  • Yes: Yes the user has completed the required prerequisite learning before attending the event. 
  • No: No the user has not completed the required prerequisite learning before attending the event.
Approving creator

The name of the event creator, who has been given the ability to approve the user to attend the event. 

When creating an event, you can decide who approves users to attend. This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the /wiki/spaces/Fuse/pages/1208386049 screen.

Approving Manager

The name of the user's manager, who has been given the ability to approve the user to attend the event. 

When creating an event, you can decide who approves users to attend. This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Approving Specified

The name of a user, selected by the event creator, who has been given the ability to approve the user to attend the event. 

When creating an event, you can decide who approves users to attend.This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Events - Occurrence costHow much it costs to attend the event. 
Events - Total seatsThe total number of available seats at the event. 
Events - Total ApprovedThe total number of users approved to attend the event. 
Events - Total Attended

The total number of users who attended the event.

Events- Users appliedThe total number of users who have applied to attend the event. 

All Event Participation Requests report

Contains participation details for each event created in Fuse, including the details of each user who has applied to attend and their approval status. 

The following information is included: 

HeaderDescription
Event IdThe unique identifier of the event.
Occurence Id

The unique identifier of the relevant event occurrence created for that event. 

Example: An event called "Company update" might have a different occurrence for each regional office (London, San Francisco, Tokyo), with agendas specifically tailored to each one. In this case, the event organiser could add a unique description for each regional occurrence outlining the agenda. 

Occurrence NameThe name of one of the specific event occurrences created for that event. 

Example: An event called "Company update" might have an occurrence for each regional office (London, San Francisco, Tokyo), with agendas specifically tailored to each one. In this case, the event organiser could add a unique description for each regional occurrence outlining the agenda. 
User IDThe unique identifier of the user who applied to attend the event. 
User NameThe name of the user who applied to attend the event. 
User E-mailThe email associated with the user's Fuse account. 
Learning Needed

Does the user need to complete prerequisite learning before being able to attend the event? In some cases, the event creator may require users to study something prior to attending the event. 

The following can be displayed: 

  • Yes: The user must complete the required learning prior to attending the event.
  • No: The user does not need to complete any required learning prior to attending the event.

Prerequisite Learning Completed

Did the user complete the required prerequisite learning before being able to attend the event. In some cases, the event creator may require users to study something prior to attending the event. 

The following can be displayed: 

  • Yes: The user has completed the required prerequisite learning. 
  • No: The user has not completed the required prerequisite learning. 
Approving Creator

The name of the event creator, who has been given the ability to approve the user to attend the event. 

When creating an event, you can decide who approves users to attend. This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Approving Manager

The name of the user's manager, who has been given the ability to approve the user to attend the event.

When creating an event, you can decide who approves users to attend.This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Approving specified

The name of a user, selected by the event creator, who has been given the ability to approve the user to attend the event. 

When creating an event, you can decide who approves users to attend. This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Creator Approval

Has the event creator approved the user to attend the event? 

The following can be displayed: 

  • N/A: Approval to attend the event was not required. 
  • Approved: The user was approved to attend the event.
  • Pending: The user's application to attend the event is pending and has not yet been approved. 
  • Declined: The user's application to attend the event has been declined. 
Manager Approval

Has the user's manager approved the user to attend the event?

The following can be displayed: 

  • N/A: Approval to attend the event was not required. 
  • Approved: The user was approved to attend the event.
  • Pending: The user's application to attend the event is pending and has not yet been approved. 
  • Declined: The user's application to attend the event has been declined. 
Specified Approval

Has the specifically chosen user approved the user to attend the event?

  • N/A: Approval to attend the event was not required. 
  • Approved: The user was approved to attend the event.
  • Pending: The user's application to attend the event is pending and has not yet been approved. 
  • Declined: The user's application to attend the event has been declined. 

The event creator can decide who can approve a user, when they apply to attend an event. This can include the event creator, the user's manager, or a specifically chosen user. 

This is done in the Applicant Approval section of the Creating a new event screen.

Date (Start Date)The start date of the event. For example, 09/02/2020. 
Date (End Date)The date the event ends. For example, 09/04/2020.
Events - Users appliedThe total number of users who have applied to attend the event.
Events - Total AttendedThe total number of events the user has attended. 
Events - Total appliedThe total number of events the user has applied to attend. 
  • No labels