Audit trail to show the API Client Name rather than Client ID
In the audit trail it would be easier to determine who/what made the change by seeing the Client Name rather than the ID. See attached screenshots for more detail.
It would be useful if the audit trail started with the date that a prospective student record was added to the system, currently the first record in the audit is whenever a field is updated, not when the record was created.
Enhancements to Registration Status API Endpoints for Improved Data Consistency and Usability
Summary: While integrating with the iSAMS API, we identified inconsistencies and limitations in the Registration - Registration Status endpoints that hinder reliable data retrieval and system interoperability. This proposal outlines actionable enh...
Ability to filter data for certain years/date range on the Attendance Records/ Medical Diary/ Rewards & Conduct Records
We would like to propose the feature of filtering the data to be shared on the cloud portal for parents, such as the Attendance records, Medical Diary, Rewards & Conducts records... If you could provide the ability to filter those data by acad...
Introduce the possibility to pseudonymise admissions records that have been withdrawn/rejected x months ago
We would look to anonymise admissions data for pupils who chose not to join us some time ago, so that we can retain the generic statistical information for future analysis whilst being GDPR compliant.
It would be useful to have the ability to upload data for Custom Fields for pupils. Currently if we wanted to update custom fields that have data such as, GCSE subject option choices, so that we can email parents the confirmed choices, we have to ...
Do not show disabled accounts against Security Profiles
It would be helpful if disabled accounts do not show in the profile 'count' of how many people are using that profile. We do not delete some users who have done a lot of work within iSAMS, as then you lose the audit - it simply shows Unknown. The ...