Ideas

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...

Allow posting / put for OOS entries and future absences via API Call backs

We would like to be able to import and retrieve deposit details using the REST API, as this would enable us to integrate more closely with our CRM and Finance systems and ensure that deposits received are correctly recorded without having to resor...

As part of the options available to us via the REST API, we can update the languages spoken by students. Since education is increasingly likely to take place in a language that is not the student's native tongue, it is a requirement for us to moni...

In order to show segregation of duties and timeliness of processing it would be useful to have a report to show auditors that show when each stage of the pay run progressed, and who processed that stage. All we see in Staffology for the month in p...

The absence, employee and claim exports in the payroll section are not created if Every HR is integrated with Staffology. It would be very useful to have these created as there are no reports showing what has been created and submitted to payroll ...

The "GET" request for Pastoral (Wellbeing) Concerns requires the concern {id} as an input parameter, as well as the student's {schoolId}. There is currently no endpoint to list concerns by student, and so it is not possible to know the concern {id...

The customer wanted a report to highlight outstanding documents that are due back from Suppliers but havent been received yet and a facility to send reminders to supply them

The customer wanted the facility to add additional fields into the suppliers form.

Be able to set a Supplier as being on STOP. Suggested workaround was to archive them or change their name to being for example "STOP - abc ltd"