[SYNCOPE-876] Fake after object reported by propagation in case of delete

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.8, 2.0.0-M3
• Fix Version/s: 1.2.9, 2.0.0-M4
• Component/s: core
• Assignee: Francesco Chicchiriccò
• Reporter: Francesco Chicchiriccò
• Created: 23/Jun/16 09:14
• Updated: 24/Jun/16 08:02
• Resolved: 23/Jun/16 09:47

Description

SYNCOPE-858 improved the way how Syncope handles the connector object returned after create / update, especially when the external resource is responsible for generating the _UID_ value.

Unfortunately, this currently leads to the generation of fake connector objects in case of delete, where such object is instead expected to be null.

Issue Links

• is broken by: SYNCOPE-858 Ensure afterObject is provided after propagation