I was trying to set a different body for each escalation I raised in this diagram, this wasn’t possible. Go to this diagram on Escalation Events - change the payload of the escalation within the collapsed subprocess on Path C, note how this also changes the escalation body on Path A.
We spoke to Daniel Lubke about this issue and he confirmed that it should be possible to set a different payload for each escalation event in the diagram. We believe this can be accomplished within the BPMN IO Extensions if, when placing a new escalation event in the diagram, you also create a new beside the process. So that each escalation event has a correspding escalation in the xml. When you set the code or payload expression on that escalation event, it should update it's corresponding BPMN Escalation.
I was trying to set a different body for each escalation I raised in this diagram, this wasn’t possible. Go to this diagram on Escalation Events - change the payload of the escalation within the collapsed subprocess on Path C, note how this also changes the escalation body on Path A.
We spoke to Daniel Lubke about this issue and he confirmed that it should be possible to set a different payload for each escalation event in the diagram. We believe this can be accomplished within the BPMN IO Extensions if, when placing a new escalation event in the diagram, you also create a new beside the process. So that each escalation event has a correspding escalation in the xml. When you set the code or payload expression on that escalation event, it should update it's corresponding BPMN Escalation.