You are welcome, I am glad I could help.

Please find below the answers for the points you raised :

1. yes you have always to specify a target for the moment. A global compensation will be supported in the next release for sure, and it will be done on the designer side exactly like you have described.

2. It works perfectly on my machine. What version are you using? if you have not downloaded 5.2 final release that would be a good opportunity to do so :)

3. same explanation as question 1.

(sorry for the link inconvenience, it should be fixed soon )

Thanks

re: 2. I am using the current beta (5.2.0.091) on windows.Attached is the example where the target on the end compensation event cannot be set. No biggie, this particular example works despite the error flag on the property.

Thanks for specifying.
That's was a bug with that version, getting the 5.2 final release will fix it.

confirmed that at designer 5.2.0115 and server 5.2.0.050
1. target property can now be set on the end compensation event
2. omitting the target property on the compensation end event has the effect of executing all eligible compensation activities

so parallel activities can be compensated as in the attached BPMN diagram

Note that the parallel gateway symbol must be present at the start of the parallel flows for this to execute correctly although it is optional in BPMN.