You can use run conditions to insert condition statements into your flows and business process tests.
A run condition checks the current value of parameters before running a:
Component in a flow
Component in a business process test
Flow in a business process test
Based on the parameter value and the run condition definition, Application Lifecycle Management (ALM) determines whether to:
Run the component or flow
Skip to the next component or flow
Skip to a subsequent component, flow, or group that you choose
Set the component \ flow status to Failed and skip to the next component
When you run business process tests containing run conditions (either directly or indirectly through a flow), the test run results display the results of run conditions in the test, and lists the entities that did not run because a run condition was not met. If a run condition is not met, the test results also provide details about why the entity run failed or did not run.
Tip: As with regular business process tests, you can view test results in the Actual section of the Last Run Report tab in the Test Lab module.
Note: If you set run conditions, and later add or remove an entity or change the order within a flow or a test, the parameters may no longer be relevant and the run condition may not work. For example, if
Component B uses an output parameter value from
Component A, and you change the order of the components so that
Component B precedes
Component A, then
Component B cannot receive the output parameter value from
Component A and the invalid run condition is ignored.