This bug has been fixed.

Fixed Version

  • Ver. 12.0.0

Affected Version and Operation

  • Version 11.11.0 and Later vesions
  • In HTML5 Modeler, adding a new destination (flow) to an existing XOR/OR gateway

Bug Details

  • Occurs in operating
    • In HTML5 Modeler, adding a new destination (flow) to an existing Step as the following
      • XOR/OR Gateway
      • A Human Task with a Split setting that specifies a Split condition with a Data Item
  • What will occur
    • Conditions may not be evaluated according to the display order of Split settings

Workaround ・ Recovery

  • When adding a new flow to the target Step, perform one of the following operations on the Split setting screen
    • Rearrange the order of conditions
    • Add new conditions (in addition to those automatically added)
  • This Bug is due to be fixed in the next version

1 thought on “May Not Be Evaluated According to the Display Order of Split Conditions (Fixed)”

  1. Pingback: v12.0 2020-05-11 Modeling Feature Completely Transits from Flash to HTML5 – Questetra Support

Comments are closed.

%d