It would be great to have the option to re run reports for individual pupils rather than having to re run a whole year group when only one pupil's report has been amended and needs re publishing.
6
Good Feature
Thank you for your interest in this idea. We’re pleased to share that development is underway to support selective publishing of student reports to the portal.
What we’re exploring: We’re also investigating functionality to generate a report for a single student after the routine has been run for the wider cohort, rather than repeating the full run.
What’s coming: You’ll be able to choose which individual student reports to publish or withhold. For example, if you’re publishing Year 11 reports and 10 students have outstanding fees, you can publish reports for the remaining 90 students. Once fees are paid, you’ll be able to publish reports for those students individually — without needing to re-run the full process.
Next steps: More information will be announced via the usual communication channels once the feature is closer to release.
Can this please be looked into? It is clearly very high on everyone's agenda
Revisiting this idea closer to the report publishing month!
Is there a reason/challenge to why it is not possible to develop/Implement.
I hope this is picked up by iSAMS soon for overhaul for publishing as well holding on to the individual reports.
Trying to explain it here with scenario:
A school where total students are 2000+, 300 students {from different years} are not receiving reports. -- with the existing process of "Creating a routine for a year group" and "Running the routine for entire year group' it will publish all the students. Deleting the 300 files once the run is complete is a massive and unnecessary work for a system.
After deleting the student files, if we need to publish it for 100 students, we need to run all the routines again, while deleting other 200 files. and repeat this process forever.
----------
The suggested option which most of the school's use: Disabling the parent portal for those families. is not logical where single sign on is setup for ECA/Parent evening and other third-party applications.
Once published - the individual pdf is not visible anywhere to common user to share it with parent via email if needed.
This is similar to idea shared in MIS-I-1098 and many other which are never looked at by iSAMS.
Allowing users to block the reports/publish the report for a group of users (e.g. Outstanding fee). blocking the entire portal or "unwanted report removal" is not ideal. Having more options at "Portal Publishing" will allow that easily.