As Aeries is redesigned, we are taking the opportunity to build in new features that can be universally applied throughout the system.
Data Validations
Occur on all “edit” operation (change, insert & delete)
Should include Errors and Warnings
Should be dynamic where the customer can add their own
Should have defaults that align to Aeries and State Reporting Standards
Custom Fields
All “tables” should allow for an unlimited number of custom fields to be added of any standard data type
May need to have some different standards for custom fields on child pages
Required Fields
All “tables” should support district-defined required fields
Requirements should support complex multi-field conditions
Requirements should support referencing other, related tables to create requirements on the current record
Should have distinction between “Required” and “Recommended” fields
Documents
All records (student or otherwise) should be able to have documents associated with them
Documents should be able to be linked to the “Master” record (ie: Student or Staff) or be linked to the specific record (ie: Discipline or Staff Credential)
Agreements
All records (student or otherwise) should be able to have “Agreements” associated with them
Full digital signature process
Agreements should be able to be linked to the “Master” record (ie: Student or Staff) or be linked to the specific record (ie: Discipline or Staff Credential)
Camden Iliff
As Aeries is redesigned, we are taking the opportunity to build in new features that can be universally applied throughout the system.
Data Validations
Occur on all “edit” operation (change, insert & delete)
Should include Errors and Warnings
Should be dynamic where the customer can add their own
Should have defaults that align to Aeries and State Reporting Standards
Custom Fields
All “tables” should allow for an unlimited number of custom fields to be added of any standard data type
May need to have some different standards for custom fields on child pages
Required Fields
All “tables” should support district-defined required fields
Requirements should support complex multi-field conditions
Requirements should support referencing other, related tables to create requirements on the current record
Should have distinction between “Required” and “Recommended” fields
Documents
All records (student or otherwise) should be able to have documents associated with them
Documents should be able to be linked to the “Master” record (ie: Student or Staff) or be linked to the specific record (ie: Discipline or Staff Credential)
Agreements
All records (student or otherwise) should be able to have “Agreements” associated with them
Full digital signature process
Agreements should be able to be linked to the “Master” record (ie: Student or Staff) or be linked to the specific record (ie: Discipline or Staff Credential)