1. Presented by: SIF3: Multi-Object CRUD Joerg Huber SIF3 Consumer: Multi-Object CRUD Exercise

2. © Systemic Pty Ltd September 2014 Training Course - Sydney: SIF3 - Multi-Object CRUD 2 What is Multi-Object CRUD? A Consumer can request CRUD operations for multiple SIF Objects (of the same type) with ONE REST call!  I.e. Update, Create, Delete 10 StudentPersonals in one call.  Response will return a list of HTTP status and/or Error Messages. #Elements in the list equals #Elements in request. Valid Status to be returned depends on the requested operation (200 ok for update, 204 ok for create etc). Refer to SIF Specification for details.

3. © Systemic Pty Ltd September 2014 Training Course - Sydney: SIF3 - Multi-Object CRUD 3 Multi-Object Create (and single object create) This REST API call requires a HTTP Header parameter called “mustUseAdvisory” which is set to either True or False :  True: The consumer has set the RefID in the SIF Objects and requests the provider to accept it. Provider may still reject it if it is invalid, duplicated etc.  False: Consumer may provide a RefID but expects the provider to allocate a new and final one and then return the new RefID in the response. SIF3 Framework: Set it in the property adapter.mustUseAdvisoryIDs

4. © Systemic Pty Ltd September 2014 Training Course - Sydney: SIF3 - Multi-Object CRUD 4 Multi-Object Delete When deleting SIF Objects only a list of RefIDs to must be provided (payload).  SIF Object does no longer exists in Consumer Application, so not more than RefID is known.  Internally the Delete API uses a HTTP POST with a HTTP Header called “methodOverride” with a value of “DELETE” HTTP DELETE does not allow for payloads where as HTTP POST does. Fully managed within SIF3 Framework (i.e. transparent to the API). Developer doesn’t need to deal with this special case.

5. © Systemic Pty Ltd September 2014 Training Course - Sydney: SIF3 - Multi-Object CRUD 5 Exercise – Multi-Object Delete, Create etc. Return to DemoConsumer from Exercise 2 Try to add more methods to either:  Delete  Update  Create Multiple StudentPersonal objects in one API call. See Exercise 4 for details