BPMN end node to allow multiple incoming connections

This is a customer reported issue:

The customer currently has multiple BPMN 2.0 modeling tools, and are looking for interoperability across platforms. 

The concern is around the manual conversion required in this case.

Customer Comments: There are validation errors for when multiple tasks use the same end event. To be supported in RHPAM each task must be manually changed after import to create separate end events, this will clutter the workflow and impact maintaining a single documented workflow that does not change because of the implementation.