Blank Initial String Type Data is Determined as the State of “Value Exists”

This bug has been fixed.

Fixed Version

  • Version 9.2.0

Affected Version and Operation

  • Version 9.1.0
  • String type data without initial value is used for determination of conditional split without a Task in read / write.

Bug Details

  • Occurs at the following timing:
    • Occurs in the Process Model of:
      • String type data item without initial value is defined.
      • The String type data item is being used for determination of conditional split (Value exists or not).
      • The process Model has been edited, saved and activated with the version 9.0.
        (Except if continuously operating from version 9.0,etc..)
    • Occurs in operating:
      • Without a Task to be entered String type data (read / write), the process arrives at gateway, and determined expression of conditional split (Value exists or not).
  • What will occur
    • Irrespective of no value has been entered, it is  determined as a state of “value exists”, will not proceed to the expected transition.


  • This bug can be work around with a method of ‘Overwrite String type data with the value of its own just before the gateway’.
    • Layout a ‘Service Task (Data assignment)’ right before the gateway.
    • Select “the String Data Item” at ‘Data item to save the value or the result of the expression’, and input “#{data[‘data definition number’]}” in ‘Value of Expression’ field.
      * “data definition number” is to be confirmed in Process Data Item setting screen.
  • This Bug is due to be fixed in coming Version (9.2.0)