Correcting errors from saving a message flow or subflow

Correct the errors that are reported when you save a message flow or subflow.

About this task

When you save a message flow or subflow, as described in Saving a message flow or subflow, the flow is validated. Errors and warnings are shown in the Problems view. The following steps describe how to correct errors that occur when you save a flow.


  1. Examine the list of errors and warnings in the Problems view.
  2. Double-click each entry in turn.

    The message flow or subflow is opened in the editor view (if it is not already open), and the editor selects the node in which the error was detected. If the error has been generated because you have not set a mandatory property, the editor also opens the Properties view, or dialog box, for that node.

    If you have included a user-defined node in your message flow, and have defined one or more of its properties as configurable, you might get a warning about a custom property editor. If you define a property as a configurable property, and you have specified that it uses a custom property editor, the BAR editor cannot handle the custom property editor, and handles the property as if it is type string. This action restricts your ability change this property at deployment time.

  3. Correct the error that is indicated by the message.
    For example, provide a value for a mandatory property.
  4. When you have corrected all the errors, save the message flow or subflow again.

    The editor validates all the resources that you have changed, and removes the corresponding graphical indication from the nodes that you have modified successfully. Corrected errors are also removed from the Problems view.


You do not have to correct every error to save your work. The editor saves your resources even if it detects errors or warnings, so that you can continue to work with them at a later date. However, you cannot deploy a resource that has a validation error. You must correct every error before you deploy a resource. Warnings do not prevent successful deployment.