Purpose
Preserve deprecation lineage and prevent accidental reactivation of outdated communication workflows.
Current state
Integr8r provides explicit retirement evidence: `SchoolMessengerStaff`, `SchoolMessengerStudents`, and `SchoolMessengerAbsences` remain in config but are disabled and annotated as moved to ParentSquare in 2024.
Next step
Keep this page as lineage-only documentation and maintain links to current ParentSquare-centered communication workflows.
Interfaces
Inputs- historical student, staff, and attendance exports
Outputs- historical demographic and attendance upload artifacts
Reality to Action trace
Reality IngestionNot in scope.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesNot in scope.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Data integrity and contracts
Source of truth rules
- Historical Integr8r config comments are the authoritative evidence for deprecation status.
Safe handling
- Do not republish historical export payloads.
- Treat any retained artifacts as restricted student/family data.
Operational notes
Reliability posture
Historical reference only. Integr8r marks these jobs disabled and moved to ParentSquare.
Observability
- legacy job definitions and comments in Integr8r config
Security and privacy
Historical exports contain restricted family and student contact data; preserve as internal lineage only.
Dependencies
Upstream- legacy Integr8r configuration and historical source-system contracts
Downstream- none for current production operations
Ownership
OwnersTechnology Services
UsersTechnology Services
SchoolMessenger Communication Workflows
Operational Notes
- Method: historical file-export plus uploader workflow only; not a live production integration.
- Implementation lineage:
Config/Config.ps1, SchoolMessengerStaff/, SchoolMessengerStudents/, SchoolMessengerAbsences/, bin/SMDIM/. - Current posture: deprecated and replaced by ParentSquare-centered paths.
Registry Alignment
- Mapped registry entry:
INT-057. - Registry clarified: this is a retired workflow preserved as historical continuity, not active operations.
- Validation gaps: none for active production use; lineage-only tracking should remain intact.