Configuring Incident Types / Customizing Templates

Above the menu is the general set up area.

1. Set the motivation "Display Name" name as it appears on the incident template.
2. Set the Types per Incident Limit, which represents the max number of behaviors that can be created/entered on each incident.
3. Set the Incident Response Limit, which represent the max number of responses that can be created/entered on each incident.

Click once on Types to identify the incident types needed.

1. Click Add to create a new incident type and type the new incident name in the field box that pops up.
2. Click Edit to rename or delete any existing incident types. Use the check boxes that populate to the left to select the incident type to edit.

To manage an incident's specifics, click on the name of the incident. The settings page opens for that incident which includes General, Custom Fields, and Section Properties.

1. If this setting is on, all descriptions for this incident type will be hidden to staff members - individuals with a permission to view restricted incident descriptions will be able to see the descriptions.
2. If this setting is on, incidents will be open by default (they will be sent to an Open Incidents section on administrators dashboards).
3. If this setting is on, incidents will appear on your weekly view dashboard automatically and will show by default under Visualization > Incidents (located on your home dashboard).
4. If this setting is on, this incident type's data will appear on the achievement Dashboard.
5. If this setting is on, an automatic email notification will send to a specific individual(s) containing all details of the incident when it is saved.
6. Choose any Schools that should have the option to use/see this incident type. If no schools are specified, all schools in the district have access.
7. Choose any Groups that should have the option to use/see this incident type. If no groups are specified, all groups in the district have access.

When an incident type is restricted to one or more user groups (or schools), only users in the group(s) added will see the incident data throughout the system. Above is an example of a "Health Office Visit" incident type being restricted and what the system looks like when users have access to see the incident data and what the system looks like when users do not have access to see the incident data.

	When users have access	When users do not have access
District, Grade, Class search
Student Profile
Incident Search

Click Create Field to create a new custom field for the specific incident.

1. Type the label of the custom field here.
2. Click the down arrow to choose the field type.
3. A preview of what the field will look like when creating an incident will appear to the right.
4. Click Save.

1. Once the custom field is added, you will see the field(name) and field Type.
2. The Options column indicates the number of options available for the custom field.
3. List Fields are the only custom field that generates multiple options. The specific options can be entered by clicking the number value.
4. Turn this setting on if you want the custom field to appear in incident charts.
5. Turn this setting on if you want the custom field to be included in exports of incident data
6. Turn this setting on if you want the custom field to be active and available when creating the incident type you are editing.
7. Turn this setting on if you want users to be required to fill out the field before saving/closing an incident.
8. The 3 dot menu allows you to delete or create an alias for the custom field.

When incidents are manually added to eduCLIMBER, specific sections may make sense to display while other may need to be hidden. There are four sections that can be customized for each incident type:

1. Description - This section will allow users to type text into a field detailing the description of the incident.
2. Motivation - This section will provide a field where users can select an option from a list of pre-defined motivations.
3. Response - This section will provide a field for users to add a response to the incident. It also provides an option to mark the incident as complete.
4. Parent Contact - This section provides a contact date field and a comment field were users can add notes for parent/guardian contact.

For any section within an incident type, identify how the sections should function. Three options exist for each section:

• Hidden - if a section is marked as hidden, the full section will not display on the screen when entering an incident into eduCLIMBER.
• Optional - if a section is marked as optional, the full section will display on the screen with the text (optional) next to the section header. This will allow users to enter data for that section, but data entry will not be required in order to save the incident.
• Required - if a section is marked as required, the full section will display on the screen with an asterisk. Users will be prompted to enter data in order to save the incident.