Learn how to setup Events to model errors in your Procedures, or to allow your users more free-form interactions within the training.
Whereas Steps define the main flow of the Procedure, where the trainee must complete each Step to progress to the next, Events are used to define possible interactions running alongside the main Steps of the Procedure. Events are often used to describe potential errors the trainee can accidentally make during the Procedure.
Events are defined in the Events tab of the Procedure Builder interface – add a new Event using the small blue ‘+’.
As the user is working on defining an Event, the scene will reflect the current state of the event – without taking other Events into account. It is also possible to select ‘Simulate as a sequence’ so all Events are simulated one after the other, resulting in the state of the event taking past Events in the list into account.
Users can configure the following in an Event:
- Activate trigger: Specify how many trainees are needed to activate the Event. Choose between "When one player activates" or "When all players have activated".
- Deactivate trigger: Specify how many trainees are needed to deactivate the Event. Choose between "When one player deactivates"’ or "When all players have deactivated".
- Is error: Let the system know if the Event is to be treated as an error. When a trainee completes the Procedure through the LMS integration, a score board is shown at the end summarizing how many errors were triggered.
- On enter actions: List of Actions that will be executed when the Event is enabled as result of a "Toggle event" Action.
- Activate operations: Defines the Operations the trainee must perform to activate the Event. Multiple Operations can be defined – unlike for Steps where multiple Operations must all be performed to proceed to the next Step, when the first of these are performed by the trainee the Event is activated.
- On activate actions: List of Actions defining how the system responds to the user activating the event.
- Deactivate operations: Defines the Operations the trainee must perform to deactivate the Event. Multiple Operations can be defined – when the first of these are performed by the trainee the Event is activated.
- On deactivate actions: List of Actions defining how the system responds to the user deactivating the event.
- On exit actions: List of Actions that will be executed when the Event is disabled as result of a "Toggle event" Action.