Resolving incidents via REST API does not trigger business rule.

[mikeder]

Hello, I have written a Shinken integration for our SN instance and currently I resolve an incident by updating the following: close_notes, close_code, state, incident_state and comments. The problem is the business rule that is supposed to run when incident state changes to either 6 or 7 doesn't get triggered. This in turn causes the calender_stc field to not get updated until our close audit runs 48hrs later. Looking at the History list for two incidents, one resolved via the UI and one resolved via REST API, shows me that the Duration, Resolve Time, Business Duration, Business resolve time are not updated by the mark_resolved business rule when resolve via REST.

Can anyone shed some light on why an update to the incident table via REST API is handled differently than one made via UI?

[myles3]

I have also just experienced this: business rules triggered by REST updates (PATCH or PUT) are not able to modify read-only fields. This seems to be a bug in the platform.

[saidineshdevadu]

Check the permissions for the user which is used in the integration