Subflow combinations not considered for All Possible Paths and constraints

Products

• CA Agile Requirements Designer

Issue/Introduction

When using subflows, the Path Explorer in the parent flow doesn't consider all the paths.  

Scenario 1:  Create 2 subflows, each with multi-output block with  A, B & C.  Add both subflows to a main flow with the output from the 1st flow being the input into the 2nd flow.  Generating All Paths in the main flow only generates 2 paths, not the 9 combinations expected (AA, AB, AC, BA, BB, BC, CA, CB, CC).

Scenario 2: Changing the 2 subflows to have an endpoint for each of the paths, and then using all 3 outputs as inputs to the next block has a similar issue when using the stored paths in each subflow.  When Subflow Integration is set to All Paths, it generates the 9 paths.

Applying constraints to subflows in the first scenario (IF subflow 1 -> A THEN NOT subflow2 ->) also has unexpected behavior.

Environment

Release : 3.0

Component : CA Agile Requirements Designer

Resolution

We were unable to reproduce the customer's results. However, the results we did see are expected using the default settings of the Optimizer.

In Scenario 1, When running the Optimizer with the default settings for All Possible Path is All Rows, which results in 3 paths generated. 



If you are expecting all 9 paths returned. For this you need to use the "All Row Combinations" when generating the Paths.


In Scenario 2, using flows modified according to their description, 6 paths is correct.


The reason for this is the not(...) on the right-hand side of the constraint is always false. Therefore, out of the 9 possible paths (AA, AB, AC, BA, BB, BC, CA, CB, CC), the 3 paths (AA, AB, and AC) where the left-hand side is true are invalid. Note that unlike Scenario 1, here it does not matter whether we choose Default, All Rows, or All Row Combinations. Also note that the same constraint works correctly (in the same way, returning 6 instead of 9 paths) in Scenario 1 with All Row Combinations.