Ideas

The workflow for invoice approval only allows for one cost centre. It would great if it could send elements of the invoice to different approvers if the cost being split across multiple cost centres

Dear iSAMS Support Team, We urgently require assistance resolving persistent 500 errors when using the POST /api/medical/students/{schoolId}/documents endpoint, despite following the "Try It" example and validating all parameters against live syst...

We are requesting for a reduce in API Key Cache Expiry time in the Batch API Module to real-time (or as minimal as possible). In our school we are trying to integrate parent, student data in Business Central for billing purpose. Having it update i...

We propose an enhancement to the iSAMS REST API to include endpoints for accessing Audit Logs associated with Student and HR records. Currently, while audit logs are visible within the iSAMS interface, the inability to retrieve this data programma...

Affected Resource: PATCH /api/medical/students/{schoolId}/conditions/{conditionId} Current Documentation Problem Statement: Developers cannot reliably update student medical conditions due to: Unclear required JSON format (RFC 6902 vs custom struc...

We are reporting a validation discrepancy identified in the "[POST] Create Medical Condition for Student" and "[PATCH] Update Medical Condition for Student" REST API endpoints. The current logic erroneously validates the dateReviewed field against...

When a User has left we are unable to stop them from appearing as available approvers against accounts. Setting security No_Access. Access level 9, input allowed 'No', Z_LEAVERS user group, Not active and removing them from the Key List of authori...

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

This would make the system consistent with the other access options in the account details tab. It's going to be very helpful when we move over to the new cloud portal and need to give more staff access to the Cloud portal module.

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