Deploy and revoke operations should update the database correctly

Current Situation

• Deploy Operation
  If a Controller object, for example a workflow, is already deployed to a Controller A and users want to deploy the same object to Controller B, then Controller B receives the object but users cannot verify in the GUI because the database has been updated for Controller A.
• Revoke Operation
  If a Controller object, for example a workflow, is deployed to Controller A and to Controller B, whereby this was first performed for Controller A and subsequently users attempt to revoke the object from Controller A, then the object will be deleted from ControllerA, however, the database entry for Controller B will be updated.
  In case of a workflow, it will still be visible in the GUI's Workflows view for Controller A being “not synchronized” instead of being deleted from Controller A too.

Desired Behavior

The database must be updated correctly to reflect deployments and revocation to a number of Controllers.