Script Task disappear in eclipse .bpmn but present in the XML

Yep, this is common (although not that frequent) and very annoying.
The only way to fix that is to edit the XML directly: there is an inconsistency in the laneset element. The shape is said to be at a place it isn’t and it confuses eclipse. Just fix this and you can continue working.

I haven’t documented how to fix it, I don’t recall the exact steps, and I don’t have anything to test with. Send the XML by email at [email protected] if you want and I’ll look that. This way I can document once and for all for my team as well.

Alright, here’s the fix:

Step 1: identify an element connected to the missing item. eg. flow64

Step 2: look for it in the XML

<sequenceFlow id="flow64" sourceRef="exclusivegateway11" targetRef="usertask11">
  <conditionExpression xsi:type="tFormalExpression"><![CDATA[${yes11}]]></conditionExpression>
</sequenceFlow>

Our missing element is ID: exclusivegateway11

Step3: Find an element that is in the same swimlane (e.g. usertask11)

<lane id="lane2" name="Data Steward">
  <flowNodeRef>usertask11</flowNodeRef>
...
</lane>

Step 4: Make sure our missing element exclusivegateway11 has one and only reference as a lane subelement, in the correct lane.

Incorrect XML

    <laneSet id="laneSet_V2TableDocumentation">
      <lane id="lane1" name="Technical Steward">
...
        <flowNodeRef>exclusivegateway11</flowNodeRef>
        <flowNodeRef>exclusivegateway11</flowNodeRef>
        <flowNodeRef>exclusivegateway11</flowNodeRef>
      </lane>
      <lane id="lane2" name="Data Steward">
        <flowNodeRef>usertask11</flowNodeRef>
...
      </lane>
    </laneSet>

Fixed XML

    <laneSet id="laneSet_V2TableDocumentation">
      <lane id="lane1" name="Technical Steward">
...
      </lane>
      <lane id="lane2" name="Data Steward">
        <flowNodeRef>usertask11</flowNodeRef>
        <flowNodeRef>exclusivegateway11</flowNodeRef>
      </lane>
    </laneSet>

Save and reload, catastrophe averted!