Issue

When updating the proxy object via API it's intuitive that those changes would need to be promoted from staging to production for example.

When updating/creating the mapping rules object(s) then this requires a second, not very intuitive, API call to update the proxy object. If this is not done then from the UI it can be very confusing because the mapping rules will appear in the integration page but they will not appear in the proxy config object.

The same action completed from the UI requires the user to hit the "update the staging environment" button and therefore mapping rules will be added to the proxy config object implicitly.

Resolution

For now I would suggest we clarify this behaviour in our ActiveDocs to avoid this problem. In the long term we need to think about how to solve this issue which is also related to that reported in THREESCALE-715. Potentially making the mapping rules direct children of the proxy config object would improve this.