Behavior Modal

Owned by Felicia Mizgorski
Last updated: Mar 25, 2024
5 min read

Overview

The Behavior Modal allows User to enter integration metadata, define benchmark criteria and map fields from their data set to the required fields.

Figma: https://www.figma.com/file/pbkupX2noQxD6SE6C7EtIv/Admin---Integrations?type=design&node-id=225-3432&mode=design&t=cRK3CpAFsEPZ0XXx-0

Epic:

UI Description: Add New Integration

  1. Subject dropdown:

    • Description: The subject selection for the new assessment

    • Required: Yes

    • Type of Input: dropdown selection

    • Validation Criteria: From the list, Attendance is selected

      • Contains alphabetical list: Attendance, Behavior, ELA, Math.

  2. Company dropdown:

    • Description: Company dropdown is a smart search containing an alphabetical ordered list of all companies that have at least one integration for the selected subject

    • Required: Yes

    • Type of input: Smart search results from dropdown or text entered for a new company

      • Search results are optimized to appear within 2 seconds under normal load conditions.

    • Validation Criteria: Selection is a selection from the smart search dropdown or a text entry

  3. Assessment Name:

    • Description: Name of the Assessment

    • Required: Yes

    • Type of Input: Text entry with no character limits

    • Validation Criteria: Text entry with at least 3 characters

  4. Description:

    • Description: Text entry field for user to provide a description of the Assessment

    • Required: No

    • Type of input: Text entry

    • Validation Criteria: None; optional field

User Interaction and Validation Notes: Add New Integration

  1. Subject dropdown:

    • Subject drop down is single select, required field

    • User select Attendance integration

  2. Company dropdown

    • Users can refine the companies displayed by typing in the search bar or selecting options from dropdown filters.

    • The search function should validate input and return relevant results.

    • Users select Custom and text enter a new Company

  3. Assessment Name:

    • Users can click inside of field and text enters name of assessment

  4. Description:

    • Clicking inside the field makes it active.

 

UI Description: Integration Settings Benchmark Tab

  1. Incident Occurrences

    • Description: The user determines the range of incident occurrences for assignment to Tier Mapping

    • Required: Yes

    • Type of input: Dropdown selection

      • Default settings are:

        • Tier 1: 0 to 4

        • Tier 2: 5 to 9

        • Tier 3: 10

      • Dropdown contains: integers 0-200.

      • Tier 1 low range is locked at 0

      • user clicks on down arrow in fields to select ranges each Tier

    • Validation Criteria:

      • User must select a range for each of the Tiers

      • Tier 1 has the lowest number of incidents

      • Tier 2 has the middle number of incidents

      • Tier 3 has the highest number of incidents

    • Tier Mapping default settings include:

      • 3 Tiers labeled as Tier 1, Tier 2, Tier 3 and are locked

  2. Return Students to Tier 1:

    • Description: User selects the number of weeks they want to have pass without any incidents so that the student is returned to Tier 1 status after the selected elapsed time.

    • Required: Yes

    • Type of input: Dropdown

    • Validation Criteria:

      • If default is left unchanged, then 9 weeks is applied as the default to the Settings in MTSS Dashboard

      • If a change is made, then the selected number of weeks is applied as the default to the Settings in MTSS Dashboard

      • Users click on arrow and select from range of 1-36

 

User Interaction and Validation Notes: Integration Settings: Benchmark Tab

  1. Incident Occurrences

    • Dropdown selections contain list of integers from 0 to 180

    • Ranges are lowest for Tier 1 and highest for Tier 3

    • Dropdown contents adjust to User's selection by removing the incident occurrence range chosen for Tier 1 as User completes Tier 1 and moves onto Tier 2.

    • Dropdown contents adjust to User’s selection by removing the incident occurrence range chosen for Tier 1 and Tier 2 as User completes Tier 3.

    • Ranges selected are all inclusive and mutually exclusive

    • Error message shows if a selection is not made for incident occurrence range of each Tier

  2. Tier Mapping

    • Tier Mapping is locked as Tier 1, Tier 2, Tier 3

  3. Return Students to Tier 1

    • Default shown to user is: 9

    • Dropdown contains integers from 1 to 36

    • The value selected represents weeks.

 

UI Description: Integration Settings Field Mapping Tab

  1. Upload Sample Template

    • Description: Button uploads the heading of the data set selected and prefills the Select field drop down with those headings so User can pick which fields they want mapped

    • Required: Yes

    • Type of input: file

    • Validation Criteria: If completed, show success message that reads: file uploaded

  2. Required Fields:

    • Description: List of fields required by RethinkEd to show User’s data into MTSS Dashboard

      • Required fields are: StudentID, Incident Date

  3. Show Tooltip:

    • Description: Optional checkbox with default as unchecked

    • Required: No

    • Type of input: Checkbox

    • Validation Criteria:

      • If checkbox is selected, then we show the Tool tip text entry box

  4. Select Field:

    • Description: Dropdown contains the headings from Upload Sample Template

    • Required: Yes

    • Type of input: Dropdown selection

    • Validation Criteria: A selection is made the conforms to criteria for a StudentId, Incident Date

  5. Add Note:

    • Description: An optional selection that provides User a text box to text enter a note about the field that was selected; no character limits

    • Required: No

    • Type of input: Textbox

    • Validation Criteria: None; not required

  6. Add Custom Field:

    • Description: Opens an additional line to Custom enter the Field, optional text entry field description, Show Tooltips checkbox, Select field dropdown, and Add Note.

    • Required: No

    • Type of input: Button input

    • Validation Criteria:

      • If selected, then User needs to Name the field, include a text description, determine if a tooltip will be used, select a field from their data set and determine if Add note will be included

      • If not selected, then no Validation Criteria is need

  7. Save button:

    • Description: Saves all work completed

    • Required: Yes, if User wants the work completed

    • Type of input: button

    • Validation Criteria:

      • If selected, then all work is saved

      • If selected and their are fields that have not been completed, then we show error message around the field that reads: Required field

  8. Cancel button:

    • Description: Removes the most recent completed work.

    • Required: Yes, button is necessary but may not be selected by user

    • Type of input: button

    • Validation Criteria:

      • If selected, then the more current entries are removed and the previous entries shown.

      • If selected and no previous entries have been entered, then the default/empty state is shown.

      • If not selected, then no validation is needed

 

Start Here

User Interaction and Validation Notes: Integration Settings: Field Mapping Tab

  1. Upload Sample template button: Required: csv,

  2. Required Fields: must have selection or error message shown.

    • Error message reads: Required field

  3. Show Tooltip: optional, shows text entry box when clicked

    • Given Show Tooltip is selected, then the text box entry is required

    • Textbox entries have no character limits

  4. Select Field: Require, dropdown contains all of the labels from the uploaded sample template

    • Single select

    • Must agree with the data type for the required fields (string, integer, float, boolean)

  5. Add Note: Optional; shows text entry box when clicked

    • No character limit

    • Save selected, then note is shown below Select field

    • Cancel selected, then the note is removed and Add not function is restored

  6. Add Custom Field: optional, if selected shows fields to text enter: Custom Label, Custom Description, Show Tooltip, Select Field, Add note

    • If selected, then Custom Label, Custom Description, and Select Field are required

    • If selected, can be removed by clicking on x to remove the line.

  7. Save button: Save button saves the updates made

  8. Cancel button: Cancels updates made

 

Workflow Description

  1. Add New Integration Metadata

    • Users selects the Subject as Behavior and selects or text enters the company, assessment name and optional description

  2. Establish Benchmark Criteria

    • User selects ranges for Incident Occurrences for each of the tier levels and selects the number of weeks that pass without any incidents the student must attain to be returned to Tier 1.

  3. Map Required Fields to Data set

    • User uploads Sample Template and matches data set to required fields. Options to add tooltip, notes and custom fields are also available.

  4. Save New Integration

    • User selects Save button to complete the new integration and new integration is added to the Assessment List page