Conditional Event evaluation not consistent

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Won't Fix
    • Priority: L3 - Default
    • None
    • Affects Version/s: 7.16.6
    • Component/s: None

      Environment (Required on creation): 

      Dev

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

       

      Within a mult-process Event Subprocess Condition Events are evaluating differently for different instances of the subprocess.   Some instances are passing the condition, some are not.   Attempting to trigger re-evaluation by altering a variable has no effect and there is no way to get the condition to fire.

       

      The condition for 'Initial Update Complete' is #{initialUpdateComplete > 0} where initialUpdateComplete is a variable in the parent process scope.

      Steps to reproduce (Required on creation):

       

      Create multiple instances within Event subprocess.

      Observed Behavior (Required on creation):

      Some instances within the subprocess pass the condition,  some do not.  All instances refer to the same varaible in parent scope.

      Expected behavior (Required on creation):

      All condition events evaluate the condition the same.

      Root Cause (Required on prioritization):

      Solution Ideas (Optional):

      Hints (optional):

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Bill Powell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: