Issue Type | Issue key | Summary | Component | Module/Program | Comment | Service Desk Reference Number(s) |
|---|---|---|---|---|---|---|
Bug | DSY-17615 | Super Authoriser is unable to authorise Purchase Order | SynWeb | Purchase Orders - Purchase Order Maint | Fixed an issue which occurred in SynWeb for Purchase Orders with 2 level authorisation. Previously SuperAuthorisers were being validated based on if they belonged to a group with code 'POSA', now they are validated based on having 'Update' permission on 'PUR|PurchaseOrderMaint||SuperAuthoriser' as described here https://help.synergetic.net.au/s/article/Configure-security-access-for-PO | 00292733, PRB-00001870 |
Improvement | DSY-26408 | Modify FutureStudent PUT/POST to not require Previous School | CoreAPI | Future Enrolments & Enquiries - Applications | For the CoreAPI FutureStudent PUT and POST endpoints, PreviousSchool is now no longer mandatory as long as there is a school on luSchool lookup table with the SynergyMeaning 'UNKNOWN'. See: https://developer.synergetic.net.au/api.html#post__future_student | |
Improvement | DSY-26359 | Prevent Stripe from unintentionally debiting accounts with recurring Payments in non-production environments when a live database backup is restored in another location | SynDB, Stripe | Stripe | Added a mechanism to automatically disable Stripe payments when an environmental change that may indicate non-production use is detected. Re-enable Stripe by setting the System|DBServerValid config to true and restarting CoreAPI. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article