Send full schema payload on Update for web services app?

[josefismael (Josef Maung)]

Which IIQ version are you inquiring about?

8.3p3

I’m forced to work with a downstream app that has an API that…let’s say leaves something to be desired Among the many limitations is the fact that there is no PATCH method for updates, only a POST to the same endpoint as you use to create. Which is then correlated on their side based on an unique attribute that is sent. But the real kicker is that the API requires the full schema to be sent as the payload, including attributes that are not changing.

So naturally, my Create Account operations are working fine, however my Update and Add Entitlement methods are bombing out with ‘500 - request body not well-formed’ errors. Of course, in the logs I can see that IIQ is doing the smart thing and only sending attributes that are actually changed as part of the body when I use the $plan. in the body.

I think I might be able to do this with a Before Provisioning rule, but this app is already way outside our typical patterns and I’d rather not have to support more complexity.

Is there a way to tell IIQ to send the full payload on every update?

[enistri_devo (Emanuele Nistri)]

Hi @josefismael,

welcome on the dark side of webservice

I had a similar case some time ago. You have two options to managed it:

1. Build the body on before operation rule(not Before Provisioning rule) reading the account attribute directly
2. Use a provisioning form with different attribute names respect to the schema

This is pass because IIQ dont put unchanged attribute into the update plan and in this case you must managed manually.