Deleting a Node May Make Editing the App Impossible

Fixed Version

• Ver. 18.0.1

Affected Version and Operation

• Ver.18.0.0 and earlier versions
• Delete nodes that meet specific conditions in the modeler

Bug Details

• Attempting to delete a node that meets the following conditions may result in an error during the deletion, or the deletion process may succeed but the App may become uneditable
  • Has Boundary events
  • Has one input flow and one output flow
  • The input flow is connected to the bottom edge of the node
• Depending on whether or not there is an output flow from the boundary event, it will be one of the following:
  • If a boundary event does not have an output flow, the deletion will succeed, but the app will be in an invalid state and will no longer be editable
    • Immediately after deletion, an error dialog appears, and reloading the page using the “Refresh” button in the dialog causes the workflow diagram to disappear
  • If a boundary event has an output flow, the delete operation will result in an error, and the application state will not change

(In Ver. 18.0, the delete operation itself will result in an error regardless of whether or not there is an output flow from boundary events. The app will not enter an invalid state and will remain editable.)

Workaround/Recovery

• If the app becomes corrupted and you can no longer edit it, restore the app to a snapshot or the latest version
• To delete the relevant node, disable the node’s Deadline and Error handling settings, delete the boundary events beforehand, and then delete the node
• This Bug is due to be fixed in the coming version (Ver. 18.0.1)