FY23.1.x: Technical Design (Slate+Advising)
- Bryon Vaughn
Executive Summary
The purpose of this document is to provide the full details of the technical solution to be used for the build of the Slate+Advising solution. Everything that is needed by the developer(s) to produce the required data model, forms and workflows will be included in this specification.
Technical Components
The following sections will detail the technical components within each functional area that are required to successfully implement this project.
Data Management
Technical Requirements
The following technical requirements must be delivered for a successful implementation of this application component:
- Incoming Data
- Create scheduled exports based on last modification date for the required data points in the following systems
- SIS
- Person data from system of record
- Registration status and history
- SIS
- Create source formats and scheduled imports for all data noted above
- Create scheduled exports based on last modification date for the required data points in the following systems
- Reports and queries
- Audit queries to validate imported data
Student Relationship Management
Technical Requirements
The following technical requirements must be delivered for a successful implementation of this application component:
- Define and build interaction categories required for reporting and tracking purposes
- Documentation/training for sending adhoc emails directly from Slate, and using the Slate Email Gateway [via BCC] for external email clients (e.g., Gmail)
- Built-in functionality, nothing to develop
- Re-use Admissions training/documentation for this since the process will be similar
- Custom form to collect and entity to store data for notes on the student record
- Placeholder for specific field(s) and form design
- Appointment/meeting notes, others?
- Determine whether it is better to use Interactions, particularly for attached document support
- Placeholder for specific field(s) and form design
- Custom tab for Advisors with student history, current registrations
- Streamline immediate actions that can be taken based on the data that is displayed
- E.g., button to send a message when student hasn't registered yet, etc.
- Streamline immediate actions that can be taken based on the data that is displayed
Security & Access Management
Technical Requirements
The following technical requirements must be delivered for a successful implementation of this application component:
- Import users for launch
- System Admins
- Advising Leadership
- Advisors
- Program admins and faculty (as needed)
- Define role-based security model and assign users to appropriate groups based on role
- Include program-level grouping to further segment access based on student population