Overview

Behavior Fields configured in openSIS are actively used across the Behavior & Discipline workflow. Understanding where these fields appear helps administrators see the direct impact of their configuration choices.

This article explains where and how behavior fields are used in the system.

Primary Usage: Add Behavior Incident

Behavior Fields are displayed when staff record a new behavior incident:

Path:
Behavior & Discipline → Add Incident

All default and custom behavior fields appear according to their sort order and data type.

Editing Existing Behavior Incidents

When editing a behavior record:

• The same configured behavior fields are displayed

• Field values can be reviewed or updated

• Custom fields behave exactly like default fields

Student Behavior Records

Behavior Fields are used to:

• Display incident details in student behavior history

• Support administrative review and follow-up

• Maintain a structured behavior record over time

Administrative Review & Discipline Management

Administrators use behavior fields to:

• Analyze incident details

• Assign responsibility

• Record decisions and outcomes

• Ensure documentation completeness

Reporting and Audits

Behavior Fields support:

• Internal reviews

• Discipline audits

• Historical behavior analysis

Well-structured fields improve data clarity and traceability.

Important Notes

• Changes to behavior fields affect future incidents

• Existing data remains unchanged

• Deleting fields may impact historical visibility

Best Practices

• Review behavior fields periodically

• Align fields with school discipline policy

• Avoid unnecessary or redundant fields

• Ensure staff understands field usage