v0.7.1
Action Types represent the specific type of action that a trainee performs during the scenario. Action types are part of a larger action string generated by GOAT as the trainee interacts with the simulation, and are used in Violation Triggers to determine if the action is a violation.
There are many different action types, each of which has a different format for its segments. Each simulator plugin defines its own action types, but there are a few that are global to all simulators.
The Check action is generated when a Check is fired.
Action String structure: Check:CheckName
CheckName: The name of the check that was activatedThe Messaged action type represents sending a message to a contact.
Action String structure: Messaged:Contact Name:Message Abbreviation
Contact Name: The name of the contact the trainee sent the message to.Message Abbreviation: The abbreviation used to identify which message was sent.The contact name and message abbreviation should correspond to an actual Communication in the scenario.
The NoActions action is generated when the trainee performs no actions at all. This typically only occurs if they start the scenario and immediately cancel it with the Done button.
Action String structure: NoActions
The Skipped action type isn't an action the trainee directly completed, but a consequence of other actions. It represents contributing to or completing an Accomplishment without having completed another Accomplishment.
Action String structure: Skipped:Skipped Accomplishment:Skipped Requirements:Completed Accomplishment:Completed Requirements
Skipped Accomplishment: The name of the accomplishment that was skipped.Skipped Requirements: The requirements of the Skipped Accomplishment that haven't been completed yet. Can be a list separated by a | character, or a substitution like ANY or ALL.Completed Accomplishment: The name of the accomplishment that was contributed to.Completed Requirements: The requirements of the Completed Accomplishment that have been completed. Can be a list separated by a | character, or a substitution like ANY or ALL.For most applications, the violation trigger should not care about requirements, and only if the accomplishments are completed or not. In those cases, the trigger would look like Skipped:Accomplishment 1:ANY:Accomplishment 2:ALL. This means that the requirements for Accomplishment 1 can be in any state as long as the accomplishment isn't completed, but Accomplishment 2 must be fully completed.